ENTERPRISE AI GATEWAY / 001

Give every AI request
one gateway.

Teapot Router gives GPT and Claude Code one gateway. Configure fallback channels, trace request costs, and inspect response times.

two model lanes auditable billing
Teapot Router / MODEL LANES OVERVIEW
02model lanes
GPT laneResponses · Chat Completions
SUPPORTED
Claude Code laneSonnet · Opus · Haiku
SUPPORTED
encrypted transit418 STORYsee current prices

THE PRODUCT / 002

Only the two lanes your team needs.

No model marketplace. No bundle maze. One endpoint for the engineering intelligence your team already uses.

01 / OPENAI
G

GPT

A general reasoning layer for product, data, and Agent teams. Responses, Chat Completions, and Codex workflows included.

Loading models…
OPENAI_BASE_URL ↗
02 / ANTHROPIC
C

Claude Code

A terminal gateway for enabled Sonnet, Opus, and Haiku models, including supported caching and tool calls.

Loading models…
ANTHROPIC_BASE_URL ↗

WHY Teapot Router / 003

A better route for every request.

Availability, latency, and cost are decisions you can inspect and tune, whether you work alone or with a team.

01Availability

Keep a way through

Configure multiple upstream channels. When one fails, the gateway can retry an eligible route instead of stopping at the first error.

Configured routes → eligible retry
02Latency

Choose with response data

Inspect request duration and channel response times, then adjust route priority and weight. Route choice follows your configuration, not an unverified speed promise.

Response time → route priority
03Cost

Know what each call costs

See configured model rates alongside request level token use and charges. Check actual spending before changing models or budgets.

Model rates → usage record

THE TEA MENU / 004

Pricing is not a black box.

Compare the configured upstream reference price with Teapot Router's standard account price. The displayed discount follows the standard group ratio; usage records remain the source of truth.

Official reference→Teapot Router price

Loading current prices…

USD / 1M tokens · Official is the configured upstream reference; Teapot Router uses the standard group ratio. Caching and request type can change the final charge; Usage is the source of truth.

THE HANDOFF / 005

Plug into the workflow you already have.

Use a supported SDK with Teapot Router by changing its endpoint and credentials.

Teapot Router / ONBOARDING READY IN 3 STEPS
01

Open an account

Create an account, add balance, and generate an API key in the workspace.

02

Replace the endpoint

Change one base URL for OpenAI; set two environment variables for Claude Code.

03

Read the ledger

Every request has a model, token, cost, and timestamp for reconciliation.

TEAM READYWORKSPACE + API KEY
teapot_setup.sh
# Teapot Router · inspired by RFC 2324
# Claude Code
export ANTHROPIC_BASE_URL="https://api.teapotrouter.com"
export ANTHROPIC_AUTH_TOKEN="rl_your_token"

# OpenAI SDK
client = OpenAI({
  base_url="https://api.teapotrouter.com/v1",
  api_key="rl_your_token",
})
OPENAI + CLAUDE CODECOMPATIBLE SDK
Docs / 01—06

Need the exact steps?

Follow the six guides from account setup to your first request, with checks and troubleshooting along the way.

Read the guides

FOR PROCUREMENT / 006

Built for engineers.
Legible to finance.

Prepaid balanceAdd balance to an account before making API requests.

Request recordsReview model, token use, charges, and duration for each logged request.

Payment historyCheck completed top-ups and usage in the workspace.

THE SMALL PRINT / 007

The boundaries are written down.

What does the Teapot Router name mean?

It tips its hat to HTTP status 418 “I'm a teapot”, the beloved easter egg from a 1998 IETF April Fools' RFC. A teapot doesn't grow tea — it pours it, which is exactly how a model gateway should behave.

Is Teapot Router a model provider?

No. Teapot Router is a gateway for GPT and Claude Code. Available models and behavior depend on the configured upstream channels.

How are prices calculated?

The table estimates base rates from the current gateway configuration. Group rates, caching, and other usage details may change the final charge, which appears in your workspace.

Can we keep our existing SDKs?

Yes. Keep your existing engineering workflow and let Teapot Router handle the gateway connection.

How does billing work?

API usage is charged against an account balance. The workspace shows top-ups and request usage. Contact us to discuss company purchasing needs.

THE POT / WHY THIS NAME

Why a teapot?

The name comes from HTTP status 418 — “I'm a teapot”, an April Fools' RFC from 1998 that developers adopted as the internet's favourite easter egg. It lets us say three serious things:

The pot doesn't grow teaA teapot brews and serves; it never grows the leaves. Teapot Router doesn't train models either — it pours GPT and Claude Code, steadily, into your code.

Short and stoutThe RFC itself says the teapot's response body may be short and stout. Short means no ego; stout means no tipping over. That is a gateway's job description.

418 is our winkThe 418 reference is a story and a developer easter egg. Teapot Router keeps account and model API responses focused on their real contracts.

HTTP 418 / brand folklore · API contracts stay ordinary

START WITH A CONVERSATION / 008

Give the next
model call to Teapot Router.

Leave a work email to discuss enterprise access, pricing, or onboarding.

Online enquiries are temporarily unavailable. You can create an account or try again later.

Prefer email?[email protected]

Announcements

Loading announcements…