docs(readme): lead with media infrastructure for the agentic internet

[yakimoto]

What changed

The README now opens with what WAVE is, then names this repository as the OpenAPI specification for that call shape. The prior opener called WAVE an "enterprise streaming platform", which is a capability, not the identity. The package.json description led with "WAVE Enterprise Streaming Platform" for the same reason and was rewritten. Two files change, one line each:

• README.md: the paragraph under the title.
• package.json: the description string. No version bump. The package is private: true and is not published.

The Overview module list, usage commands, authentication section, related packages, and license are untouched. openapi.yaml is untouched, so generated types do not change.

Before / after

Surface	Before	After
README first sentence	OpenAPI 3.1 specification for the WAVE enterprise streaming platform APIs.	WAVE is media infrastructure for the agentic internet: one call shape moves live and on-demand media across every transport, and both kinds of user, people and agents, discover it, call it, and pay for it per call.
README second sentence	(none)	This repository is the OpenAPI 3.1 specification for that call shape.
package.json description	WAVE Enterprise Streaming Platform API specification — openapi.yaml plus the tooling that validates it and generates SDK types from it.	OpenAPI 3.1 specification for WAVE, media infrastructure for the agentic internet: openapi.yaml plus the tooling that validates it and generates SDK types from it.

Accuracy checks

• openapi.yaml info.title still reads "WAVE Enterprise Streaming Platform API" and info.description opens with the same phrase. That is the spec's own metadata and is rendered into every generated client, so it is left for a separate, reviewed spec change rather than folded into a README PR.
• No SOC 2 claim, no "first" claim, no customer or revenue claim, no Wallet availability claim. Em-dashes in changed lines: 0 (the old description carried one).

Gates

$ node voice-gate.mjs README.md --register-bans --report
voice-gate: clean
$ positioning-check.sh README.md
positioning gate: 0 errors, 0 warning(s) → PASS
$ npm ci --ignore-scripts && npm run lint    # redocly lint openapi.yaml
openapi.yaml: validated in 101ms
Woohoo! Your API description is valid. 🎉
You have 55 warnings.        # exit 0; the 55 warnings pre-date this PR (openapi.yaml is untouched)

LIVE RECEIPTS

$ npm view @wave-av/api-spec description version
npm error 404   (registry.npmjs.org, 2026-09-02: private package, never published)

$ curl -sS https://gateway.wave.online/.well-known/wave-skills.json -o skills.json -w '%{http_code}'
200
178 skills; 175 priced over x402 in USDC (177 settle on Base, 1 on Tempo); 2 free; 1 metered. Measured 2026-09-02.

Operator steps

None. Do not merge from automation; a person reviews and merges.

🤖 Generated with Claude Code

https://claude.ai/code/session_01K9mRh8G2ugbUt2kaXvFvF6

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

---

Note

Low Risk
Documentation and package metadata only; no API spec, code, or generated artifact changes.

Overview
Repositions how WAVE is described at the repo entry points: the README opener and package.json description no longer lead with “enterprise streaming platform” and instead frame WAVE as media infrastructure for the agentic internet, with a unified per-call model for people and agents.

The README now explains that positioning first, then states that this repo holds the OpenAPI 3.1 spec for that call shape. openapi.yaml and generated types are unchanged; spec info.title / info.description still use the older “Enterprise Streaming Platform” wording.

^{Reviewed by Cursor Bugbot for commit d78a874. Bugbot is set up for automated code reviews on this repo. Configure here.}

Summary by Sourcery

Clarify WAVE’s product positioning and the purpose of this API specification repository.

Enhancements:

• Reframe the README and package metadata to position WAVE as media infrastructure for the agentic internet and clarify this repository’s role as its OpenAPI specification.

Documentation:

• Update the README’s introductory description to lead with WAVE’s identity and call-based media model.

[codeant-ai]

Your free trial PR review limit of 300 PRs has been reached. Please upgrade your plan to continue using CodeAnt AI.

[qodo-code-review]

ⓘ Qodo reviews are paused because your workspace is out of credits. Ask your workspace admin to add credits to resume reviews. Manage billing

[sourcery-ai]

Sorry @yakimoto, this account has used its review budget of 2,500,000 diff characters for the last 7 days.

You can request another review in 8 hours and 43 minutes by commenting @sourcery-ai review.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_41a19c1b-8a0e-49d4-8e01-7d64cf2134b0)

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This documentation-only PR updates the README and private package metadata to lead with WAVE’s media-infrastructure identity and clarify that the repository contains the OpenAPI 3.1 specification for its call shape; the API specification, generated types, version, and other documentation remain unchanged.

File-Level Changes

Change	Details	Files
Repositions the project identity in the README and package metadata from an enterprise streaming platform to media infrastructure for the agentic internet.	Rewrites the README opener to describe WAVE’s media-infrastructure positioning and identify the repository as its OpenAPI call-shape specification. Updates the package description to use the same positioning while retaining the specification and tooling context.	README.md package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[gitar-bot]

Note

Automatic reviews are paused because your team has used its included automatic processing for this billing period (headroom scales with your seat count). You can still comment "Gitar review" to run one anytime, and automatic reviews resume on their own by October 1. Add seats for more headroom.
Learn more

Code Review ✅ Approved

Repositions WAVE's product identity in the README and package.json description, leading with media infrastructure for the agentic internet rather than enterprise streaming platform capabilities. The OpenAPI specification reference and all tooling sections remain intact. No issues found.

Options

Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[macroscopeapp]

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This PR only updates the README’s introductory copy and leaves the API specification and all runtime behavior unchanged. The sole changed file is within the author’s ownership area.

Not approved because:

• Credit balance exhausted. Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: 0d787280-72a4-4622-a634-e95f77c36a86

📥 Commits

Reviewing files that changed from the base of the PR and between 1f0cb94 and d78a874.

📒 Files selected for processing (2)

• README.md
• package.json

Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

📜 Recent review details

⏰ Context from checks skipped due to timeout. (1)

• GitHub Check: semgrep-cloud-platform/scan

🧰 Additional context used

📓 Path-based instructions (1)

See `README.md` for setup.

📄 CodeRabbit inference engine (AGENTS.md)

Files:

• README.md

🔇 Additional comments (2)

README.md (1)

3-3: LGTM!

package.json (1)

6-6: LGTM!

---

📝 Summary

Summary by CodeRabbit

• Documentation

  • Updated the README to describe WAVE as media infrastructure for the agentic internet.
  • Clarified support for a unified access model across live and on-demand media, with discovery and usage by both people and agents.
  • Documented per-call payment capabilities.

• Chores

  • Updated the package description to align with the current WAVE product positioning.

Walkthrough

WAVE descriptions now present the project as media infrastructure for the agentic internet. The updated text covers live and on-demand media, people and agents, and per-call payment.

Changes

WAVE positioning

Layer / File(s)	Summary
Description updates README.md, package.json	The README and package description now identify WAVE as media infrastructure for the agentic internet. The README also mentions unified live and on-demand media access, people and agents, and per-call payment.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to d78a8

This PR updates documentation and private package metadata only; no API behavior, generated types, or runtime code changes are introduced, so no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the primary README positioning change. It matches the documented changes in README.md and package.json.
Description check	✅ Passed	The description directly explains the README.md and package.json updates, their scope, validation results, and unchanged files. It is relevant and sufficiently specific.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/positioning-media-infra

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch docs/positioning-media-infra

---

_{Comment @coderabbitai help to get the list of available commands.}