Skip to content

docs: gateway and platform pages match the release - #1032

Open
nik13 wants to merge 12 commits into
mainfrom
docs/gateway-release-2026-10
Open

nik13 wants to merge 12 commits into
mainfrom
docs/gateway-release-2026-10

Conversation

@nik13

@nik13 nik13 commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

Summary

These pages now match the AI gateway release (Agent Command Center) and the platform pages it touches. Every changed sentence states what the product does today and was checked against the code it describes.

  • Command Center API reference: each endpoint's contract, including chat and streaming usage, Assistants, Vector Stores and Files, media pricing, headers and error codes.
  • Command Center features: routing and fallbacks, caching, cost tracking, rate limits, budgets, guardrails, MCP and A2A, and virtual keys, as the gateway runs them.
  • Concepts, guides and overview: the request pipeline as it runs.
  • Deployment and self-hosting: readiness, egress, image pinning and telemetry.
  • Quickstarts: send a gateway request; set up an annotation queue.
  • Evaluation, SDK, cookbook and other product pages: inputs and results for each check, with example results labelled as examples.
  • Navigation and redirects: the sidebar lists the published pages, and the four moved pages redirect.

Checks

  • check-mdx passes on every changed MDX page.
  • check-deleted-pages passes: every removed page has a redirect.
  • audit-links finds 0 broken nav or content links.
  • The whole-site astro build passes: 1,181 pages.
  • gitleaks over the range finds only the documented placeholder key in a curl example.

🤖 Generated with Claude Code

nik13 and others added 12 commits October 24, 2026 03:02
The Assistants, chat completions, embeddings and rerank, endpoints,
headers and media pages, and the API reference concept page, state the
fields each endpoint takes, the headers and stream chunks it returns,
the allowed models, rate limits, guardrails, request log and metering
that apply to the Assistants and Vector Stores APIs, and the
TypeScript client import `@agentcc/client`.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
…line as it runs

The overview, core concepts, configuration, platform integration,
virtual keys, organizations, errors and troubleshooting pages name the
model endpoints the request pipeline runs on, give the plugin order,
the organization config fields the gateway reads and where each one is
set in the dashboard, and list the error codes the gateway returns.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
…haves

The caching, cost tracking, custom properties, guardrails, MCP and A2A,
observability, providers, rate limiting, routing, self-hosted models,
streaming and webhooks pages state the settings each feature reads,
which gateway runs it (hosted or self-hosted), the responses and
headers it returns, the routes the organization's rate limits count,
and the events webhooks send.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
…e pinning

The self-hosted gateway page, the self-hosting overview and the Helm,
images, configuration reference, telemetry and monitoring pages state
where a self-hosted gateway sends requests, when the gateway reports
ready, which outbound calls go through the proxy, how the chart pins
each image by digest, and what each deployment mode suits.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
…notation queue

The gateway quickstarts and the get-started routing page send a request
through your configured routing, guardrails and cost tracking, find the
API key under Gateway > API Keys, and use stream loops that check
`choices` before reading it. The annotations quickstart sets up a
queue with the Manual strategy.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
… its inputs and result

The built-in evaluator pages, evaluation concepts, guides and reference,
the SDK evals, tracing, protect and optimization pages, and the
optimization guides and reference describe each evaluator, Turing model
and local metric by the inputs it takes and the result it returns, label
model-based example scores as an illustrative run, and list the SDK
arguments and result fields the released SDK provides.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Cookbook pages describe each step by what it does, label example scores
and results as an illustrative example run, name third-party models
without grading them, and use stream loops that check `choices`. The
semantic caching cookbook covers a self-hosted gateway and names where
the organization's cache switch is.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
…rve and protect as they run

Annotation guides and the queue API pages list the strategies and
fields the app takes and the export buttons it offers. Billing pages
list each plan's entitlements. Integration, observe, protect and
tracing pages scope exported traffic and guardrail activity to the
request log and use stream loops that check `choices`. The release
notes, FAQ, docs home and site landing page describe each feature in
plain terms.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
The chat widget, fast navigation, sidebar and base layout copy and
comments say what each component does. The repository tracks no
`.playwright-mcp` browser logs (`.gitignore` lists the folder) and no
unused chat side panel component. The style guide asks for a measured
figure with its benchmark and machine, or no speed claim.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
`/changelog` redirects to the release notes, and CONTRIBUTING.md names
the release notes page as the changelog. The shadow experiments page
and its `/docs/prism/` path redirect to the Command Center overview,
`/docs/command-center/api/async-batch` redirects to chat completions,
and `/docs/command-center/api/files` redirects to the endpoints
reference. The sidebar lists Langfuse under Migrate, the Assistants API
before the headers page in the gateway API section, and Comparing
Optimizers as the last Optimization cookbook.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant