What changes
| Behaviour | Hosted | BYO Anthropic |
|---|---|---|
| Who is billed | mapping.travel (counted against your Pro Max subscription) | You, by Anthropic, directly |
| Daily spend cap | Still enforced (cents) | Still enforced (cents, estimated from token counts) |
| Model selection | claude-opus-4-7, claude-haiku-4-5-20251001 | Any claude-* your account has access to |
| Prompt caching | Enabled | Enabled (Anthropic-native) |
Steps
Create the key in the Anthropic Console
console.anthropic.com → API Keys → Create Key. Name it “mapping-travel-agents”. Copy the value (
sk-ant-...).Store it in mapping.travel
Agents → [your agent] → Settings → LLM Provider. Switch to BYO Anthropic. Paste the key. Click Save — we validate it with a low-cost
messages.create ping before storing.Pick a model
Any Anthropic model your account has access to. We recommend
claude-opus-4-7 for the default planning path; switch to claude-haiku-4-5-20251001 for the fast path on routine cycles.Equivalent API call
byoKeySecretId, and never echoes the plaintext key back.
Security
- The key lives in the same vault as other workspace secrets (data-source credentials, Stripe webhook signing secrets).
- It is only visible to
OWNERandADMINusers; redacted (sk-ant-****1234) everywhere else, including the audit log. - Rotating the key: paste the new value over the old one — we re-validate before swapping.
Reverting to hosted
Switch the provider back to Hosted Anthropic in Settings. The BYO key is deleted from the vault; the audit log recordsAGENT_UPDATED with the provider change.
Related
- Agents overview — broader context.
- Cost and limits — caps are still enforced on BYO.
- Configuration reference — full field list.