Cursor model routing

Give Cursor a backup when one provider fails

Point Cursor at TEKIZ.AI. Use the same address for hosted routing, local Ollama, Tailnet models, and the OpenAI-compatible or Anthropic-compatible providers you connect.

Create API key Copy quickstart Coding-agent router Cursor guide

Cursor custom OpenAI endpoint

Use TEKIZ.AI as Cursor's OpenAI-compatible base URL with OPENAI_BASE_URL=https://api.tekiz.ai/v1 and a generated hosted key, or point Cursor at a local router on port 8790.

Works with Claude-style connections

When Cursor expects an Anthropic-compatible connection, TEKIZ.AI can use Anthropic or Dario access you have connected.

Keep working when an account is busy

Use more than one authorized API key so Cursor can continue through another working route when one key or provider reaches its limit.

Set up Cursor setup

export OPENAI_BASE_URL=https://api.tekiz.ai/v1
export OPENAI_API_KEY=sk_tekiz_your_generated_key

# Cursor: set the custom OpenAI-compatible endpoint to:
#   Base URL: https://api.tekiz.ai/v1
#   API key:  sk_tekiz_your_generated_key
#   Model:    tekizai/frontier
# Cursor stores this custom-provider connection in its Settings UI; it does
# not expose a supported provider configuration file to edit directly.

curl "$OPENAI_BASE_URL/chat/completions" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "tekizai/frontier",
    "messages": [{"role": "user", "content": "Route this Cursor coding task"}]
  }'

Send files to services that accept them

Capability checks prevent multimodal Cursor requests from landing on text-only models.

Use accounts you are allowed to use

TEKIZ.AI does not grant unauthorized OpenAI, Anthropic, Gemini, or OpenRouter access. Customers bring authorized access or use generated keys for TEKIZ.AI account control.

See setup activity without reading prompts

TEKIZ.AI can measure setup and key creation without collecting prompts, provider credentials, or model responses.

Keep Cursor on one stable address

If one key hits a limit or a provider slows down, TEKIZ.AI can use another route. Local backups and file support are handled in the same place, so Cursor does not need a separate setup for each provider.

Next steps

Create an API key, copy the hosted quickstart, compare coding-agent setup, or estimate routing fit.