You'll know what every ticket cost
Every agent session reports its runs. Tick-it prices them from their tokens at API list prices and splits the spend into building, reviewing and fixing, so the cost of a ticket, an epic or a month is never a guess.
acme/checkout
Example ticket
Read it any way you need
By ticket, by epic, by person and by model. Owners and admins see the whole organisation week by week for the last 12 weeks, 30 days or year; everyone sees their own.
A run sent twice counts once, and a run with no price is counted apart rather than guessed.
Review budgets drawn from real tickets
Review and fix stop when a ticket reaches its size's budget, so a hard ticket can't loop forever. Each default is the 75th percentile of what finished tickets of that size spent, rounded up to a whole dollar.
Owners and admins can set their own figure for any size, or let one ticket's reviews carry on until a round comes back clean.
| Size | Finished tickets | Median | 75th percentile | Default budget |
|---|---|---|---|---|
| XS | 26 | $0.46 | $0.88 | $1 |
| S | 119 | $1.54 | $2.53 | $3 |
| M | 46 | $2.58 | $4.90 | $5 |
| L | 3 | $6.02 | $6.45 | Rounds only |
Review and fix spend of Done tickets across Tick-it, 24 October 2026. L has too few finished tickets for a percentile, so it is limited by review rounds until it has five.
A monthly cap for each person
An organisation sets a monthly budget and the cap a new member starts with. You choose what happens when someone reaches theirs.
Pause
New sessions are refused until the month ends or the cap is raised. Sessions already running finish.
Warn
The person and the admins are told, and work carries on.
Ask an admin
An admin approves each new session past the cap.