This page previously described a named multi-region deployment (specific regions, automatic geographic routing, and per-region load balancing). Those infrastructure details could not be verified against the Swarms API application source and have been removed rather than restated as fact. If you rely on region-specific guarantees (data residency, regional failover SLAs), confirm current infrastructure details with the Swarms team before depending on them.
Connecting to the API
All requests go to a single base URL regardless of where you connect from:
There is no region-specific hostname or path — use this base URL for every request, from any location.
What This Means for Your Integration
- No configuration needed: Point your client at
https://api.swarms.world — there is nothing region-specific to select or configure.
- Standard HTTP networking applies: Latency to
https://api.swarms.world depends on your own network path and DNS resolution, like any other HTTPS API.
- Retries and timeouts: Treat the API like any internet-hosted HTTPS service — implement normal timeout and retry handling (see Rate Limit Headers for
Retry-After on 429s).
If You Need Region or Residency Guarantees
If your use case requires guarantees about where requests are processed or data is stored, contact technical support or your account team directly rather than relying on this page — those details are outside what the public API surface exposes.
