Show the endpoint
Put Base URL and key usage above long explanation.
The documentation layer here is not a generic knowledge dump. It is part of the sales and activation path: pricing, compatibility, quick-start, client setup, and troubleshooting all need to feel immediate and credible.
Built for activation, not vanity.
Put Base URL and key usage above long explanation.
Route users into Codex, Claude Code, Cursor, Cline, or SDK setup.
Give one copyable command and one safe first task.
Name common Base URL, model, and quota mistakes early.
From registration and first key to the first successful request in the shortest possible route.
For beginners: choose a coding agent, install it, connect OpenMagic, and run the first useful task.
Claude Code, Codex, Cursor, Cline, and SDK setup notes with the right base URL shape.
How top-up, monthly plans, rewards, and fair-use rules fit together.
Documentation should answer the exact questions that block the first successful call.
Do not bury the one value users need under paragraphs. Put the right endpoint shape at the top of each relevant page.
Claude-style routes, Codex config files, and tool-specific edge cases should be explicit so support volume stays manageable.
Users need to know whether they are on balance, plan quota, or a support-assisted arrangement before heavy usage begins.
Public docs should feel clean. Internal implementation notes stay under /DOCS/ where they help construction instead of confusing customers.