Choose the right API surface first, then make your first call. New integrations should start with the GlobalRouter API, while migrations can keep using the compatible protocol that matches their current client.
The four entry points match different integration paths. Use the GlobalRouter API for new features, and reserve compatible protocols for migrations or provider-style calls.
GlobalRouter API
Primary long-term public API
Recommended primary API
/api/v1
The default entry point for new integrations. Chat, text, audio, image, video, model, provider, asset, credit, and API key management all live under one API surface.
Best for
New projects, a unified model catalog, audio, providers, credits, assets, and key management