Skip to content
Roblette
Developers

Give an agent a seat.

Everything a player can see, an agent can read. Everything a player can do, an agent can prepare. Nothing is signed here: your wallet signs, the treasury enforces the limits, and the same gates apply to everyone.

API beta · 1.0.0-beta
Fig. 01 · Execution pathAPI never signs. The agent wallet signs.
Agent01
reads · verifies · quotes · builds intents
API02
/api/v1 · MCP · returns unsigned intents
Wallet03
signs · the only key holder
Contract04
RiskEngine.checkWager · reverts over cap
Table05
round · commit–reveal result
Intents carry to · chainId · data · abi · descriptionTestnet
Capabilities01

Read, verify, quote, build intents. Never sign.

Roblette exposes one machine interface in two shapes: a JSON REST API under /api/v1 and an MCP server that wraps it. Any agent framework that can make an HTTP request or speak the Model Context Protocol can use it.

  1. Read
    01

    Tables, limits, treasury snapshot, reward inventory, settled rounds and outcome counts. Public, cacheable, CORS-open.

  2. Verify
    02

    Recompute keccak256(serverSeed) against the commitment and derive the pocket for any round. Pure math over your input.

  3. Quote
    03

    Run the exact pre-acceptance check the table runs: payout per bet, worst-case liability and whether it fits under the per-round cap.

  4. Build intents
    04

    Get unsigned calldata for enterTable, placeBets, leaveTable and claimAs. The intent names the contract, chain id, ABI and args. You sign it, or you do not.

Responses share one envelope: { ok, demo, data } or { ok: false, error: { code, message } }. Every route reads the deployed contracts on Robinhood Chain through a cache of a few seconds, and every response says so with demo: false. When the chain cannot be read the answer is CHAIN_UNAVAILABLE, never substitute data. Amounts are whole chip units; USD figures are derived from the treasury's chip peg and labelled as such.

Safety model02

The wallet signs. The treasury decides. The gates apply to everyone.

  • 01No custody, no signing. Write routes return unsigned transaction intents with to, chainId, data and a human-readable description. The API never sees a private key. An agent that cannot sign cannot move anything.
  • 02Limits are enforced before acceptance, on chain. The quote shows you the result of the solvency check in advance, but the contract re-runs RiskEngine.checkWager over the whole round and reverts if the worst-case payout exceeds the per-round exposure cap. There is no API path around it.
  • 03Same rules as humans. Agents are bound by the same age, jurisdiction and responsible-play gates as human players. Stock Token settlement is jurisdiction-gated regardless of who prepares the transaction. See Responsible Play and Restricted Jurisdictions.
  • 04Verifiable outcomes. Every round carries its commitment, revealed seeds and block reference. Agents should re-verify what they observe; the derivation is public and identical to the one on the Fairness page.
  • 05Neutral data. The stats endpoint describes the past. It is not a signal; every spin is independent and the documentation says so wherever counts appear.
Intent shape
{
  "to": "0x…",                 // the deployed contract
  "contract": "RouletteGame",
  "chainId": 4663,               // Robinhood Chain
  "value": "0",
  "data": "0x…",               // ABI-encoded calldata your wallet signs
  "abi": { "name": "placeBets", "signature": "placeBets(uint256 roundId,(uint64 numbersMask,uint16 multiplier,uint128 stake)[] bets)", "args": [...] },
  "description": "Place 1 bet(s) on round 246: Red 10.",
  "warnings": ["Unsigned intent. Review calldata and sign with your own wallet; this API never holds keys.", ...],
  "signedBy": "agent-wallet"
}
Quickstart03

Three calls to understand the protocol.

1 · Health
curl -s https://<host>/api/v1/health | jq .data.chain
2 · Quote a bet set
curl -s -X POST https://<host>/api/v1/quote \
  -H 'content-type: application/json' \
  -d '{"bets":[{"betId":"red","stake":10},{"betId":"straight:17","stake":1}],"table":"1"}' \
  | jq '{accepted: .data.accepted, maxNetPayout: .data.maximumLiability.maxNetPayout, cap: .data.limit.maxRoundExposure}'
3 · Verify a round
BODY=$(curl -s https://<host>/api/v1/rounds/109 | jq .data.verify.body)
curl -s -X POST https://<host>/api/v1/verify \
  -H 'content-type: application/json' \
  -d "$BODY" \
  | jq .data
4 · Prepare a seat (unsigned)
curl -s -X POST https://<host>/api/v1/intents/enter-table \
  -H 'content-type: application/json' \
  -d '{"address":"0xYourWallet"}' \
  | jq '{to: .data.intent.to, data: .data.intent.data, approveFirst: (.data.prerequisites | length), error: .error.code}'

Bet ids are stable strings: red, dozen:2, straight:17, split:17-20, corner:25. Stakes are chip units. On chain, a bet is { uint64 numbersMask, uint16 multiplier, uint128 stake } where bit i of the mask is pocket i; the intent builder does the conversion.

MCP server04

Seventeen tools, stdio transport, zero keys.

The MCP server lives in agent/mcp of the repository. It is a thin client over the REST API: every tool calls an endpoint and returns the structured result, so there is exactly one place where limits and encodings are defined.

Claude Desktop · claude_desktop_config.json (or any MCP client)
{
  "mcpServers": {
    "roulette": {
      "command": "bun",
      "args": ["run", "/path/to/repo/agent/mcp/src/index.ts"],
      "env": { "ROULETTE_API_URL": "https://<host>" }   // optional: defaults to the production site
    }
  }
}
Tools17 · stdio
  • get_health
  • list_tables
  • get_table
  • get_treasury
  • get_limits
  • list_rewards
  • list_prices
  • list_rounds
  • get_round
  • get_stats
  • verify_round
  • quote_bets
  • build_enter_table_intent
  • build_place_bets_intent
  • build_leave_table_intent
  • build_convert_to_rewards_intent
  • build_claim_intent

The five build_* tools take your wallet address, check its onchain balances and return intents, not receipts. Hand them to the wallet integration your agent already trusts.

Endpoints05

Nineteen routes under /api/v1.

MethodPathPurpose
GET/api/v1/healthChain and deployment status
GET/api/v1/tablesTables with effective limits
GET/api/v1/tables/{id}One table
GET/api/v1/treasurySolvency snapshot and per-round cap
GET/api/v1/limits?multiplier=35Max safe stake for a payout multiplier
GET/api/v1/rewardsReward inventory and statuses
GET/api/v1/pricesReward asset prices
GET/api/v1/roundsSettled rounds with fairness proofs
GET/api/v1/rounds/{id}One round, with a ready verify body
GET/api/v1/statsOutcome counts over a window
POST/api/v1/verifyRecompute a commit–reveal proof
POST/api/v1/quoteValidate bets against the treasury limit
POST/api/v1/intents/enter-tableUnsigned enterTable
POST/api/v1/intents/place-betsUnsigned placeBets
POST/api/v1/intents/leave-tableUnsigned leaveTable
POST/api/v1/intents/convert-to-rewardsUnsigned CasinoTreasury.convertToRewards (chips to a win balance, one-way)
POST/api/v1/intents/claimUnsigned RewardVault.claimAs
GET/api/v1/openapi.jsonOpenAPI 3.1 document
GET/api/v1/datasetsDataset catalog

Reads are cached briefly and allow any origin. POST routes are lightly rate limited per client. Errors use stable codes: VALIDATION_ERROR, NOT_FOUND, RATE_LIMITED, TABLE_LIMIT, CONTRACTS_NOT_DEPLOYED, and for intents whose precondition is not met on chain: ROUND_NOT_OPEN, INSUFFICIENT_ESCROW, NO_CHIPS, INSUFFICIENT_CHIPS, ASSET_UNAVAILABLE, INSUFFICIENT_WIN_BALANCE, PAUSED. CHAIN_UNAVAILABLE means the chain could not be read.

Datasets06

What you can pull, how often it changes.

DatasetEndpointRefreshFieldsSource
Settled rounds with fairness proofs
Rounds settled on chain with commitment, revealed seeds, block reference and result. Each row is independently verifiable with POST /api/v1/verify; any round id can also be read directly at /api/v1/rounds/{id}.
GET /api/v1/roundsPer settled round (the operator opens rounds only while a player is seated)14Live
Outcome distribution
Descriptive counts (color, parity, dozen, column, half, pocket histogram) and chip units staked/returned over rounds settled on chain inside the scanned block window. Neutral language only: every spin is independent.
GET /api/v1/statsPer settled round7Live
Treasury solvency snapshot
Bankroll, reserved liabilities, claimable rewards, protocol and safety reserves, available bankroll, per-round exposure cap and collateralization, in chip units with wei and peg-derived USD alongside.
GET /api/v1/treasuryPer deposit, wager, settlement or claim9Live
Tables, limits and the current round
Every on-chain table with its stake range, treasury-backed effective limits, the round in flight (or null) and what the round operator is waiting for.
GET /api/v1/tablesPer round transition9Live
Reward vault inventory
Assets registered on the reward vault with on-chain status, inventory in token units, the posted oracle price and its age. Registry entries the vault does not hold are listed as not yet listed.
GET /api/v1/rewardsOn inventory funding, claim or oracle post (about every 5 minutes)9Live
Posted oracle prices
The USD price last posted to the on-chain oracle for every asset registered on the reward vault, with its timestamp, age and a staleness flag. No off-chain price feed is consulted.
GET /api/v1/pricesPer oracle post (about every 5 minutes)6Live
Fairness proof verification
Stateless recomputation of commitment and result for any round tuple. Useful for auditors and agents that re-verify every round they observe.
POST /api/v1/verifyOn demand (POST)4Live

Field dictionaries, provenance and licensing notes for each dataset are in /api/v1/datasets. The fairness-proof route is pure math over your input.

Status07

Beta, independent.

BetaSchema may change before v1.1. Pin to X-API-Version.

Roblette is an independent product built on Robinhood Chain. It is not affiliated with, endorsed by or operated by Robinhood. The API is in beta and reads the deployed contracts on Robinhood Chain; intents are checked against your wallet's onchain balances and are never signed here. Nothing on this page is an invitation to wager where that is not lawful, and no availability, licence or audit is claimed. Contracts are NOT YET AUDITED.

Explorer: robinhoodchain.blockscout.com. Architecture and contract roles are on the Technology page.