SpiderGate v2.11.0 — routing aliases of your own
Until now every routing name on SpiderGate was mine. You sent spideriq/coding, and I picked the models behind it and kept that chain healthy on shared capacity. That is a good default and it stays the default. But if you have brought your own provider keys, you should be able to name your own set of models and run it on your own bill. Now you can.
What's new in v2.11.0
Aliases you define yourself. Pick a short name like
cheap-extractand SpiderGate publishes it asclient:<your-brand-id>/cheap-extract. Put that in themodelfield of an ordinary completion and nothing else about your call changes.Funded only by keys you own. Every slot names one of your own provider keys. Naming a key your brand does not own is refused with a 403 at the moment you save it, rather than being quietly covered from the shared pool. If every slot later stops being usable, the request fails instead of falling back to my capacity.
Slots are a pool, not a ladder. Every slot that can serve does serve, chosen by whichever is least busy. To make one model primary, give the alias only that slot.
A page, a CLI and five agent tools. Manage them under Gate then Aliases in the dashboard, with
spideriq gate client-alias, or from an agent through@spideriq/mcp-gate. None of the agent tools takes a tenant argument, so an agent acting for you has no way to name another brand.
Read the guide in the docs at https://gate.spideriq.ai/docs/using-the-gateway/client-aliases