Use the Anthropic SDK with Manifest
The official Anthropic Python and TypeScript SDKs accept a custom
baseURL. Point them at Manifest and your
messages.create calls (agents, chatbots,
tool-using apps) route through the cheapest capable model.
— models routed through Manifest over the last 30 days.
Why use the Anthropic SDK with Manifest
Claude is a top-tier model, but you don't always need it. Manifest lets you keep the Anthropic SDK ergonomics (the same message shape, the same streaming API, the same tool-use contract) while downshifting to cheaper models when the prompt allows.
- One baseURL swap, no SDK fork
- Cut Claude API costs by 40–70% across your app
- Keep the Anthropic message format: streaming, tool use, vision
- Fall back to other providers when Anthropic rate limits hit
- Per-app spend caps and audit logs in the dashboard
- Open source, self-hostable, no lock-in
Setup in 60 seconds
Pass the Manifest base URL and key when constructing the client. The Anthropic SDK
auto-appends /v1/messages, so the base
URL should not include /v1.
Install the Python SDK and create a client pointing at Manifest:
from anthropic import Anthropic
client = Anthropic(
base_url="https://api.manifest.build",
auth_token="mnfst_YOUR_KEY",
)
message = client.messages.create(
model="auto",
max_tokens=1024,
messages=[{"role": "user", "content": "Hello"}],
)
Install the TypeScript SDK and wire it to the Manifest endpoint:
import Anthropic from "@anthropic-ai/sdk";
const client = new Anthropic({
baseURL: "https://api.manifest.build",
authToken: "mnfst_YOUR_KEY",
});
const message = await client.messages.create({
model: "auto",
max_tokens: 1024,
messages: [{ role: "user", content: "Hello" }],
});
https://api.manifest.build
mnfst_YOUR_KEY
auto
Anthropic SDK tokens processed on Manifest
Models in use
# Model |
Auth type | Tokens / last 30 days |
|---|---|---|