Use recipes on your own keys
Who this is for: Anyone who calls a ready-made name like spideriq/chat or spideriq/coding and wants to know which of them work on the keys in their vault, and which key would unlock the rest.
What this does: Shows you, recipe by recipe, which slots your keys fill, lets you add the key a locked recipe needs, and lets you copy a recipe into an alias of your own with Customize.
Before you begin
A recipe is a ready-made routing name (
spideriq/chat,spideriq/research, …). It lists one fallback slot per provider, in order. A request tries the slots in order and uses the first one your workspace has a key for.Slots are filled from your workspace's own keys first, then from keys a connected company shares with you, then from the community pool if your workspace shares a free key. A recipe with no slot you can fill is locked: the request returns
403 no_access.You can read recipes as any member of the workspace. Adding keys and creating aliases follow the usual vault and alias permissions.
Steps
1. Open the recipes
Go to app.spideriq.ai/dashboard/gate/aliases and open the Recipes tab. Each card is one recipe, marked Usable or Locked for this workspace. The tab next to it, Your aliases, holds the aliases you created yourself.
2. Read a recipe slot by slot
Open a recipe. Slots by provider lists every slot in the order a request tries them. Each slot says who serves it: Your key (with its number), Connected company, Community pool, or Locked with the provider whose key is missing. Sign-in only marks a provider that runs through its own sign-in app and is never used by a recipe.
3. Unlock a locked recipe
A locked recipe shows This recipe is locked and an Add API key button for the first provider that would fill a slot. Click it to add that key in the vault, or follow the provider's guide. One key of any listed provider is enough to make the recipe usable.
4. Copy a recipe with Customize
Click Customize on a usable recipe to create your own alias from it. The copy keeps the slots that run on keys your workspace owns. Slots served by a connected company or the pool are left out, and the form lists each one with the reason, because an alias of your own can only use your own keys. Give it a name and save it. Customize stays off while a recipe is locked.
5. Ask from an agent or the command line
Your agent gets the same answer as the page. With the SpiderGate skills installed, ask it to "list my SpiderGate recipes": it calls gate_recipes and says which recipe to use and which key would unlock more. From a terminal, run spideriq gate recipes, or spideriq gate recipes --usable for only the ones that work now. Neither ever prints a key.
Verify it worked
Back on the Recipes tab, the recipe you unlocked now reads Usable, and its first filled slot reads Your key. Send one request with it:
curl https://spideriq.ai/api/gate/v1/chat/completions \
-H "Authorization: Bearer $SPIDERIQ_TOKEN" \
-H "Content-Type: application/json" \
-d '{"model": "spideriq/chat", "messages": [{"role": "user", "content": "Say hello"}]}'A 200 means the recipe served on your keys.
Troubleshoot
Every recipe reads Locked? Your workspace has no key a recipe can use. Run setup, or click Add API key on the recipe you need.
A slot reads Never tried? The gateway does not route that provider from that slot. Add a key for another provider in the same recipe.
Customize is greyed out? The recipe is locked, so there is nothing of yours to copy yet. Add a key first.
My alias from Customize has fewer slots than the recipe? Slots served by a connected company or the pool cannot go into an alias of your own. The form named each one it left out.