Gateway overview Docs-first contract

One public surface for agents, tools, and model traffic

Backplane is the stable entry point for model traffic and MCP sessions. Docs now own the endpoint catalog, client setup, and authentication details.

Model path

Routed centrally

Tool path

Namespaced access

Skill path

Reusable records

Agents Public origin

Backplane Private routing

Start here

Choose what you want to connect

Backplane has two protected resources. Pick the one your client needs, then follow the setup guide for its token and request format.

For tools

Connect an MCP client to one Streamable HTTP resource and discover namespaced tools from every configured service.

For models

Use an OpenAI or Anthropic compatible API while Backplane keeps provider credentials, routing, and usage behind the gateway.

For Google clients

Native Gemini GenerateContent, model discovery, and the separate Antigravity subscription route.

Start with MCP for tools or the LLM proxy for model requests. Tokens are bound to that choice.

Use the setup guide for your coding agent or a custom OAuth client.

Copy a safe example, inspect the route reference, and keep access tokens in environment variables.

Provider routing, model aliases, usage capture, and compatible model APIs.

One managed tool gateway with upstream services and namespaced tools.

Reusable skill records, archive handling, and managed skill tools.

Configure coding agents and API clients to use Backplane.

Client tokens, open local mode, and public OAuth endpoints.