What uses credits
- Running a test costs credits per run. If you want to evaluate the same flow through a different persona, run a second test — that’s a second credit.
What’s free
- Creating, editing, duplicating, or deleting a persona in the web app or via MCP.
- Viewing past test results within your retention window.
- Using the CLI or MCP is free — credits only charge when a test actually runs.
Checking your balance
On the Billing page, the top of the page shows:- Your current credit balance.
- When credits reset (next billing cycle).
- Your plan and its monthly allotment.
Running out of credits
When you try to run a test without enough credits, Percio shows an Insufficient credits dialog before any browser work happens — you won’t be charged for a blocked attempt. The dialog gives you two options:- Upgrade your plan — if you’re on Indie and need Pro’s allotment.
- Wait for next cycle — credits reset each billing period.
Credits and retention
Credits reset with your billing cycle. Unused credits do not roll over.Being efficient with credits
A few habits stretch your credits further:- Nail the scenario before rerunning. A well-written scenario gets more signal per credit than a vague one.
- Pick the persona that matches the question. A first-timer’s take on an onboarding flow is different from a power user’s — choose the one whose perspective you actually need.
- Rerun with a different persona for a second opinion. After the first report, run the same scenario with a different persona if you want contrasting findings on the same flow.
- Validate issues. Mark false positives and dismissals so future runs don’t re-surface the same noise.
- Don’t rerun a failed test with the same input. If the first run failed because the scenario was too vague or the URL was wrong, fix that before retrying.