Anthropic (usage and cost) + Memtro

What did we spend on the Claude API this week, and which workspace uses most tokens?

This connects your Anthropic organisation's Admin API for usage and cost. It never calls a model. Memtro reads daily cost in USD by workspace and line item, token usage by model, workspace and API key, workspaces, members and the names of API keys, never a key value or hint. When asked and once an administrator has granted the action by name, it can invite people by email, change or remove members and roles, and create or rename workspaces. Archiving a workspace is permanent and stops its API keys working. Claude Enterprise on claude.ai is not covered.

In Memtro

What you can do with Anthropic (usage and cost) in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Anthropic (usage and cost) tool, reads what it needs, and answers with the source cited.

What it does

  1. 01Reads daily cost in USD per workspace and line item, such as model, web search and code execution, over up to 31 days
  2. 02Reads token usage per model, workspace, API key or service tier, including cache reads and writes, never per person
  3. 03Lists workspaces, organisation members with name, email and role, and one workspace's members with their workspace role
  4. 04Lists API keys by name only, with status, workspace, who created each and expiry, never a key value or hint
  5. 05When asked and granted, invites someone by email, which Anthropic sends, cancels invites, and changes or removes organisation and workspace members and their roles
  6. 06When asked and granted, creates, renames or recolours workspaces, and permanently archives a workspace, which stops its API keys working within seconds

Acts when asked

When you ask it to

These tools change something in Anthropic (usage and cost). The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.

  1. 01Invite someone to the Anthropic organisation by email with a chosen role (Anthropic emails them)
  2. 02Cancel a pending Anthropic organisation invite
  3. 03Change a member's Anthropic organisation role
  4. 04Remove a member from the Anthropic organisation
  5. 05Create an Anthropic workspace
  6. 06Rename or recolour an Anthropic workspace
  7. 07Archive an Anthropic workspace permanently: its API keys stop working
  8. 08Add an organisation member to an Anthropic workspace with a chosen role
  9. 09Change a member's role in an Anthropic workspace
  10. 10Remove a member from an Anthropic workspace

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Anthropic (usage and cost), choosing the same kinds; the tab shows Anthropic (usage and cost)'s own steps. Each event can start a job, with the event as its input. Anthropic (usage and cost) signs every delivery, and one whose signature does not check out is refused before it is read.

Events and webhooks
  • 01A session started running
  • 02A session is waiting for input
  • 03A session reached its budget and paused
  • 04A session hit a transient error and is retrying
  • 05A session terminated
  • 06A sub-agent thread is waiting for input
  • 07A sub-agent thread terminated
  • 08An outcome evaluation iteration ended
  • 09A session was deleted
  • 10An agent was created
  • 11A new agent version was published
  • 12An agent was archived
  • 13A scheduled deployment paused
  • 14A scheduled deployment resumed
  • 15A scheduled run started
  • 16A scheduled run created its session
  • 17A scheduled run failed
  • 18An environment was updated
  • 19An MCP OAuth credential could not be refreshed
  • 20A memory store was created
  • 21A memory store was deleted
In practice

Ask it like you would a colleague

Once Anthropic (usage and cost) is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.

Anthropic (usage and cost) + Memtro
  • What did we spend on Claude last week?

  • Which workspace used the most tokens in the last 30 days?

  • How many cache reads did each model have in the last 7 days?

  • Which keys are still active in the prod workspace?

  • Invite dan@acme.com to the organisation as a developer.

01

The weekly Claude bill

Priya Sharma, CTO at BigCo, asked what the team spent on Claude last week and which workspace cost most. Memtro read the daily cost report per workspace and line item and named the workspace with the highest total.

02

A new engineer starts

Dan Fletcher, security lead at Acme Ltd, asked Memtro to invite Maya Okafor as a developer. Memtro sent the invite with that role, and Anthropic emailed Maya a link. Once she accepted, Dan asked for her to be added to the prod workspace as a developer, and Memtro did that too.

Teams

Where it fits

The teams that lean on Anthropic (usage and cost) most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in Anthropic (usage and cost) is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.

Also in Engineering and operations

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withAdmin API key
  1. 1

    In Anthropic, open platform.claude.com → Settings → Admin keys. An ordinary inference key (sk-ant-api…) will not work here.

  2. 2

    Create an admin key named for Memtro, with an expiry, so you can revoke it. Admin keys have no scopes, so Memtro changes members, invites or workspaces only when an administrator grants that. Copy it, as it is shown once.

  3. 3

    In Memtro, open Connections → Anthropic (usage and cost) and paste it into Admin API key. Memtro never calls a model with it.

  4. 4

    Ask: "What did we spend on Claude last week?"

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Anthropic (usage and cost) tools are the same everywhere.

FAQ

Questions

Can Memtro change anything in Anthropic (usage and cost)?+

Only when you ask, and only what it has been granted: invite someone to the Anthropic organisation by email with a chosen role (Anthropic emails them); cancel a pending Anthropic organisation invite; change a member's Anthropic organisation role; remove a member from the Anthropic organisation; create an Anthropic workspace; rename or recolour an Anthropic workspace; archive an Anthropic workspace permanently: its API keys stop working; add an organisation member to an Anthropic workspace with a chosen role; change a member's role in an Anthropic workspace; remove a member from an Anthropic workspace. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

Who can use a Anthropic (usage and cost) connection?+

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Does Memtro store my Anthropic (usage and cost) data?+

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

How do I connect Anthropic (usage and cost)?+

Admin API key. In Anthropic, open platform.claude.com → Settings → Admin keys. An ordinary inference key (sk-ant-api…) will not work here.

Can Anthropic (usage and cost) start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Anthropic (usage and cost), choosing the same kinds; the tab shows Anthropic (usage and cost)'s own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.

Connect Anthropic (usage and cost) in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time