Authenticate the user with an OAuth 2 access token using any of mod.io's supported identity providers
POST to /games/{game-id}/mods/{mod-id}/subscribe to subscribe the authenticated user to a mod; the API returns 200 on success or 400 if the mod is not available or the user is already subscribed
On game launch, call GET /me/subscribed to retrieve all mods the user is subscribed to across your game and sync them with the local install queue
Handle pagination in the subscriptions response using the returned cursor or page metadata to ensure all subscriptions are retrieved for users with large collections
When a user unsubscribes, DELETE to /games/{game-id}/mods/{mod-id}/subscribe to remove the subscription and trigger local uninstall logic in your game client
Known gotchas
Subscriptions are tied to the authenticated user, not the device; on a new device the game must always sync from the API rather than relying on local storage
If the game has curation enabled and a mod's status changes to unavailable after a user subscribes, the subscription persists but the modfile will not be downloadable until the status is restored
Rate limits on subscription sync requests can affect games with many players launching simultaneously; implement a jittered backoff for the GET /me/subscribed call at game startup
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