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.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.
Related pages
- Models & providers for credentials, model policies, and the daily token limit
- LLMs for
task.llmand the unified LLM proxy - Usage for spend by model