OpenAI-compatible workflow
Single base URL, single bearer token, and SDK-friendly request shapes for the broadest tool support.
- Chat Completions
- Embeddings
- Vision inputs
- Future Responses support
The point of the platform is to let users consume multiple model families through one product surface and one account system, while provider complexity stays behind One API and the business layer.
The user should feel they are buying access to capability, not backend complexity.
Single base URL, single bearer token, and SDK-friendly request shapes for the broadest tool support.
Claude Code, Codex, Cursor, Cline, and similar tools should route through one product story rather than separate provider accounts.
Customers buy capability and billing clarity. Channel selection, routing, and fallback stay behind the business layer.
Rates are stored in the business database and expressed as USD per million tokens before plan-specific discounts or restrictions.
| Provider | Model | Tier | Input / 1M | Output / 1M | Context |
|---|---|---|---|---|---|
| openai | GPT-4o mini | standard | $0.1800 | $0.7200 | 128,000 |
| openai | GPT-4o | premium | $3.2000 | $12.8000 | 128,000 |
| openai | GPT-4.1 | premium | $2.6000 | $10.4000 | 1,000,000 |
| anthropic | Claude Sonnet | premium | $3.6000 | $18.0000 | 200,000 |
| anthropic | Claude Opus | elite | $18.0000 | $90.0000 | 200,000 |
| Gemini Flash | economy | $0.1200 | $0.4800 | 1,000,000 | |
| Gemini Pro | premium | $1.5000 | $6.0000 | 1,000,000 | |
| xai | Grok Fast | premium | $2.6000 | $10.4000 | 128,000 |
| deepseek | DeepSeek Chat | economy | $0.0500 | $0.1800 | 128,000 |
| deepseek | DeepSeek Reasoner | standard | $0.2200 | $0.8800 | 128,000 |
| groq | Groq Open Models | economy | $0.0300 | $0.1200 | 128,000 |
OpenMagic should explain what the user buys without exposing every operational detail of upstream accounts and exit nodes.
The operating target is official accounts, enterprise purchasing, or compliant upstream channels. Gray account pools are not the product direction.
Provider accounts can be bound to specific exit nodes so traffic can keep a consistent region and IP profile.
Users keep one Base URL. Operations can change channels, model mappings, and node routes behind the gateway.
The front-end story has to match the actual request shapes developers paste into tools.
Most SDK and client traffic should point to https://api.openmagic.ai/v1 so migration feels obvious.
Some clients will need a root host or alternate path shape. Those exceptions belong in docs, not on the homepage.
Aliases can simplify the catalog, but they should not hide what customers are actually buying or testing.
Rate limits, plan caps, and fallback behavior should be explained before users hit avoidable errors.