Read game data over REST
Use your existing scoped MCP token with the Ravensight API. Each game-data request has the same price as an MCP read: 100,000 weighted events on the shared event meter. A studio must have funded a prepaid balance. GET /api/v1/data/games is free. This surface requires usage billing V2 to be enabled.
Send the token only in the Authorization header. Tokens in query strings are rejected. Existing studio membership, role, project and tool restrictions still apply. Reuse an operation ID only to retry the exact same request; completed retries do not charge again.
curl https://api.ravensight.io/api/v1/data/games/GAME_ID/overview \
-H "Authorization: Bearer $RAVENSIGHT_TOKEN" \
-H "X-Ravensight-Operation-Id: overview-request-001"
Under /api/v1/data/games/:gameId/, read metrics, overview, retention, funnel, breakdown, monetization, economy, health, progression, distribution and events. Pass from and to in Unix seconds, at most 31 days apart. Funnel steps and retention days accept comma-separated values. Property filters accept a JSON object.
Event pages contain up to 1,000 rows in the shared export schema. Continue with after=nextAfter&skip=nextSkip until nextAfter is null. The cursor timestamp is in milliseconds. Offsets are bounded to 1,000; use bucket export for bulk archival or a timestamp containing more rows than this bounded reader can page. Synthetic events are excluded by default; include_synthetic=include or only changes that scope.
Responses carry meta plus X-Ravensight-Operation-Id, X-Ravensight-Event-Units and X-Ravensight-Rate-Version. A query is bounded to 128,000 response bytes. The rate limit is 300 requests per minute per token. Unknown and inaccessible games both return 404. Download the OpenAPI 3.1 specification.