Opus 4.8
Claude Opus 4.8 API through one API3 balance
Use Opus 4.8 with your normal API3 key, Anthropic-compatible `/v1/messages`, OpenAI-compatible clients, and one shared balance for every available Claude model.
API3 endpoint
api3.claudestore.store
api3.claudestore.store/v1
Sonnet 4.6
Opus 4.7
Opus 4.8
Opus 4.8 inside API3
Use your normal sk-cs2-* API3 key.
Anthropic-native base URL: api3.claudestore.store.
OpenAI-compatible base URL: api3.claudestore.store/v1.
Usage is visible in the same dashboard history and token breakdown.
The same API3 balance covers Sonnet 4.6, Opus 4.7, Opus 4.8 and the other supported Claude models.
One key. One balance.
Opus 4.8 is not a separate checkout flow. Use the same API3 key, the same dashboard balance, and the same usage history as the rest of the Claude lineup.
Best-fit workflows
Long coding sessions in Cursor, Claude Code, and VS Code agents.
High-consistency multi-turn workflows where cache reuse compounds.
Teams that want one API key and one balance for all Claude models.
API3 balance for Opus 4.8
Top up your regular API3 balance once and use it across Sonnet 4.6, Opus 4.7, Opus 4.8 and the other available models.
Integrations and use cases
Key format
API base: api3.claudestore.store
Public model: claude-opus-4-8
Key: API3
Frequently asked questions
What is Claude Opus 4.8 best for?
Opus 4.8 is best for difficult coding, long-running AI agents, code migrations, and high-autonomy tasks where consistency matters more than raw speed.
How do I buy Opus 4.8 access?
Top up the regular API3 balance. The same balance is used for Opus 4.8 and the rest of the supported Claude models.
Do I need a separate API key?
No. Opus 4.8 uses the same API3 key and the same dashboard balance as the other Claude models.