Quickstart

Create a gateway

Open the header Gateway selector. With no gateway yet, creation opens on its own; otherwise pick New Gateway from the selector. Name it and choose SaaS.Choose Private only when prompts must not leave your network. You then run the data plane yourself — Docker, Kubernetes or by hand, from the instructions the console generates — and paste its public URL. Deployment covers what that involves. Everything else in this guide is the same either way.

Connect a provider

Pick a provider, enter its credential, and Test connection before you save. A credential that fails here fails later as provider errors your callers see, so the test is the cheap moment to find out. Model providers has what each one asks for.

Create an application

Open Access → Applications and create an application. Add the provider you just connected. Its type follows — it now serves LLM traffic.Issue it a key. It is shown once. Copy it somewhere safe.

Use the Playground

Open the Playground and pick the application you just created. The Playground only lists applications created in Access. Pick one of the provider’s models, type a question, send. The request goes through the gateway you just created.

Read the trace

Status, model, latency, tokens, trace id, response. This is the shape of every row in Activity from now on.

The step that matters

The Playground request used the application you created. A caller outside the console still needs the snippet. Open Connect and copy it. It already carries the right URL, the right header, and the right model value for the application’s strategy. The provider’s credential never leaves the gateway. The application holds only its own key, and rotating one never touches the other.

from openai import OpenAI

client = OpenAI(base_url="https://<llm-host>/<application-slug>/v1", api_key="<application key>")

client.chat.completions.create(model="auto", messages=[{"role": "user", "content": "Hello"}])

import OpenAI from "openai"

const client = new OpenAI({ baseURL: "https://<llm-host>/<application-slug>/v1", apiKey: "<application key>" })

await client.chat.completions.create({ model: "auto", messages: [{ role: "user", content: "Hello" }] })

curl -X POST "https://<llm-host>/<application-slug>/v1/chat/completions" \
  -H "X-AG-API-Key: <application key>" \
  -H "Content-Type: application/json" \
  -d '{"model": "auto", "messages": [{"role": "user", "content": "Hello"}]}'

Clients that only take a base URL and an API key — OpenAI or Anthropic SDKs, Cursor, desktop chat apps — can send the same key as Authorization: Bearer or x-api-key instead. Nothing else about them changes.

The same gateway, for tools

The tool side has the same shape: something in the registry, an application that names it, a client pointed at its URL.

Add a server

Registry → MCP servers. Most of the catalogue is a credential decision, not an integration: either you supply one credential for everyone, or each caller connects their own account. Your own server or an OpenAPI document goes here too.

Create an application and add the server

On General. Its type follows — it now serves tool traffic. A key is issued when you create it and shown once; Auth is where you swap that for an identity provider instead.

Point a client at it

Connect has the snippet, already carrying the URL and the header.

claude mcp add --transport http TrustGate https://<mcp-host>/<application-slug>/mcp

{ "mcpServers": { "TrustGate": { "type": "http", "url": "https://<mcp-host>/<application-slug>/mcp" } } }

A call to a server nobody has signed in to does not fail blankly: it comes back asking for the account and naming who connects it — an administrator for a shared account, or the person the call is for. Connect an agent covers the rest, including writing the agent yourself.

Then

The five objects

Gateway, registry, application, access, policy — and the one question each answers.

Policies

A budget, a rate limit, a guardrail — attached to the application you just made.

Routing

A second provider as fallback, or a cheaper model for easy prompts.

MCP Gateway

The same gateway in front of tools.

Start here

Concepts

LLM Gateway

MCP Gateway

Policies

Operate

The step that matters

The same gateway, for tools

Then

The five objects

Policies

Routing

MCP Gateway

​The step that matters

​The same gateway, for tools

​Then

The five objects

Policies

Routing

MCP Gateway

The step that matters

The same gateway, for tools

Then