AI Sonar exposes multiple API formats so common coding tools, SDKs, and frameworks can integrate with minimal glue code.This page is intentionally narrower than a marketing matrix:
Supported means we document a concrete setup path and AI Sonar exposes the protocol shape that path expects.
Strong native path means the repo also has direct adapter or request-format evidence for that protocol family.
Best-effort means the integration can work, but the upstream client does not treat this custom gateway workflow as a stable contract.
Unsupported fields are not handled uniformly. On compatibility routes, some fields are ignored or normalized. On /v1/responses, unsupported fields can return explicit 400 or 503 errors when that route cannot guarantee the requested behavior.
Works for BYOK standard chat/editor flows, not as a replacement for Cursor-managed features like Tab Completion
Claude Code CLI
Strong native path
Anthropic
Native /v1/messages route with adapter coverage for thinking and tool_choice
Codex CLI
Supported with model/path limits
OpenAI Responses
Treat /v1/responses as an advanced path for Codex-specific workflows; some Responses-only fields are not guaranteed across every model and routed path
Gemini CLI
Best-effort / experimental
Gemini
Custom AI Sonar base URL flow is not a stable upstream contract
OpenCode
Supported
OpenAI-compatible
Use an OpenAI-compatible provider by default; move to a Responses-based provider only when you explicitly need it
Other OpenAI-compatible editors and agent tools often work with the same base URL pattern, but this repo does not currently maintain tool-specific regression coverage for Windsurf, Aider, Continue.dev, Cline/Roo Code, GitHub Copilot, and similar clients.
Compatibility path for /v1 Chat Completions and Embeddings; use native provider routes for provider-specific behavior, and do not assume Responses-only fields work across every model
Anthropic SDK
Python/JS
Strong native path
Native Messages route with direct evidence for tools, thinking, and prompt caching
Vercel AI SDK
TypeScript
Recommended integration pattern
Prefer @ai-sdk/openai-compatible; use @ai-sdk/openai only when you explicitly want Responses-native behavior
LangChain
Python/JS
Supported standard surfaces
ChatOpenAI and OpenAIEmbeddings are the intended scope; vendor-native extras are out of scope
LlamaIndex
Python
Supported via OpenAILike
Use OpenAILike, not the built-in OpenAI classes, for third-party gateways such as AI Sonar
Dify
-
Supported with scope limits
OpenAI provider and chat-completions-oriented flows are the intended path; not a fit for Codex-specific Responses or WebSocket behavior