API routes
OM Router exposes the same API through two independent routes. Choose one service address and send requests to it directly; the routes do not redirect API traffic to each other.
Available routes
Section titled “Available routes”| Route | Service address | OpenAI-compatible base URL | When to use it |
|---|---|---|---|
| Cloudflare (default) | https://api.omrouter.com |
https://api.omrouter.com/v1 |
Start here for general use and North American networks. |
| EdgeOne | https://eo.omrouter.com |
https://eo.omrouter.com/v1 |
Try this alternative for Asian and some European networks, or when Cloudflare is slow from your location. |
Route performance depends on your ISP, location, and current network conditions. Test both from the environment where your application runs if latency matters.
Switch routes
Section titled “Switch routes”Only replace the service origin. Keep the API path, API key, model name, request body, and authentication header unchanged.
https://api.omrouter.com/v1/chat/completionshttps://eo.omrouter.com/v1/chat/completionsThe same API key works on both routes.
Choose the route before sending a request. Do not automatically replay a generation request on the other route after it may have reached OM Router, because duplicate requests can produce duplicate work and charges.
Protocols
Section titled “Protocols”Both routes support the documented HTTPS APIs, streaming responses, WebSocket upgrades, and long-running requests. Use the protocol and path shown by the relevant API reference page.