Anthropic through Squiid

What Anthropic is

Anthropic builds Claude, a model family aimed at careful reasoning, long context windows and tool use. The Messages API handles chat and multi-turn tool calling, prompt caching cuts the cost of resending a large system prompt or codebase, and batch processing runs large jobs at a lower rate. Claude is also the model behind Claude Code, which is why so many agent-written projects end up calling the same API from inside the product they are building.

In an AI-coded application Claude usually takes the jobs where being wrong is expensive: reviewing a diff, summarising a contract, extracting structured data from a long PDF, or driving an agent loop that calls your own functions. Teams often run Claude alongside a cheaper model, routing short classification calls to one provider and long-context work to Anthropic, which means two more keys to manage unless something is holding them for you. Long context is the other draw, since a single request can carry an entire schema file, a set of migrations and the diff you want reviewed without a retrieval step in between.

Why connect it through Squiid

Squiid provisions Anthropic access instantly, keeps the upstream key in its own custody and routes your calls to https://api.squiid.io/v1/anthropic/... with Authorization: Bearer $SQUIID_API_KEY. The official Anthropic SDKs work by pointing their base URL at the gateway (gateway convention), so an existing integration changes by one line. Token usage is metered per model against your prepaid balance, appears next to every other service in one dashboard, and arrives on one monthly invoice. Rotating the Squiid key cuts off every agent at once if a laptop goes missing. Batch jobs draw on the same balance as interactive traffic, so one number tells you what the month costs.

• One account, one key, one bill, one dashboard. Anthropic sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Anthropic credentials. Your code carries SQUIID_API_KEY, so ANTHROPIC_API_KEY, ANTHROPIC_BASE_URL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Anthropic costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Claude models through the Messages API on your Squiid key
• Prompt caching and batch requests passed through
• Per-model token spend next to your other services
• Anthropic SDK support by base URL swap
• Anthropic list pricing, no Squiid margin

How to connect Anthropic

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces ANTHROPIC_API_KEY, ANTHROPIC_BASE_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/anthropic/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Anthropic charges per input and output token by model, with reduced rates for cached and batched tokens, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Anthropic usage, with no markup and no per-request margin.

Anthropic has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Anthropic usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Nothing to move: Anthropic is usage-metered, so leaving means creating your own Anthropic key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Anthropic's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Anthropic through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Anthropic usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.