Working with the Anthropic API: Console, Models, BYOK & Costs

Last verified: September 2026. The API is where Claude stops being a chat window and starts being infrastructure. Four deep dives, one hub — the developer console, every model identifier, the subscription-vs-API cost crossover, and the bring-your-own-key strategy that keeps multi-provider stacks from breaking.

The console: your developer home base

The Anthropic Console (platform.claude.com) is where the API work actually happens — creating API keys, managing billing, monitoring usage, setting up workspaces, and navigating the developer dashboard. Start here if you haven’t touched the API side yet.

→ Anthropic Console: Developer Quickstart Guide (2026) — API keys, billing, usage monitoring, workspaces.

The models: every identifier, decoded

Every current Claude API model string — claude-fable-5, claude-opus-4-8, claude-sonnet-4-6, claude-haiku-4-5 — with context windows, per-token pricing, and when to use each. The one to bookmark; you’ll come back to it every time a new model drops and your code needs the right string.

→ Claude API Models: Complete 2026 Identifier Guide — model strings, context windows, per-token pricing, usage guidance.

The money question: API vs subscription

Subscription (Pro/Max) for interactive daily use; API for automation, building, and irregular usage. Here’s the cost crossover — and what the API adds that subscriptions don’t. The honest math on which billing shape fits your workload.

→ Claude API vs Subscription: Which Is Cheaper? (2026) — the cost crossover and what the API adds.

The multi-provider play: BYOK on OpenRouter

How to wire bring-your-own-key provider integrations on OpenRouter across dozens of providers without breaking your stack — prioritization, fallback chains, and per-agent configuration. For the builders running more than one model behind their agents.

→ BYOK on OpenRouter: Provider Keys, Prioritization, and Fallback Strategy — provider keys, prioritization, fallback chains.

Four deep dives, one hub. The console to get set up, the model identifiers to wire it right, the cost math to bill it right, and BYOK when one provider isn’t enough.