Skip to main content
OpenRouter is a third-party inference provider. It routes to models from every publisher Guild supports, so one OpenRouter key can reach all of them. Guild calls OpenRouter with your API key, and OpenRouter bills the calls to your account.

Publishers on OpenRouter

Guild refreshes its list from OpenRouter’s public model catalog every day, keeping the text models in these namespaces. Variants with a suffix after a colon, such as :free, aren’t listed. To see what’s available, browse OpenRouter’s models and drop the namespace: qwen/qwen3-coder becomes qwen3-coder.

Connect OpenRouter

1

Create a key

In your OpenRouter account, create an API key.
2

Start the credential

In Guild, click Access & setup in the left nav, then Models & providers. Click Add API key and choose OpenRouter from the menu.
3

Name it and paste the key

Give the credential a Name, such as Production, and paste the key into API key.
4

Choose publishers

Under Models, check each publisher this credential should reach. Keep or change the default model next to each one.
5

Save

Click Add Key.
One OpenRouter credential can reach every publisher at once. Check them all to use a single key for everything.

Model IDs

Write canonical model names, such as claude-sonnet-4-6 or deepseek-r1, in policies and llmPreferences, without the OpenRouter namespace. Guild adds the namespace for you. OpenRouter spells Claude versions with dots, so Guild maps claude-sonnet-4-6 to anthropic/claude-sonnet-4.6.

Pricing

OpenRouter bills your OpenRouter account at its own rates, and those rates change as OpenRouter and the model publishers update them. For current prices, check each model’s page on OpenRouter’s models list, and see OpenRouter pricing for how OpenRouter charges. Guild’s Usage pages estimate spend from Guild’s own price list, which can lag behind OpenRouter’s. For a model Guild hasn’t priced yet, the estimate uses a fallback rate. Your OpenRouter account is the source of truth for what you paid.
Last modified on October 20, 2026