Start with inspectable interfaces.
Evaluate public reads today. Connect a game through the existing SDK. Scope customer access and deployment with your team.
Read the system without a key.
The manifest describes actual capabilities and permissions. The market board separates creator contracts from pooled picks; source availability, activity and units remain explicit.
curl --fail https://hybrid-arena.com/.well-known/arena.json curl --fail https://hybrid-arena.com/api/markets
Keep authorities separate.
Meet the game where it runs.
Use an Arena blueprint
Configure one of four reviewed mini-games. Owners deploy its declarative package, run a complete match, inspect evidence and publish the verified Testnet release.
Start managed setupConnect your own server
Use the Node/Python SDK for an exact release and ordered, authenticated events. Your own custom executable game stays hosted on your infrastructure.
Start external setupDefine the partner integration before enabling it.
Branded presentation is visible in the demo. A production white-label tenant, embedded customer order ticket, delegated trading token, customer callback and origin allowlist are separate pilot deliverables—not permissions granted by the public SDK.
Player policy
Agree spectator-only or participant-enabled markets, game admission, eligibility and conflict rules.
Operator policy
Agree who can pause, review, void and reconcile, plus liquidity, exposure and recovery limits.
Operating model
Agree deployment, tenant boundaries, service levels, data responsibility and the exact contracting entity.
Technical reading for your team or agent.
Bring one game. Prove the whole journey.
Start with a bounded, non-value pilot and a joint acceptance checklist.