Skip to main content
LLM settings control which provider and credentials Guild uses when agents call task.llm. By default, agents use managed LLM access backed by your Guild tokens balance. You can switch to bring your own key (BYOK) by adding a provider API key. LLM configuration is stored on an account (your user account or an organization), not on individual workspaces. Sessions in a workspace use the LLM settings for that workspace’s owner account.

​
Open LLM settings

The console Settings panel lists LLM Settings after Credentials and before Usage.

​
Personal account

1

Open Settings

Click your profile in the top-left corner, then select Settings.
2

Go to LLM Settings

In the settings sidebar, click LLM Settings.
Direct URL: https://app.guild.ai/settings/llm-settings

​
Organization

Organization LLM settings apply to workspaces owned by that organization. Only organization admins can open this section.
1

Open your organization

Switch to the organization from the profile menu.
2

Open Settings

Go to Settings for the organization.
3

Go to LLM Settings

In the settings sidebar, click LLM Settings.
Direct URL: https://app.guild.ai/organizations/{org-name}/settings/llm-settings

​
Managed vs BYOK

ModeWhen it appliesBilling
ManagedNo active provider API keys on the accountLLM usage draws from your Guild tokens balance
BYOKAt least one active provider API keyCalls use your provider account; your Guild tokens balance is not consumed
The page shows your current mode as LLM Tier:
  • Managed () — Guild runs LLMs on your behalf using managed infrastructure.
  • BYOK (Bring Your Own Key) — Guild routes LLM calls through your default API key.
When you add your first API key, the account switches from managed to BYOK automatically. When you delete your last active key, Guild switches back to managed.

​
Add an API key

Click Add API key in the page header.
FieldDescription
ProviderAnthropic, OpenAI, or Gemini
NameA label you choose (for example, Production or Testing)
API KeyThe key from your provider console
DefaultWhether this key is the default for LLM calls. The first key you add is marked default automatically.
Guild stores keys securely and shows only a masked value in the table (first and last few characters).

​
Manage keys

The keys table lists each key’s provider, masked API key, created date, and creator. Use the row menu to:
  • Set as default — Use this key for LLM calls when multiple keys exist.
  • Delete — Archive the key. Archived keys appear when you filter to Archived keys.
Use Search and the status filter (All keys, Active keys, Archived keys) to find keys.
Deleting your last active key returns the account to managed mode. Deleting the default key promotes another active key to default if one exists.

​
Daily token limit

When you use BYOK, you can set a Daily token limit below the keys table. All LLM requests are rejected after the account exceeds this limit for the day. The limit resets at midnight UTC. Leave the field empty for unlimited usage. This limit applies to LLM usage on the account while BYOK is active.

​
Guild tokens balance

When the account is in managed mode, the page shows your Guild tokens balance. The balance is indicative and may not update in real time.

​
How agents use these settings

Agents do not embed provider API keys in code. At runtime, Guild resolves LLM configuration for each session from the workspace owner’s account settings. See LLMs for calling task.llm from agent code and Credentials for connecting third-party services agents use as tools.