Documentation / Integrations / Anthropic
Anthropic connector
Connect an Anthropic Admin API key so Meridian can pull Claude spend and usage for attribution and close.
AvailableMethod: API
Overview
Connect an Anthropic Admin API key so Meridian can pull Claude spend and usage for attribution and close.
Data pulled
- Daily cost by model from the Admin cost report; charges without a model, such as web search, are kept under their cost type
- Token counts are not provided by this path (recorded as zero)
- Persisted as source_type=api_sync
What gets attributed
Meridian reads the Anthropic Admin cost report and stores one row per day per model; charges without a model, such as web search, are kept under their cost type. Workspace splitting is off until you ask for it.
Until a workspace is mapped, its spend arrives unattributed in the attribution inbox (Agents & allocation → Unattributed), where you can assign it or create a rule that matches on vendor or model.
Attributing spend by workspace or project
Workspace splitting is available on request. Contact support@onaro.io. We enable it with you and confirm your first month's split together. Dates before that cutover stay as a daily total.
Authentication & credential storage
Meridian stores the following fields for this connector (values encrypted at rest):
api_key
- Credentials are encrypted with AES-256-GCM using a KMS-wrapped data encryption key (DEK) and stored in vendor_connections.credentials_encrypted.
- Meridian never returns the plaintext key after save. Revocation is disconnect: deactivate or delete the vendor connection — sync stops and the encrypted blob is no longer used.
- Requires an Admin API key (keys that include admin in the identifier). A standard inference key validates but cannot retrieve billing.
Sync schedule & behavior
Provider Admin APIs return daily buckets. Syncs automatically every 6 hours; manual sync anytime. There is no per-connection frequency setting.
Setup steps
- Create an Admin API key in the Anthropic console.
- In Meridian → Vendors, select Anthropic, paste the admin key, and label the connection.
- Run or wait for sync and verify spend_records.
Troubleshooting
- 403 on sync: replace a regular API key with an Admin key.
- 401: regenerate the admin key and reconnect.
Related
- Open Agent Spend Attribution (OASA) Specification
- Glossary
- Integrations hub
- Meridian Vendors (connect / disconnect)
Onaro Meridian is FinOps for agentic AI: the system of record that attributes, controls and books what AI agents spend.