Why we publish prices and hand out keys without a sales call
Every aggregator in this market asks you to book a demo before seeing anything. We publish the prices, the limits and the documentation, and issue sandbox keys instantly — because an integrator can evaluate an API far better than a salesperson can describe it.
The standard arrangement
Search for a casino game aggregator and every result offers the same thing: thousands of games from hundreds of studios, and a form. No prices, no limits, no documentation until someone has qualified you.
That is a choice, and it is usually defensible on their side: enterprise deals, revenue-share negotiated per account, integrations that genuinely need hand-holding.
What it costs
It costs the buyer a fortnight. You cannot compare two suppliers without talking to both, and you cannot evaluate an API by talking about it — you evaluate it by calling it and seeing what comes back.
It costs the supplier the developers. The person who will actually integrate you is rarely the person on the call, and they form their opinion in the first hour of reading documentation. If there is no documentation to read, the opinion forms anyway.
What we publish instead
- Prices, with the limits each plan carries, enforced in code rather than described on a slide.
- [The full API reference](/docs), including the wallet contract we expect you to implement and every error code we can return.
- Sandbox keys, immediately, with play money and every game enabled.
- The RTP of every game, and a public verifier for any round we have settled.
The honest caveat
Self-serve suits a smaller, own-built catalogue. We are not aggregating two hundred studios, and if what you need is fifteen thousand titles then one of the aggregators is the right answer and we would say so.
What self-serve buys you is the ability to find that out this afternoon rather than after two calls.
Try it against a real API
Sandbox keys are issued instantly, with play money and every game enabled. No card, no call, and the documentation is public whether or not you sign up.
More notes
- How a provably fair crash round is actually generatedA crash multiplier is derived from a hash of a server seed the operator committed to before the round, combined with a client seed the player controls. Publish the commitment first and anyone can check afterwards that the result was not chosen.
- What a casino wallet integration actually has to doFive endpoints: balance, debit, credit, refund and rollback. The only hard requirement is that debit and credit are idempotent on the transaction id you are given — everything else is detail.
- RTP, house edge and the number operators should actually checkRTP is the long-run share of stakes returned to players; the house edge is what is left. The number worth checking is not the advertised RTP but whether the running game reproduces it — which requires the operator to be able to see their own round history.