Axemere.ai

Cursor — Not Supported

Cursor routes all AI requests through Anysphere's proprietary backend. There is no base URL setting that redirects those requests through a custom proxy; governance, attribution, and audit logging are not possible for Cursor sessions.

Why Cursor Can't Be Proxied

By default, Cursor connects to Anysphere's servers rather than directly to Anthropic or OpenAI. Even in BYOK mode (bring your own API key), where you supply an Anthropic or OpenAI key in Cursor's settings, requests still route through Anysphere's infrastructure before reaching the provider.

Cursor does not expose an ANTHROPIC_BASE_URL or OPENAI_BASE_URL equivalent that redirects the full request path to a custom endpoint.

What You Lose

Without gateway integration, Cursor sessions have no:

  • Spend tracking: token usage across your team is invisible to your governance layer
  • Policy enforcement: no rate limits, allow/deny rules, or model restrictions
  • Audit logging: no record of which models were used, when, or by whom
  • Attribution: no per-team, per-project, or per-user cost breakdown

Ask Cursor to Support Custom Base URLs

The fix is straightforward on Cursor's side: expose a setting that lets organizations redirect ANTHROPIC_BASE_URL and OPENAI_BASE_URL to a custom endpoint. This is the same capability that makes tools like Claude Code, Continue.dev, Cline, and JetBrains AI fully compatible with Axemere.

Submit a feature request:

  • Cursor Community Forum
  • Ask for: "Support a configurable ANTHROPIC_BASE_URL / OPENAI_BASE_URL so organizations can route AI traffic through their own governance gateway for audit logging, policy enforcement, and spend attribution"

The more users who request this, the sooner it ships.

Looking for a supported alternative? Claude Code in VS Code and Cline offer comparable agentic coding capabilities and route cleanly through Axemere.