Integrations · Anthropic
Guild agents call Anthropic’s Claude models through task.llm, with no API key in agent code. Guild holds the credential server-side, checks your model policies on every call, and attributes spend to the workspace, agent, and user that made it.
Book a demo
See how teams govern agents that use Anthropic.
Start free
Connect Anthropic and scope your first agent.
One model name, three ways to reach it
Writeclaude-sonnet-4-6 once, in a policy or in llmPreferences. Guild sends it to the Anthropic API, AWS Bedrock, or OpenRouter, depending on which credential your policies select, and maps it to that provider’s own model ID. Prompt caching is added for you unless your request sets its own cache breakpoints.
How it works
1
Add a credential
In Access & setup > Models & providers, click Add API key and choose a provider that serves Claude models. Check Anthropic under Models. On a managed account, you can skip this while Guild holds a managed Anthropic key.
2
Write a model policy
Bind the credential’s Anthropic access to the account, a workspace, or an agent, and list the models it may call, such as
claude-sonnet-*.3
Call it from task.llm
Name
"anthropic" in llmPreferences, or leave preferences out and let your policies choose. Guild resolves the credential at runtime.Every Claude call goes through your policies
Agents never hold the key. Guild stores the credential server-side and shows only a masked value, so you can rotate it without touching agent code or the model policies bound to it. Policies are an allowlist: a workspace, agent, or installed agent can call a Claude model only if a rule allows it. Set a daily token limit to cap spend, and see each call by workspace, agent, and user in Usage. A raw API key in an agent’s environment reaches every model the key can. A policy reaches only the models you name.About Anthropic models on Guild
Inference providers
You can reach these models through the Anthropic API itself or through a third-party provider.
Write the canonical model name, such as
claude-sonnet-4-6, everywhere in Guild. Guild maps it to each provider’s own model ID.
Models
Guild prices and recognizes these Anthropic model IDs. A policy or preference can also name any other model your credential can reach. Third-party providers route more models than this list, and their catalogs change; see each provider’s page for what it serves.Set up Anthropic
On a managed account, agents can use Anthropic models without a credential, as long as Guild holds a managed key for Anthropic. To use your own Anthropic account instead, add a credential. Adding your first credential switches the whole account to bring your own key (BYOK).1
Open Models & providers
Click Access & setup in the left nav, then Models & providers. In an organization, only admins can open it.
2
Add a credential
Click Add API key and choose an inference provider from the table above.
3
Enter the provider's secret
Give the credential a Name and paste your provider’s API key. AWS Bedrock asks for an IAM role and region instead.
4
Choose Anthropic
Under Models, check Anthropic. Keep
claude-sonnet-4-6 as its default model or enter another from the list above. Then click Add Key.--models "claude-sonnet-*" limits a policy to matching models:
Use it from an agent
Agent code never names a credential. Guild resolves the call against the workspace owner’s settings. To ask for Anthropic explicitly, put it inllmPreferences:
claude-opus-5-5. The second falls back to the default model of the matching policy. Preferences are strict: if no credential or policy allows any of them, the call fails rather than using another publisher. See LLM preferences.
Notes
- Guild adds prompt caching to Anthropic calls automatically, unless your request sets its own cache breakpoints.
- When a Claude model uses adaptive thinking, Guild requests summarized thinking so the session can show reasoning progress.
- The Claude Code runtime driver calls the Anthropic API directly through the runtime, so it needs an Anthropic credential or managed Anthropic access.
- On Bedrock, Guild passes only the
anthropic-betaflags Bedrock accepts, and drops the rest.
Frequently asked questions
Can Guild agents use Claude without my own Anthropic key?
Can Guild agents use Claude without my own Anthropic key?
Yes, on a managed account, when Guild holds a managed key for Anthropic. Usage then draws from your Guild tokens balance. Adding any credential switches the whole account to bring your own key (BYOK).
Can I run Claude through AWS Bedrock instead of the Anthropic API?
Can I run Claude through AWS Bedrock instead of the Anthropic API?
Yes. Add an AWS Bedrock credential and check Anthropic under Models. Bedrock serves current Claude models in all four supported US regions.
Will Guild switch to another publisher if no policy allows Claude?
Will Guild switch to another publisher if no policy allows Claude?
No. Preferences are strict. If no credential or policy allows any of an agent’s preferences, the call fails rather than quietly using another publisher’s model.
What does the Claude Code runtime need?
What does the Claude Code runtime need?
An Anthropic credential or managed Anthropic access. The Claude Code runtime driver calls the Anthropic API directly through the runtime.
Put a governed agent on Anthropic this week
Book a demo
See how teams govern agents that use Anthropic.
Start free
Connect Anthropic and scope your first agent.