Availability
This page says what works today and what does not, so you can plan. "Verified" means exercised by an automated test or by the end-to-end scripts in this repository against the real RGS code. Dates are not promised on this page.
Works and verified
| Capability | Status | Evidence |
|---|---|---|
Operator API: launch, demo launch, products, catalogue (incremental, ETag), settled-round lookup, round and transaction lookups | implemented in operator-api | its test suite; interop/run.sh runs all five SDKs against it |
| Request signing: Engine body-only and full-request forms, two keys per operator, timestamp freshness, constant-time verification | implemented | the same suites, plus the shared vectors |
Launch safety: token reuse refused, idempotent retries, Idempotency-Key, rate limits, error negotiation | implemented | interop/run.sh and the service tests |
| Wallet calls from the RGS: balance, debit, credit, rollback, signed per operator, byte-identical retries, fencing of refused and timed-out debits | implemented in play-core | examples/reference-wallet/e2e.sh drives the real RGS against the reference wallet |
| Game API (Engine-compatible): authenticate, balance, play, end-round, event, replay | implemented | the conformance suite and the end-to-end script |
| Wallet conformance kit (WCS): signed report, capability flags | implemented in the RGS repository (conformance/wallet) | its own tests against the wallet simulator; the reference wallet passes it (examples/reference-wallet/wcs.sh) |
| Reference wallet and SDKs (TypeScript, Python, Go, Java, Rust, PHP, C#) | in this repository | vectors, unit tests, interop, the conformance kit |
Launch to play across processes
| Capability | Status | Evidence |
|---|---|---|
A launch from the operator API is a session the game API (a different process) can use: the session is written to Postgres, play-core finds it, authenticates it with your wallet and plays | implemented in the RGS and verified end to end; held for release approval | examples/reference-wallet/launch-e2e.sh: your SDK launches, play-core authenticates and plays on the same database, signed balance, debit and credit calls reach the wallet, the books agree, and a session id that was never issued is refused |
What that session carries is the operator, player, game, user, token, currency, IP, language and launch time. The launch's jurisdiction, release pin, tag, brand, country, device, new-bet window and metadata are resolved at launch but not yet stored with the session, so the game takes its release from its own configuration for now.
Implemented, but not yet joined for production
These pieces exist but run with in-memory adapters, so a deployed, multi-instance service needs the production adapters first.
| Gap | Effect today |
|---|---|
| Production registries (operators, releases, rounds) and replay/idempotency/rate-limit state in a shared database | one operator-API process only; no multi-replica |
| KMS signing of launch tokens and wallet requests | local keys only |
| The launch's jurisdiction, release pin, tag and other fields stored with the session | see above |
| Edge pieces: the launcher host that redirects the launch URL, and game hosting | the edge code exists; the production wiring is not part of this repository |
Specified, not built yet
| Capability | Notes |
|---|---|
| Hosted sandbox environment with the wallet simulator, fault toggles and forced outcomes | until it exists, run the local stack (see Testing) |
| Back office: operator registration, key upload, IP lists, go-live requests | keys and operators are configuration today |
| Webhooks (round, balance and key events) | specified, not served |
| Feeds and reports (finished rounds, transactions), daily automated reconciliation | until then, reconcile with the lookup calls |
GET /runecode/v1/catalogue (rich catalogue), GET /game/list (deprecated alias) | GET /v1/{product}/game is available |
Responsible-gaming restrictions and session revocation, displayCurrency | refused with 400 until implemented, never ignored |
| Promotions, free rounds, jackpots, tournaments | specified separately |
detailsUrl support pages, archived-round jobs (older than the hot window) | lookups cover the hot window |
| Operator-API conformance suite (OCS) | the interop script in this repository is the starting point; the wallet kit above is available |
| Hosted docs portal with an API reference and signature debugger | this guide is the first version |
If something you need is in the last table, tell us early: several of these are decided and only waiting for the first partner's priorities.