Quick answer
For Claude Code, do not assume every OpenAI-compatible relay works. First verify Anthropic-compatible endpoint behavior, model names, streaming, pricing, privacy policy and billing rules from public docs.
Public Source Checks
Claude Code Gateway Candidate Checks
Use Anthropic's official API and Claude Code behavior as the baseline. The providers below are candidates with visible Claude Code or Anthropic-compatible signals; use public setup docs, pricing links, source coverage and risk notes to decide what to verify before adding balance or sending repository code.
What to verify before choosing
- Does the provider explicitly mention Claude Code or Anthropic-compatible APIs?
- Are base URL, auth token format, model names and streaming behavior documented?
- Can you verify pricing, refund terms and support channels before adding balance?
- Does the privacy policy explain logging or data retention for code prompts?
Official API Baseline
Start here for production, sensitive code and compliance-heavy workflows. Third-party relays should be compared against these official routes, not treated as the default.
OpenAI
GPT, Codex-style workflows, OpenAI SDK and Responses API compatibility baseline.
Anthropic
Claude Code, Claude API and Anthropic-compatible behavior baseline.
Google AI Studio
Gemini API, multimodal model access and Google-native developer workflows.
DeepSeek
DeepSeek API, low-cost reasoning/code models and official OpenAI-compatible reference.
Gateway and Relay Candidates
After checking the official API baseline, compare provider type, suitable workflow, tool compatibility, public source links, missing fields and next actions in one compact table.
| Entry | Provider | Type | Fit | Tool compatibility | Public links | Notes | Source / action |
|---|---|---|---|---|---|---|---|
| Check 1 | MoleAPI | Claude Code friendly | Developers who want one endpoint for Claude Code, Cursor, Codex CLI, and common OpenAI SDK workflows. | Claude Code Codex CLI Cursor Cline | Run low-balance test first | ||
| Check 2 | API易 | Claude Code friendly | Teams that care about documentation, invoices, and visible model/pricing references. | Claude Code Codex CLI Cursor Cline | Run low-balance test first | ||
| Check 3 | 灵芽 API | Claude Code friendly | Users who primarily need copyable setup steps for AI coding terminals and editors. | Claude Code Codex CLI Cursor Cline | Run low-balance test first | ||
| Check 4 | 柏拉图 AI | Claude Code friendly | Users comparing Chinese relay services with coding-tool setup support. | Claude Code Codex CLI Cursor Cline | Pricing needs checking |
Use these checks this way
- Start with source links: official site, docs and pricing should be easy to verify.
- Use the public source checker when a provider page is missing docs, pricing, models, privacy, terms, status or support fields.
- Use official API routes as the baseline before treating any relay or gateway as a candidate.
- Treat missing docs, missing pricing and unclear compatibility as filtering signals.
- Open the provider detail page to see source fields and risk notes before deciding what to verify next.