Skip to main content
Every game starts with caps on, so no single player and no script can run up your bill. Raise or lower them per game on the game’s Summer Router tab in Studio, or ask your agent: it uses the router.set_settings operation, and you approve the change. Caps reset at midnight UTC and on the first of each month (UTC).

​
Spend caps

A cap counts the cost of finished calls plus the most each running call can cost, so parallel calls never go past it. Each character can also have its own daily caps per player and per game, set on the character.

​
Rate limits

Test turns from Studio and your agent while you build count toward their own cap: $20 per developer per day.

​
When a cap is reached

The call answers limit_reached with the cap’s scope and resets_at, and the game shows its offline line. The player never sees an amount. You see the cap hit in Studio usage, with the place to raise it. Over a rate limit the call answers rate_limited (HTTP 429 with Retry-After). The result’s retry_after says how many seconds to wait; until then the SDK answers rate_limited without asking Summer. Calls from the player’s game count toward that player’s caps and the game’s. Calls from your server in a multiplayer game count toward the game’s caps and call rate.