API reference overview

Gateway routes

AnchorShell Relay currently implements these application-facing routes:

POST /v1/chat/completions
POST /v1/responses
POST /v1/embeddings
GET  /v1/models

The proxy rewrites the incoming model to the selected endpoint’s configured upstream model. Streaming is supported for compatible request/endpoint combinations.

Hosted authentication

External hosted traffic goes through AnchorShell Platform. Platform authenticates the browser session or user API key, resolves organization/user identity and Relay permissions, strips untrusted client context headers, signs a short-lived internal context, and forwards the request to hosted Relay.

Browsers and external API clients should not call the hosted Relay service directly.

Metering metadata

Trusted upstream control planes can receive safe numeric Relay response metadata for selected provider/model identifiers, wait time, token estimates, reported token totals, and configured cost when available. These values do not include prompts, response bodies, provider credentials, admin tokens, or cookies.

This overview is not a provider-compatibility guarantee. Only OpenAI-compatible upstream behavior is currently implemented.