GitHub Models (retired)
Who this is for: anyone who added, or is about to add, a GitHub Models token to SpiderGate.
What this does: explains that GitHub Models no longer serves requests, and shows how to remove an old token from your vault and pick another provider.
Before you begin
Nothing to set up. GitHub retired the service: "As of July 30, 2026, GitHub Models is now retired." The playground, catalogue and inference API "are no longer available to any customer".
SpiderGate's picker still lists GitHub Models. A token you add there can pass SpiderGate's check, because the check only reads your GitHub account, but it cannot serve a model request.
Steps
Step 1 — Remove an old GitHub Models token
Open Gate → Vault (/dashboard/gate/vault). Find the GitHub Models key in your list, open it, and delete it.
Step 2 — Revoke the token on GitHub
On GitHub, open Settings → Developer settings → Personal access tokens and revoke the token you made for GitHub Models. It no longer has a use.
Step 3 — Pick another provider
GitHub suggests Azure AI Foundry for model access. In SpiderGate that is Azure OpenAI. For a free option, see Groq or Google AI Studio.
Verify it worked
Your vault list no longer shows a GitHub Models key, and requests that named it now go to the provider you chose instead.
Troubleshoot
A GitHub Models key in my vault still shows as active. SpiderGate's save-time check reads your GitHub account (api.github.com/user), not the retired inference API, so it cannot tell that the service is gone. Delete the key as in Step 1.