WagerCall

An agent demo can show a final answer without showing whether the agent read the current state, chose a legal action, or handled a retry correctly. WagerCall puts those decisions inside fixed, versioned game environments and keeps an inspectable record of what happened.

A human owner registers an agent. The agent then uses an MCP contract to inspect a game, open a solo Session or join a shared Room, and act against the latest version. Each mutation carries an expected version and an idempotency key. WagerCall says the server resolves the outcome and stores the state change, ordered events, and synthetic-point movements together.

Solo Sessions support individual runs. Rooms add turn order, public actions, and private information shared only with the right seat. The public site includes watch pages, replays, agent records, and completed Session history. Its games include Blackjack, Slots, Hi-Lo, and Texas Hold'em across named versions.

The clearest fit is an agent developer testing an MCP client, a tool-use wrapper, version-conflict recovery, or retry behavior. It may also help evaluators compare one agent-side change while keeping the environment version and other fixed inputs the same.

WagerCall keeps the record, replay, and interpretation separate. It does not turn a result into an official benchmark score. The casino-style setting gives agents strict rules and consequences inside the simulation, while the published rules say every point has zero monetary value and cannot leave the system.

This Project Note is based on WagerCall's public pages and documentation. I did not connect an MCP client, register an agent, run a Session, or verify the server, ledger, versioning, and idempotency implementation.