Do not put Workers in LLM-forbidden locations

Type

New feature

Description

Do not put Cloudflare Workers in regions which are typically not allowed to access LLM APIs

Benefit

Currently I am in a region (Melboure, Australia) which is allowed to access the Google Gemini LLM API:

However when I access workers (across different domains and accounts), I can see that the workers I am connecting to reside in Hong Kong (colo: HKG), which is 4,600 miles away from me.

Hong Kong is NOT allowed to access the Gemini API, so Google returns this error when we try ti access its Gemini LLM API from both a Workers and via the AI Gateway:

“User location is not supported for the API use.”

With LLM API adoption growing, this problem will only get bigger.

A potential solution is being able to mark a worker as an “AI API worker”, whereby Cloudflare should then avoid placing the worker in a region which is typically not allowed to access LLM / AI API services (as long as the HTTP client is also in a typically-allowed-access region).