Regions & Node Resolution

Node directory

GET
/api/discover.php
Every enabled service node — region, label, api_url, realtime — plus suggested_region (public, rate-limited)
POST
/api/discover.php
Game resolution — send the game key in X-Api-Token (never in a URL); returns {region, node} for the single node the game is pinned to
POST /api/discover.php
curl -X POST "https://api.michitai.com/api/discover.php" \
     -H "X-Api-Token: YOUR_API_KEY"
{"success":true,"region":"uk","node":{
  "region":"uk","label":"United Kingdom (London)",
  "api_url":"https://uk-api.michitai.com/api",
  "realtime":{"host":"uk-realtime.michitai.com","port":443,
              "protocol":"wss","udp_port":3000}}}

A game is pinned to exactly one node — its players, rooms, matchmaking, leaderboards and realtime sessions exist only there. Resolve once at startup, then use node.api_url as the base URL for every REST call and node.realtime for WS/UDP. Presenting the key on a wrong node answers 421 with {"home_region","home_api_url"} — re-resolve and repoint. Each SDK ships this as ResolveGame / resolveGame / resolve_game / resolveGameNode; see the per-language Regions pages. Older keys (region = NULL) resolve to the main Amsterdam node and keep working unchanged.