Integrations · Meta
Guild agents call Meta’s Muse and Llama 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 Meta.
Start free
Connect Meta and scope your first agent.
Muse from Meta, Llama from OpenRouter
The Meta API serves Muse models and speaks the OpenAI Chat Completions format. Guild reaches it through its unified LLM proxy. OpenRouter serves both families: Muse undermeta/ and Llama under meta-llama/.
How it works
1
Add a credential
In Access & setup > Models & providers, click Add API key and choose a provider that serves Muse and Llama models. Check Meta under Models. On a managed account, you can skip this while Guild holds a managed Meta key.
2
Write a model policy
Bind the credential’s Meta access to the account, a workspace, or an agent, and list the models it may call, such as
muse-*.3
Call it from task.llm
Name
"meta" in llmPreferences, or leave preferences out and let your policies choose. Guild resolves the credential at runtime.Every Muse and Llama 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 Muse and Llama 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 Meta models on Guild
Inference providers
You can reach these models through the Meta API itself or through a third-party provider.
Write the canonical model name, such as
muse-spark-1.1, everywhere in Guild. Guild maps it to each provider’s own model ID.
Models
Guild prices and recognizes these Meta 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 Meta
On a managed account, agents can use Meta models without a credential, as long as Guild holds a managed key for Meta. To use your own Meta 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 Meta
Under Models, check Meta. Keep
muse-spark-1.1 as its default model or enter another from the list above. Then click Add Key.--models "muse-*" 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 Meta explicitly, put it inllmPreferences:
muse-spark-1.2. 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 reaches the Meta API through its unified LLM proxy. There is no raw passthrough route for Meta, unlike Anthropic and OpenAI.
Frequently asked questions
Can Guild agents use Meta models without my own Meta key?
Can Guild agents use Meta models without my own Meta key?
Yes, on a managed account, when Guild holds a managed key for Meta. Usage then draws from your Guild tokens balance. Adding any credential switches the whole account to bring your own key (BYOK).
Can I run Llama models on AWS Bedrock?
Can I run Llama models on AWS Bedrock?
No. Bedrock lists Llama models, but Guild doesn’t route Meta models through Bedrock. Use OpenRouter.
Can I run Meta models on Fireworks AI?
Can I run Meta models on Fireworks AI?
Not today. Meta is a publisher you can check in the Fireworks AI form, but no Meta models are on its list.
Is there a raw passthrough route for the Meta API?
Is there a raw passthrough route for the Meta API?
No. Meta calls go through the unified LLM proxy, unlike Anthropic and OpenAI, which also have passthrough routes.
Put a governed agent on Meta this week
Book a demo
See how teams govern agents that use Meta.
Start free
Connect Meta and scope your first agent.