Anthropic

Priority Tier is not on this bill. Priority Tier dollars are absent from the Admin Cost Report this connector calls. That usage is on Anthropic's usage report, which Meridian does not pull. (Usage and Cost API)

Connection steps are in the Anthropic connector guide. This page is only attribution.

What you set up

1. Connect Anthropic with an Admin key, using the connector guide.
2. In the Anthropic console, give each agent its own workspace. The default allowance is 100 workspaces per organization, and archived workspaces do not count toward it. (Workspaces)
3. Ask Onaro to turn on workspace splitting. During Early access a platform admin does this with you. Write to support@onaro.io. The Source identities screen shows the cutover date. It does not include a switch.
4. On that screen, under Anthropic workspaces, map each workspace to an agent and a department. If you pick an agent and leave the department empty, Meridian uses that agent's department.
5. Create the agents first, under Agents & allocation, and the departments under Governance.

The cutover is the first UTC date Meridian writes one row per workspace. Dates before the cutover stay one row per day and model. A re-sync of those dates keeps that shape. A date is never stored both ways. If you already have Anthropic rows, the cutover is tomorrow, or the day after a locked month that would contain tomorrow. Days already stored in the open month stay combined. If you have no Anthropic rows yet, the first pull, about 30 days, is split from the start, except days inside a locked month, which are skipped.

What Meridian receives

Meridian calls Anthropic's Admin Cost Report, grouped by day. (Get Cost Report)

While splitting is off, and for every date before the cutover, Meridian stores one charge per UTC day and model. Token counts on those rows are zero. Workspace ids are not used to split the row.

On and after the cutover, Meridian asks for workspace as well as model and stores one charge per UTC day, model, and workspace. Amounts are dollars, converted from the cents Anthropic reports.

Anthropic's default workspace has no workspace id in the cost report. Meridian lists that bucket as Default workspace.

The cost report's groups are the model description and, when you ask for it, the workspace. They are not the API key. The separate usage report can group by key. Meridian does not call that usage report. (Usage and Cost API)

How it's attributed

After the cutover, a workspace you have mapped is attributed to that agent and department. The row is mapped by you.

Before the cutover, and while splitting is off, the day-and-model total is unattributed until a person assigns it or a rule on Agents & allocation matches the vendor or the model. A rule does not replace a workspace you have already mapped. A person's assignment can replace a mapped row. It does not replace a row declared by a gateway or an OASA event, and it does not replace a row inherited from a tag or a seat file.

If gateway or OASA events for the same model and day are also coming in, Meridian scales the event rows that have no pool id to this bill so the dollars are not counted twice. The bill is the tie-out. The match is vendor, model, and day. A pool id stays at the measured amount.

What lands unattributed, and how to fix it

While splitting is off, the Anthropic total for each day and model is unattributed. Fix it only at that coarse grain: assign the rows, or add a rule. You cannot go back and split those dates by workspace.

After the cutover, an unmapped workspace stays unattributed. The inbox reason is "This Anthropic workspace is not mapped to an agent or department." Map it on Source identities and save. Meridian applies the mapping to unlocked dates. A locked month is not rewritten. Later drafts show an adjustment.

Default workspace uses the same reason until you map it. Mapping it assigns the whole default workspace to one agent and department. It does not divide that workspace across agents.

Several agents in one workspace stay one bucket. The cost report cannot split them. Give each agent a workspace, or send the calls through a gateway or OASA events.

Limits

• The cost report does not group dollars by API key. (Usage and Cost API)
• metadata.user_id on a Messages request is not a cost-report dimension. It does not show up on this bill. (Messages)
• Priority Tier dollars are absent from the cost report. Priority Tier usage is on the usage report, which Meridian does not call.
• Token counts on these cost rows are zero.
• Once a cutover date is recorded, splitting cannot be turned off. That would write a second copy of the same dollars.
• While splitting is off, a re-sync can refresh the amount on a date you have already locked. The locked chargeback file is not rewritten. Once splitting is on, sync skips dates inside a locked month.
• Claude on Amazon Bedrock is not this connector. See AWS Bedrock.