Spec comparison
| Spec | OpenRouter | Anthropic Direct |
|---|---|---|
| Models available | 200+ across 30+ providers | ~6 (Claude family only) |
| API surface | OpenAI-compatible (drop-in) | Anthropic native (Messages API) |
| Claude Opus 4.7 input price | $5.00 + ~5% markup | $5.00 |
| Claude Opus 4.7 output price | $25.00 + ~5% markup | $25.00 |
| Prompt caching support | Yes (provider-dependent) | Yes (90% off cached read) |
| Failover / multi-provider | Yes (built-in) | No |
| BYO API key | Yes (per-provider) | N/A |
| Enterprise features | Limited (no MSA/DPA on small plans) | Full (MSA, DPA, BAA) |
| Best for | Multi-model apps + portability | Pure Claude apps + enterprise |
Feature matrix
| Capability | OpenRouter | Anthropic |
|---|---|---|
| Access to Claude Opus 4.7 | ✓ | ✓ |
| Access to GPT-5.5 + Gemini + DeepSeek | ✓ | ✗ |
| OpenAI-compatible /v1/chat/completions | ✓ | ✗ |
| Anthropic-native Messages API | ~ | ✓ |
| Prompt caching (full discount) | ~ | ✓ |
| Batch API (50% off) | ~ | ✓ |
| Computer use | ~ | ✓ |
| Tool / function calling | ✓ | ✓ |
| Vision | ✓ | ✓ |
| Multi-provider failover | ✓ | ✗ |
| Provider markup (OpenRouter ~5%, Anthropic 0%) | ~ | ✓ |
| Enterprise MSA / DPA / BAA | ~ | ✓ |
| SOC 2 + HIPAA path | ~ | ✓ |
| Single-vendor SLA | ✗ | ✓ |
| Provider-agnostic gateway | ✓ | ✗ |
Cost analysis (Claude Opus 4.7)
| Workload | OpenRouter | Anthropic Direct | Direct saves |
|---|---|---|---|
| 10K in / 1K out (no cache) | $0.0788 | $0.075 | 5% |
| 10K in / 1K out (60% cache hit) | $0.046 | $0.030 | 35% |
| 100K in / 5K out (batch) | $0.394 | $0.313 | 21% |
| 100K in / 5K out (cache + batch) | $0.215 | $0.105 | 51% |
When OpenRouter wins
OpenRouter wins anytime you need more than one model. Switching from Opus 4.7 to GPT-5.5 to Gemini 3.1 Pro is a one-line config change: same OpenAI-compatible API surface, same SDK, same auth flow. The 200+ available models include every major provider plus dozens of open-weight hosts. Built-in failover (route to a fallback if the primary is down) is a real production safety net you would otherwise build yourself. The OpenAI-compatible API surface is also the lowest-friction integration path: any client library that talks to OpenAI talks to OpenRouter. For experimentation, prototyping, multi-model A/B testing, and any product whose value depends on always picking the right model per request, OpenRouter is the right default. The ~5% markup is small relative to the engineering cost of building this yourself, and the BYO-API-key feature lets you use your own provider rate limits when it matters.
When Anthropic Direct wins
Anthropic Direct wins for any Claude-only workload where price, full feature surface, or enterprise procurement matters. The cost story compounds fast: full prompt caching (90% off cached read tokens) + Batch API (50% off output) means a real workload often costs 50-70% less on Direct than the same calls on OpenRouter. Computer use, the Claude Code CLI, prompt caching, and the latest features always land on Direct first. Enterprise procurement (MSA, DPA, BAA for HIPAA, SOC 2) is mature and standard on Anthropic enterprise plans, while OpenRouter's enterprise tier is still maturing. For pure Claude apps at any meaningful scale, Direct is the right default. The trade-off is portability: locking your tool-calling, prompt structure, and SDK to Anthropic-native APIs raises your vendor exit cost measurably.
The common combination
The smart pattern: Anthropic Direct as the primary path for Claude traffic (best price, full caching), OpenRouter as a secondary endpoint for everything else and for failover. A simple wrapper exposes one OpenAI-compatible API to your application; the routing logic decides whether to hit Direct or OpenRouter per request. This setup gives you the cheapest Claude + the broadest model coverage + the failover guarantee, with portability preserved at the application layer. The Swfte router ships exactly this pattern as default behaviour, and our vendor lock-in leaderboard shows why a portable abstraction layer is worth the effort.
How to choose
- If your app is Claude-only and growing, default to Anthropic Direct. Caching alone justifies it at scale.
- If your app uses 2+ models or is exploring, default to OpenRouter for the OpenAI-compatible surface.
- For enterprise deals (MSA/DPA/BAA), Anthropic Direct is the cleaner procurement path.
- Always design your client to talk to a single internal endpoint, not a vendor URL. Swap providers behind it.
- Pilot one workload on each. Measure cache hit rate; if >40%, going Direct is almost always cheaper.
- Add a failover endpoint regardless of primary choice. A single-provider outage should not become an outage for you.
Frequently asked questions
Is OpenRouter or Anthropic Direct cheaper for Claude?
Anthropic Direct is the cheapest path to Claude: same headline price ($5/$25 per 1M for Opus 4.7) without OpenRouter's ~5% markup, plus full prompt caching (90% off cached read tokens) and Batch API (50% off). For Claude-only workloads at any meaningful volume, Direct wins.
When does OpenRouter make more sense?
When you need more than one model. OpenRouter gives you 200+ models behind a single OpenAI-compatible endpoint with built-in failover. Switching from Claude to GPT to Gemini is a parameter change. The ~5% markup is the price of provider-agnostic flexibility.
Does OpenRouter support prompt caching?
Partially. Caching support is provider-dependent and the discount may not always pass through cleanly. For workloads where >40% of tokens are cached input, going Direct typically saves more than the OpenRouter markup costs.
Which has better enterprise procurement?
Anthropic Direct. MSA, DPA, BAA (for HIPAA), and SOC 2 attestations are all standard on Anthropic enterprise plans. OpenRouter has improved its enterprise tier in 2026 but the procurement maturity gap is still real for large deals.
Can I use OpenRouter for failover and Anthropic Direct for production?
Yes. The common production pattern is Anthropic Direct as the primary path (full pricing, full features, full caching) with OpenRouter as a secondary failover endpoint that can route to GPT or Gemini if Anthropic is down. This gives you the best of both.