Connect Claude to Anthropic

List the Claude models this API key can call, newest first, with each model's id, display name, release date, context window and maximum output tokens. Call this before create_message or count_tokens whenever a model id is not certain - this connector deliberately does not carry a hard-coded list of model names, because Anthropic's roster changes faster than a file in a repository can. Free, and the cheapest proof that the key works.

Read one model by its id: display name, release date, context window, maximum output tokens, and the capability flags saying whether it accepts images or PDFs, supports extended thinking, structured outputs, citations, code execution or the Batch API. Use it to check that a model supports a feature before building a request around that feature, and to confirm an id from list_models is still available to this key. A 404 means the id does not exist for this key - call list_models to see what does.

Count how many input tokens a message request would use, without sending it and without being billed for the completion. Takes the same `model`, `messages`, `system` and `tools` that create_message takes, so the honest way to use it is to build the request, count it here, and only then decide whether to spend it. A read, because nothing is created and nothing is charged. Returns a single input_tokens number; it does not predict output tokens, which are the larger part of the cost of most calls.

List the organization's workspaces with their ids, names, display colours and archive state. Needs the separate Admin API key, not the ordinary one - without an admin_key credential this call is refused before it is sent. The `wrkspc_…` ids it returns are what usage_report and cost_report take to break a report down by workspace. The Admin API is unavailable to individual accounts; on one of those this returns nothing useful no matter which key is pasted.

List the organization's API keys as records - id, name, status, partial key hint, which workspace each belongs to and who created it. It does not and cannot return key values; Anthropic shows those once, at creation. Needs the separate Admin API key. The `apikey_…` ids are what usage_report takes to attribute token spend to a particular key, which is the usual reason to call this.

Token usage for the organization over a time range, in buckets, split into uncached input, cache reads, cache writes and output tokens. This is the accurate number - far better than adding up what individual responses reported. Group by "model", "workspace_id", "api_key_id" or "service_tier" to see where the tokens went; filter with models, workspace_ids or api_key_ids to narrow it. Needs the separate Admin API key. Bucket limits are Anthropic's: 1d allows at most 31 buckets per call, 1h at most 168, 1m at most 1440 - ask for a range that fits, or page with `page` when has_more comes back true. For money rather than tokens, call cost_report.

What the organization was actually billed, in USD, bucketed by day. Prefer usage_report when the question is about tokens and this when the question is about money. Group by "workspace_id" to attribute spend to a team, or "description" to see it split by line item - grouping by description is also how web search and code execution charges become visible, since they are not token usage. Needs the separate Admin API key. Daily buckets only; Anthropic rejects any other bucket width here. Priority Tier spend is billed differently and does not appear at all - track that through usage_report instead.