Why this exists
Applications increasingly need different models for reasoning, latency, cost, media, or regional availability. Connecting every provider directly creates duplicated authentication, usage accounting, policy, and reliability work.
What we will not hide
A unified API must not pretend all models or protocols are interchangeable. The catalog will identify models, endpoint compatibility, pricing rules, and meaningful limitations. Provider-native APIs remain the correct choice when translation would erase capabilities.
How the platform is separated
The public website and editorial system are independent from the request gateway. The gateway can be upgraded without replacing the Blog, and the Blog can publish content without access to API keys, balances, or routing secrets.