Pricing & billing
The unit is the Polis token. One number you spend, with a visible balance and a monthly reset. You see the exact token cost before every run (polis_estimate). Standard rate: $5 per 1,000 tokens.
Free trial
Every new account gets 200 free trial tokens (no card). You can run tests that fit within your balance immediately. Subscribe for usage beyond the trial.
Plans
| Plan | Price/mo | Included tokens | Per-token |
|---|---|---|---|
| Starter | $5 | 1,000 | standard |
| Pro | $50 | 12,500 | ~20% cheaper |
| Scale | $200 | 55,000 | ~27% cheaper |
Beyond the included tokens, usage is strictly metered at the standard rate ($5/1,000) and billed via Stripe. The higher tiers are a discount on the included bucket. Every account has a monthly spend limit (default $25); runs that would exceed it are blocked before any charge. No surprise bills.
Token cost of a run
tokens = 60 (base: persona generation + synthesis)
+ persona_count x 1 (text) or x 3 (visual URL)
+ 8 (only for url content)
+ 2/1k tokens of artifact beyond the first 1k,
scaled by persona_count (long content is shown to every persona)Example: 100 personas on a tweet = 60 + 100 = 160 tokens = $0.80. Pass content to polis_estimate for an exact quote on long articles.
Rough costs by scenario
These are computed from the live pricing formula, so they match what you are actually charged. Persona count is the biggest lever; a screenshot (visual url) run costs more per persona than a text run; long content adds a little because every persona sees it.
| Scenario | Polis tokens | Approx. cost |
|---|---|---|
| Tweet / short post, 100 personas | 160 | $0.80 |
| Quick text test, 25 personas | 85 | $0.43 |
| Website (scrape text), 100 personas | 168 | $0.84 |
| Website (screenshot, vision), 100 personas | 368 | $1.84 |
| Website (screenshot, vision), 200 personas | 668 | $3.34 |
| Long article (~3k words), 150 personas | 218 | $1.09 |
| Large run, 500 personas, tweet | 560 | $2.80 |
A screenshot (url + visual) run is roughly 3x the per-persona cost of a text run, because vision-capable models are pricier and the page image is sent to every persona. copy mode (scrape the text) is the cheap way to test a page's message; visual is for testing the actual design.
Always call polis_estimate first. Tokens for runs that fail before producing a report are refunded automatically.
A human completes Stripe Checkout (agents cannot pay yet — see the roadmap for agent-native payment).
All docs
- What Polis is: The concept, inputs, and what you get back.
- Agent quickstart: Connect, get a key, run a test, read the report.
- How to run a test: The workflow, a worked example, and how to read the report.
- Test options reference: Every input, every variation, and the full report schema.
- MCP tools: Every tool, its inputs, and cost.
- Pricing & billing (you are here): Polis tokens, plans, free trial, metered usage, spend limit.
- Discovery & well-known endpoints: How agents and clients discover Polis.
Polis docs index · Full machine-readable index (llms.txt) · Everything inlined (llms-full.txt)