Claude API

Building something that calls Claude: model ids, pricing, streaming, tool use, prompt caching, token counting. Reach for it before guessing an API detail from memory.

A situation it fits

Your app sends Claude the same 40kb of context on every request and the bill is climbing. You want to know whether that context can be cached.
Claude API. mcp-builder is the trap, because 'connecting Claude to my system' sounds like MCP. MCP is for giving Claude tools to reach outward. Here your code calls Claude, and the question is about a request parameter: prompt caching, its minimums and its TTL. That is claude-api, which exists precisely so nobody answers a pricing question from memory.

2 scenarios in the bank answer to Claude API. The rest are in the game.

Skills it gets confused with

These share a family with Claude API, which is another way of saying they are the ones you might reach for by mistake.

Knowing what Claude API does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Claude API is part of anthropics/skills. Licence: Apache-2.0. The description above was written for this game, not taken from the skill.

← All skills