Skip to main content
Cursor cannot route its Anthropic (Claude) traffic through Wardin today. Cursor has no Anthropic base-URL override — Claude requests always go directly to api.anthropic.com. This is an open Cursor feature request.

​
Why it doesn’t work

  • No Anthropic base-URL field. Cursor only exposes an OpenAI base-URL override. There is no equivalent for Anthropic, so you cannot point Claude requests at the Wardin gateway.
  • The OpenAI override breaks Claude. If you set Cursor’s OpenAI base URL, Cursor sends Claude traffic to it too and the payloads don’t match — Anthropic models start failing with 422 errors.
  • Cursor routes through its own servers. Even where a base-URL override exists, Cursor proxies API traffic through Cursor’s backend, so the target must be a public URL — a local gateway (http://localhost:8080) is unreachable.
  • The Wardin gateway speaks the Anthropic Messages API (/v1/messages) and embeddings only — it does not expose an OpenAI /v1/chat/completions endpoint, so the OpenAI-override path has nothing to talk to either.

​
What to use instead

To send governed requests through Wardin today, use a client that honors ANTHROPIC_BASE_URL:
  • Claude Code — set ANTHROPIC_BASE_URL + ANTHROPIC_AUTH_TOKEN and every session flows through Wardin.
  • curl / the Anthropic SDK — point base_url at the gateway (see the onboarding Point a client step for copy-paste snippets).

​
When this will change

A Cursor integration becomes possible once either lands:
  1. Cursor ships an Anthropic base-URL override (track the feature request above), or
  2. Wardin exposes an OpenAI-compatible endpoint so Cursor’s OpenAI override can target the gateway.
Until then, this guide won’t claim a configuration that doesn’t work.