Authenticate the reporting user with an OAuth 2 access token to associate the report with their account
POST to /report with a JSON body specifying resource (the type of resource being reported, e.g., mods, users, games), id (the resource's numeric ID), type (reason category integer), and summary (free-text description)
Map reason categories to your in-game report dialog options; mod.io defines standard reason integers for DMCA, not appropriate, and other violation types
Present the user a confirmation that the report was received; the API returns 200 on success with no body
Ensure your moderation team monitors the mod.io game admin moderation dashboard regularly, as reports do not trigger automated actions by default
Known gotchas
The /report endpoint requires an authenticated user token — game API keys alone cannot submit reports on behalf of a user
There is no deduplication guarantee; the same user can submit multiple reports for the same resource, which may inflate report counts without additional server-side throttling
Reports submitted via the API appear in the same moderation dashboard queue as reports made via the mod.io web UI; all reports require manual moderator review
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