Obtain a production API key from the Riot Developer Portal by submitting a project application; note that development keys have stricter rate limits and expire periodically.
Resolve the correct regional routing value for match-v5 (americas, asia, europe, sea) based on the player's platform (e.g., NA1 and BR1 route to americas); use this as the base URL host.
Call the match-v5 matchlist endpoint with a PUUID and optional filters (queue type, count, start index) to retrieve an array of match IDs.
Fetch individual match details by calling the match-v5 match endpoint with each match ID; cache responses aggressively since historical match data is immutable.
Implement a rate limit handler that reads the X-Rate-Limit-Count and X-Rate-Limit-Type response headers to track consumption; on a 429 response, read Retry-After and wait the specified duration before retrying.
Separate API calls into per-method and per-service buckets as Riot enforces both; exceed either and you receive a 429 even if the other bucket has capacity.
Known gotchas
Development API keys have very low rate limits and are unsuitable for any volume testing; always test rate limit handling with a production key or by mocking 429 responses.
PUUIDs are cross-region but match IDs contain a platform prefix; always route match-v5 calls using the regional cluster (americas/asia/europe/sea), not the platform cluster (na1/euw1/etc.).
Riot's rate limit headers reflect limits at the time of the response, not the time of the request; a burst of parallel requests can all succeed and then all trigger 429s on the next wave before headers update.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp