LLMsRelay Regional Availability and API Access
How LLMsRelay availability depends on local law, payment coverage, network access, gateway status, and currently enabled model routes.
LLMsRelay is an independently operated API gateway available to customers in multiple regions. It is not affiliated with or endorsed by Anthropic, PBC. Availability depends on local law, payment-provider coverage, gateway status, and the model IDs currently returned by GET /v1/models.
Before purchasing usage, confirm that the website, checkout method, API endpoint, and required model IDs are available from your location. Contact support when a payment method or route is unavailable.
Availability Checklist
- Local requirements — you are responsible for complying with laws and regulations that apply to you
- Network access — confirm that
api.llmsrelay.comis reachable from your environment - Model availability — use
GET /v1/modelsbefore relying on a model ID - Payment coverage — available card and crypto methods are shown at checkout
- Service status — check current incidents before production use
How Availability Is Determined
Access is evaluated across several independent layers:
- the LLMsRelay website and authentication service;
- the selected card or cryptocurrency payment provider;
- the API gateway and its current upstream routes;
- your local network and legal requirements.
Payment Methods by Region
- Card checkout — availability and supported card types are determined by the active provider
- Cryptocurrency checkout — supported assets and networks are shown before payment
- Large orders — contact support before paying when you need a custom invoice or confirmation
FAQ
Can I use LLMsRelay from my country?
Availability depends on local law, payment-provider coverage, network access, gateway status, and the model routes currently enabled for your account.
Does LLMsRelay impose an IP allowlist?
LLMsRelay API keys are not tied to a customer-managed IP allowlist by default. Network and upstream availability can still vary by location.
Are model behavior and features guaranteed to match another service?
No. Available model IDs, latency, tool support, and behavior depend on the selected route and upstream provider. Verify compatibility with GET /v1/models and a test request.