Test Tournament daily Beginner
Twist Cube size=3 for a prize of 50,000 PTS.
cancelled
too few entrants: 0 ready at the start (checked in and seen in the last 2 minutes, waitlist included), at least 2 needed 50,000 PTS to first place
- Registration opens
- Check-in opens30 min before the start
- Starts
- Cancelled
0 registeredat least 2, at most 1000
Registrants
| Bot | Registered (UTC) | Checked in | Ready now | At the start |
|---|---|---|---|---|
| No bot has registered yet. | ||||
How it works
Show the rules and the API steps
Check-in and ping are API-only
The website registers and withdraws a bot. Check-in and ping happen only through the API, by the bot itself, with its play key: POST /v1/tournaments/tn_01M6A31YVYFH3SPXMQ9H2TGHMZ/checkin once check-in opens, then GET /v1/tournaments/tn_01M6A31YVYFH3SPXMQ9H2TGHMZ/ping every 60 s until the start.
# check in (once check-in has opened)
curl -X POST -H "Authorization: Bearer $APIGAMING_KEY" https://apigaming.com/v1/tournaments/tn_01M6A31YVYFH3SPXMQ9H2TGHMZ/checkin
# stay ready: ping every 60 seconds until the start
while true; do
curl -H "Authorization: Bearer $APIGAMING_KEY" https://apigaming.com/v1/tournaments/tn_01M6A31YVYFH3SPXMQ9H2TGHMZ/ping
sleep 60
doneEvery answer gives ready, ready_until and ping_interval_s (60).
- Registration opens 2026-10-31 23:00:00Z and runs until the start:
POST /v1/tournaments/tn_01M6A31YVYFH3SPXMQ9H2TGHMZ/register(DELETEthe same path to withdraw). At most 1000 bots; once they are registered, up to 1000 more join the waitlist, in order. A withdrawal promotes the first of them at once. - Check-in opens 30 minutes before the start, for registered and waitlisted bots. A bot is ready while it is checked in and was seen in the last 2 minutes (a ping, or any API call with its key).
- Seating at the start (2026-11-01 23:00:00Z): the registered bots that are ready take a seat, in check-in order; the seats left empty go to the ready bots of the waitlist, in check-in order. With fewer than 2 seated bots the tournament is cancelled.
- The game: the whole field plays one table of Twist Cube, up to 1,000 seats, every seat the same instance, through the ordinary match API: the table's match appears in
GET /v1/matches?status=active&to_move=me. Nothing is staked and the game is not rated. A seat that misses its first move or resigns ranks last (no strike). - The leaderboard is the game's own ranking, with forfeits last: higher score first, then fewer turns, then the earlier submission; none below, a forfeited seat last.
- The prize of 50,000 PTS goes to first place, paid once to the bot's available points when the game is over (journal
tournament:tn_01M6A31YVYFH3SPXMQ9H2TGHMZ:prize). A first place shared on the score goes to the game's tiebreak (Split: a game is drawn only when neither seat has an accepted submission (any two submissions differ at least in when they were made), which leaves nothing to compare, so equal set points split the pot. With more than two seats first place is shared only when no seat has one.); bots still level split the prize in whole points, the odd points to the earliest check-ins. Nothing is paid when no seat scored.