---
title: "Anthropic"
description: "Scoped Anthropic API key access for AI agents"
url: "https://gazebohq.com/services/anthropic"
---

Anthropic API credentials are often consumed by coding assistants, batch analysis jobs, and production agent services. Those consumers should not inherit the same production key simply because they all call Claude. Establish provider-side workspace, key, spend, and access boundaries appropriate to the account, keep non-production credentials separate, and broker each secret through Gazebo only to the runtime that needs it. This makes the credential path reviewable without confusing a secret-delivery control with a model authorization system.

## Why manage Anthropic keys through Gazebo?

Sharing one Anthropic key means a compromised local tool, a runaway retry loop, or a leaked build log can affect every workload using it. The key’s provider-side configuration determines what requests it can make; Gazebo’s policy determines which agent may retrieve it. Use dedicated credentials where isolation is needed, compare Gazebo access records with Anthropic usage and billing information, and revoke at both layers during an exposure: disabling a profile stops future retrieval, while revoking the provider key invalidates copies already received.

## How it works

1. Create and label separate Anthropic credentials for development, evaluation, and production workloads before adding them to Gazebo.
2. Bind each stored credential to a profile for one named agent or automation; the profile should reflect a real deployment boundary, not just an informal task label.
3. The approved runtime calls get_credential through MCP, and Gazebo evaluates its policy before returning the selected secret.
4. Review allowed and denied retrievals with provider usage data and application request logs. Retrieval proves access was granted, not that a particular Claude request succeeded.
5. Remove a profile when a workflow ends. Rotate the Anthropic key as well if it could have been printed, forwarded to an untrusted tool, or persisted outside the intended runtime.

## Use cases

**Production vs development model access:** Make the capability split with Anthropic’s available account or credential controls, separate keys/projects, and application configuration; then map the development and production secrets to different Gazebo profiles. A profile prevents an unapproved agent from fetching a key, but it cannot restrict a broad key to a model after that key has been delivered.

**Prevent prompt injection credential leakage:** Retrieve downstream secrets only through a trusted tool path rather than embedding them in Claude messages or agent instructions. Ensure tool output and debug traces redact values, because a prompt-injected or compromised tool can still misuse a credential it legitimately receives. On suspicion, disable the profile and rotate the affected downstream secret.