Cursor model routing

Cursor AI model router for OpenAI-compatible and Anthropic-compatible failover

Point Cursor at Sage Router instead of hard-coding one provider key. Use hosted sk_sage_* keys, local/Tailnet routers, local Ollama fallback, OpenAI-compatible routes, Anthropic-compatible routes, and provider health policy through one model layer.

Create API key Copy quickstart Coding-agent router Cursor guide

Cursor custom OpenAI endpoint

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

Anthropic-compatible path

When Cursor workflows expect Claude-style routing, Sage Router can keep authorized Anthropic/Dario paths in policy without turning public plans into bundled provider resale.

429 failover

Multiple API-key load balancing and health-aware failover let Cursor continue through eligible authorized routes when one provider key or endpoint rate-limits.

60-second Cursor setup

export OPENAI_BASE_URL=https://api.sagerouter.dev/v1
export OPENAI_API_KEY=sk_sage_your_generated_key

# Cursor: set the custom OpenAI-compatible endpoint to:
#   Base URL: https://api.sagerouter.dev/v1
#   API key:  sk_sage_your_generated_key
#   Model:    sage-router/frontier

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

Multimodal routing

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

Provider boundaries

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

Activation telemetry

Copy events and hosted key creation paths make Cursor demand measurable without collecting prompts, provider credentials, or raw model outputs.

Why Cursor needs a router

Cursor is productive when the model path is stable. The failure mode is operational: one key 429s, one provider slows down, local fallback is configured somewhere else, and multimodal requests need capability-aware routing. Sage Router centralizes those choices behind one endpoint.

Next steps

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