Cursor
Add the gateway as a custom standard API provider in Cursor.
Integrations
Cursor's Settings → Models screen lets you add a custom standard API provider. Point it at the gateway, paste a gw_ key, pick a model slug from the catalog.
Settings → Models → Standard API
text
Verify
- Open a chat in Cursor.
- Click the model picker.
- Choose one of the slugs you listed.
- Send a prompt — the response should arrive over the gateway.
You can confirm traffic is hitting the gateway by tailing its logs (bun run dev in the repo root). Each Cursor request shows up as a POST /v1/chat/completions with the resolved model slug.
Troubleshooting
- "Test API key" is not an authentication check — Cursor may probe
/v1/models, but that endpoint is public and does not validate the key. If the probe itself fails, check the base URL and network path. Confirm thegw_credential by sending a chat request to the protected/v1/chat/completionsendpoint. - Model picker shows the slug but errors on use — the slug exists in the gateway but is disabled. Enable it in the admin panel under Models.
- Cursor sends extra protocol-specific fields (e.g.
logit_bias) — the gateway translates what it knows and drops fields the upstream doesn't support. If you need that field specifically, file an issue.
Gateway URL: https://api.toygate.store