mozg.whyexploreguideconnectSign in

explore / Game development / egorfdrv

Stake Engine · RGS API

Answer questions about the RGS wallet endpoints exactly as they are specified: authenticate, balance, play, end-round, bet-replay and event — the HTTP method and path of each, every request field with its type and whether it is required, the response shape, the error cases, and how amounts are expressed in minor currency units.

64 notes · updated 2026-08-03 · trained 69%

use this brain
# sign in to get a token
$ claude mcp add --transport http mozg \
https://mozg.sh/mcp --header "Authorization: Bearer …"
> use egorfdrv/stake-engine-rgs-api — …
Get a token

What it can answer

30 checks
69%
▲Authenticate5 / 6
▲Bet Replay4 / 5
▲Play4 / 6
✓Balance2 / 2
▲End Round2 / 3
▲Event2 / 4
▲Currency units1 / 2
▲Errors1 / 2

Inside

  • Retrying play after a timeout is not documented as safe · Endpoint list
  • POST /wallet/play method and path · Endpoint list
  • Play error responses: 400, 401, 500 · Error codes
  • Play response round object fields · Endpoint list
  • Bet amounts are in minor currency units · Currency units
  • Error response body shape · Error codes
  • Play amount must be within minBet/maxBet · Endpoint list
  • Play request body parameters (amount, sessionID, mode) · Endpoint list
  • Play 200 response shape: balance and round · Endpoint list
  • Play response balance object fields · Currency units
  • Event requires an active session and an in-progress round · Endpoint list
  • Event request body fields: sessionID and event · Endpoint list
  • Event endpoint errors: ERR_IS (401) and ERR_GEN (500) · Error codes
  • Event 200 response shape · Endpoint list

Licence

CC BY-NC-SA 4.0

Use it, copy it, build on it, with credit. Selling it is not allowed.