Environments and limits
Test and live environments, test players and reset, the free allowance and its grace.
Every project starts with one test environment and one live environment. You choose the
kind when you add an environment (POST /v1/projects/{id}/environments with name and kind,
or Settings → Environments & keys); the name is free-form ("staging", "playtest") and renaming
never changes the kind or billing. GET /v1/environments/{id} answers kind and test_mode.
Test environments
- Free. Outbound delivery is simulated: notifications through your own connectors (Klaviyo, Braze, OneSignal, FCM) and commerce fulfilment requests are recorded as sent or fulfilled without reaching anyone. Built-in email and push go to a fake provider.
- Webhooks to your own servers still fire, with
"test_mode": truein the signed envelope, so your receiver can keep test traffic apart. Customer sessions answertest_mode: true, and the hosted portal and widget show a permanent Test mode banner. - 25 test players per test environment since its last reset. Every customer created counts,
anonymous ones included, whichever way it is created (events,
POST /v1/customers, match results, imports). An existing id or a replayed request counts nothing; merging or deleting a customer gives no place back. The next new player answerstest_player_limitwithused,limitand the hint to reset.GET /v1/environments/{id}/test_playersshows the count. - Reset test environment (
POST /v1/environments/{id}/reset, owner or admin, also reachable from MCP) deletes every test player with their balances, progress, memberships, rankings, sessions and pending deliveries, and keeps the configuration (rules, programs, rewards, keys, webhooks). While it runs, new players are refused (test_environment_resetting); work aimed at a deleted player is refused. Usage, AI and abuse budgets are not reset. - The organization's test environments share 100,000 test events a month; above that, test
events answer
quota_exceeded.
Live environments and the free allowance
Every live environment of the organization, in every project, shares one allowance:
- 10,000 actions per organization each UTC month are free, then $0.25 per 1,000 actions. No subscription fee. Reads, replays and work already accepted never count again.
- At 80 % and 100 % of the free actions, owners get a dashboard notification and an email.
- With a payment method (Settings → Billing), work continues past the free actions and is billed.
- Without one, a one-time grace starts: up to 10,000 more actions or 7 days, whichever comes
first, never charged. Owners are told when it starts and when it ends. After it, new billable
work answers
402 free_allowance_exhausteduntil a payment method is added; reads, replays, processing already accepted, recovery and test environments keep working. - The free plan allows up to 5 projects.
Organizations an agent signed up
Until a verified person claims the project, it has test environments only: the live environment
answers live_requires_claim to billable work, and no live environment can be added. After the
claim the free allowance above applies.
Pricing and billing
Launch pricing: 10,000 actions free per organization each month, then $0.25 per 1,000. What counts as an action, how small charges accrue until $5, and how billing works in the dashboard.
Recipes
One-prompt integrations by stack for an AI agent: web games, Unity, Godot, React Native and Expo, Roblox, Firebase and Supabase.