OpenRouter eu. and us. base URLs vs Sume's single API host
OpenRouter added us. and eu. in-region base URLs on 2026-09-09. Sume documents one host, api.sume.com, and no region-pinned base URL or ZDR toggle.
Sume's docs publish one API host, https://api.sume.com, and no region-pinned base URL like OpenRouter's us.openrouter.ai or eu.openrouter.ai. The video docs also say Sume has no ZDR toggle. If you need a guarantee about where requests are processed, the docs read 2026-10-01 do not give you one to rely on, so ask Sume before you commit.
What did OpenRouter launch?
The 2026-09-09 announcement says requests to us.openrouter.ai are decrypted inside the US and routed only to US provider endpoints; eu.openrouter.ai does the same for the EU. You swap the base URL to https://us.openrouter.ai/api/v1 or https://eu.openrouter.ai/api/v1, and keys, bodies and model ids stay the same. If no in-region provider serves the model, the request fails with a 404. The post says the feature is available on the Business and Enterprise plans.
What does Sume document about its host?
| Topic | What the docs say |
|---|---|
| Base URL | curl https://api.sume.com/v1/me in the API reference |
| What is available | GET /v1/catalog: capabilities, endpoints, runtime readiness, models and pricing metadata |
| Provider names | Public API responses are provider-neutral |
| ZDR | "Sume has no ZDR toggle" |
Can I pin a Sume request to a region?
Nothing in the API reference, the catalog description or the generation docs describes a region parameter or regional hostname. Because responses are provider-neutral, they also do not tell you which backend ran. Treat region pinning as not offered until Sume documents it.
What should I check before migrating?
Read the live catalog with GET /v1/catalog, and compare the route differences in OpenRouter-compatible video generation. If a residency review is a hard requirement, get that answer in writing; this post is not legal advice.
Sources
Related posts
More in Developers
- OpenRouter video webhooks vs Sume callback_url, signing, retries
OpenRouter's video guide points to a webhooks cookbook. On Sume, pass an HTTPS callback_url, verify x-sume-webhook-signature, retry with Idempotency-Key.
- OpenRouter weight_exceeds_budget: never retry; Sume queue_full
OpenRouter's weight_exceeds_budget 402 will not clear on retry; in_flight_budget_exhausted will. Sume splits the same way: queue_full retries, 402 does not.
- Pipedream 750-second timeout: poll loop or Sume webhook?
Pipedream paid plans allow 750 seconds per run. Submit the Sume video job, then finish in a second workflow triggered by the webhook not a long poll loop.
- Polly async needs an S3 bucket; Sume gives a status URL and webhook
Polly's StartSpeechSynthesisTask writes audio to your S3 bucket and can notify an SNS topic. Sume TTS returns a status URL, or a signed webhook on completion.
Written by Sume