Collect cheat evidence server-side; never rely solely on client-reported signals
POST to https://partner.steam-api.com/ICheatReportingService/RequestPlayerGameBan/v1/ with your publisher API key, the offending steamid, appid, reportid (your internal reference), cheatDescription, duration (0 = permanent), and delayBan (bool for delayed visibility)
Store the returned banid for future revocation
To revoke, POST to https://partner.steam-api.com/ICheatReportingService/RemovePlayerGameBan/v1/ with the banid
Optionally use ReportCheatData (requires a standard web API key, not a publisher key) to submit cheat evidence files to Valve for VAC consideration
Known gotchas
RequestPlayerGameBan requires the publisher API key and must be called from a secure server; it is distinct from the standard web API key used by ReportCheatData
Game bans issued via ICheatReportingService appear in GetPlayerBans under NumberOfGameBans, not VACBanned; they are separate from Valve-issued VAC bans
delayBan=true defers public visibility; use it to prevent cheaters from detecting detection before you patch the exploit
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