References
Reference material for looking things up rather than reading end to end: the SDK and API surfaces, the gateway's documented behavior, telemetry and audit schemas, and the planning and evaluation pages that support a rollout.
Programming surfaces
Agent Router exposes two different HTTP surfaces. They are related to the management plane and data plane split, but they are not the same thing: the management plane is where Agent Router is hosted and configured; the Management API is the HTTP catalog for that configuration. Live model traffic uses the Gateway APIs on the data plane.
Agent Router SDK
Quickstarts for Go, Python, TypeScript, and curl.
Gateway APIs
Use when an app sends prompts through the data-plane gateway: OpenAI- or Anthropic-compatible paths such as /v1/chat/completions, with request and streaming examples.
Management API reference
Use when provisioning or automating Agent Router itself: clients, keys, catalog, projects, insights, and related OpenAPI services.
Gateway behavior and schemas
Gateway behavior
Routing, fallback, streaming, and error semantics as the gateway implements them.
Configuration propagation
How long a saved change takes to reach the data plane, and what the gateway returns while it is in flight.
Console messages and states
What a banner, badge, or empty state in the Console means, and which action clears it.
OTEL metrics
The OpenTelemetry metrics and attributes the gateway exports.
Audit log events
The audit event catalog with actors, targets, and payloads.
Reading tare doctor output
The status line, the checklist categories, exit codes, and what each finding means.
Planning and evaluation
Sizing and scale
Throughput, resource sizing, and deployment footprint.
Compliance
Residency, retention, and due-diligence answers.
Evaluation scenarios
Graded, verifiable exercises for a hands-on product evaluation.
Lookup