Bring your own keys
SpiderGate runs on the provider keys your workspace brings. Setup tells you which keys to get, where to get them, and which ones are free. Share a free one with the pool if you want.
No key, no calls
A workspace with no key of its own can browse every model in the catalog. It cannot call one. Ask for a model your keys cannot reach and you get 403 no_access, and the error names the provider keys that would serve it, with a link straight to setup. Locked models stay on the Models page, so you can see what one more key would add.
403 no_access
None of your keys reaches this model. The error names the keys that would.
503 capability_unavailable
SpiderGate could not check your models just now. Send it again.
0 usable, 1,524 locked
What a workspace with no keys sees on the Models page, as of 4 November 2026.
Add API key
On every locked model. Add the key yourself, or invite the person who has it.
Where your request finds a key
Every request looks for a key in the same order. Your own keys first. Then keys your connected companies share with you, unless a key is kept private. Then the community pool of free keys, which you can draw on while you share at least one active free key of your own. Free keys are shared by default, and a workspace admin can switch that off.
1. Your own keys
The keys in your vault. Always tried first.
2. Connected companies
Run more than one company here? They can share keys. Any key can stay private.
3. Community pool
Free keys other workspaces chose to share. Yours to use while you share one too.
Never pooled
Paid keys and subscription keys. They are yours, full stop.
Six steps from zero to working
Setup at app.spideriq.ai/dashboard/gate/setup asks how you will use SpiderGate, what you already pay for, and which free keys you want, then walks you through adding each one with the same guide as the docs. Save and exit keeps your place, and a small bubble on every dashboard page brings you back. The last step shows how many models you can use and the Base URL to paste into your tools.
# Which ready-made names work on your keys, slot by slot.
spideriq gate recipes --usable
# Where setup stands, and the one next step.
spideriq gate setup statusFree keys we recommend
Each card shows the free allowance and whether the provider asks for a phone check or a card.
Ask a teammate
Their page has a guide, checks the key live before saving it, and never shows it back. No account needed.
Recipes
spideriq/chat and the rest have one slot per provider, so one key of any listed provider is enough.
Your agent
gate_onboarding_status and gate_recipes say the next step. An agent can suggest an invite; a person sends it.
Built, off by default
Two more pieces are built and switched off by default: platform jobs running on your own keys, and a daily budget for pool use. Today, platform jobs still run on our keys. We will say so here when either switch goes on.
Jobs on your own keys
Built, off by default. Today platform jobs run on our keys.
Daily pool budget
Built, off by default. Pool use has no daily cap switched on yet.