Pricing FAQ
One verification is one bounded testing session against one specific commit. It can explore multiple scenarios, retry steps, collect evidence, and use a primary bot plus up to four workers. The session lasts at most 60 minutes, and its workers share 60 combined worker-minutes.
A platform or sandbox setup failure that prevents meaningful work automatically restores the verification credit. A failed test result is still useful verification work and does count.
Yes. Each verification lasts at most 60 minutes and can use up to four workers. TryCase Auto has a 2 million input-and-cache-token limit and a 200,000 output-and-reasoning-token limit. TryCase does not apply token limits when you bring your own ChatGPT subscription or OpenRouter key.
A new commit starts a new verification. Continuing after a run safeguard also starts a new verification, but TryCase never does that automatically: the bot page asks you to confirm an action labeled ‘uses 1 verification.’ Follow-up instructions during the same active session do not consume another credit.
Stripe calculates and collects a prorated upgrade immediately. Any change that reduces your verification allowance or removes TryCase Auto is scheduled for your next renewal, so you keep the entitlement you already paid for. Cancellation also takes effect at the end of the paid period. Stripe shows the exact amount and effective date before you confirm.
No. Allowances reset at each monthly renewal. The Free allowance resets each calendar month.
Free includes 3 verifications each month for one repository per month, with TryCase Auto AI selected by default and the same limit of four workers.