Veo is US-region only: what EU teams call on Sume

A third-party listing says that as of Sept 18, 2026 Google's Veo is available only in the US region us-central1, with no EU region or multi-region endpoint documented. Sume exposes one endpoint, https://api.sume.com/v1/videos, whatever model you pick, and its docs do not state where a model runs, so an EU team with a residency requirement should get a written answer first.

What each source says

The first row is from innfactory's Veo page, a secondary source. I did not check Google's own documentation, so treat the region claim as something to confirm there.

What one endpoint means

Sume serves video through POST /v1/videos with catalog ids such as seedance-2, and lists each model's resolutions, aspect ratios and durations at GET /v1/videos/models. Your code does not choose a cloud region; it chooses a model. That keeps integration simple, but it also means the region question is answered by Sume, not by a parameter you set.

The docs say a v1 model runs on a single backend and that provider.options is rejected. There is no region field to pin, and I would not assume one exists.

curl "https://api.sume.com/v1/videos/models" \
  -H "Authorization: Bearer $SUME_API_KEY"

What an EU team should do

• Ask Sume in writing where each model you plan to use processes data.
• Read the privacy section linked from the Sume basics page for retention terms.
• Do not send personal data in prompts or reference images until you have that answer.
• Re-check Google's docs for Veo regions, since a listing can lag the vendor.