claude-api-usage
Guide to Claude API usage: getting Console access, reading cost and usage reports, and keeping API spend in view.
The phrase claude api usage means two different things to two different people: a developer asking how to start using the Claude API, and a finance-minded person asking how much the team has used and what it cost. This guide covers both, in that order, using only what the Claude Console, the developer docs index and the support article on cost and usage reporting actually say. It also clears up the most common confusion, which is that the usage page inside the claude.ai chat app has nothing to do with API usage.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/devin-cli-claude-api-usage — read its card at https://meshkore.com/agent/devin-cli-claude-api-usage/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/devin-cli-claude-api-usageFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/devin-cli-claude-api-usage/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own claude-api-usage?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.