Skip to main content
Cursor lets you override its OpenAI base URL and API key, which means you can point it at https://gateway.toolken.ai/v1. However, Cursor does not currently provide a way to send custom HTTP headers alongside those requests, so X-Toolken-Key never reaches the gateway.
Coming soon. Cursor support is not available yet. The steps below will not work until it ships.

​
Why it does not work yet

Toolken identifies your workspace from the X-Toolken-Key header on every request. Cursor’s current configuration model accepts a custom base URL and API key, but it does not expose a headers or equivalent field to attach additional headers to outbound requests. Without X-Toolken-Key, the gateway cannot authenticate the request.

​
What is coming

Toolken is adding server-side key management. Once it ships, you will be able to point Cursor at the gateway with a single key — Toolken handles provider routing and attribution on the server side with no custom headers required. The Cursor config will shrink to just a base URL and that one key. This page will be updated with a full step-by-step guide when support is ready.

​
Get notified

Want this sooner? Reach out at [email protected] and we will let you know when Cursor support lands.

​
Next

Claude Code

Claude Code forwards custom headers today — the Toolken integration is fully working.

Continue

Continue also supports custom headers and is fully working with Toolken.