Free
Explore the platform
Free
- Browse the product
- Connect GitHub
- Buy tokens to unlock workflow access
Pick a plan quickly, compare the self-serve tiers side by side, and expand the policy details only when you need them.
Start free, then move into billing when you need more workflow capacity or recurring token quota.
Explore the platform
For individual developers
For heavier workflow usage
For larger workflow capacity needs. This tier is for organizations that need higher workflow capacity or billing coordination before starting.
The main tradeoff between plans is scale, not hidden unlocks.
Paid plans include recurring platform token quota before purchased tokens are used.
Documentation, Web Reader, JavaScript REPL, and Browser Run consume the same shared token pool as workflow usage.
Paid tiers raise workflow concurrency and rate limits without changing the core product surface.
Plan quota is spent first, then non-expiring purchased tokens keep workflows moving.
Documentation, Web Reader, JavaScript REPL, and Browser Run share your plan quota and fall back to pay-per-use.
Look up up-to-date library documentation and code examples
800 tokens per use
Shared allocation: plan quota first, purchased tokens second
Fetch public web pages and return bounded readable text for analysis
1,600 tokens per use
Shared allocation: plan quota first, purchased tokens second
Run JavaScript-only snippets for small computations and caller-declared HTTPS reads, not shell commands or repository files
1 tokens per execution second
Shared allocation: plan quota first, purchased tokens second
Run bounded browser tests and rendered-page inspections on caller-selected HTTPS targets or sandbox previews
72,000 tokens/browser hour
Billed by started browser execution seconds
Shared allocation: plan quota first, purchased tokens second
Paid plans include recurring platform token quota for workflows and tools. Purchased tokens are used after plan quota and never expire.
You can keep going with purchased tokens. Recurring plan quota refreshes automatically on its normal schedule.
Paid plan changes are handled through Stripe Checkout or the Stripe Billing Portal and update after Stripe confirms them.
No. Polka Codes uses platform-managed model routing, so there is no provider setup required.
Tool invocations and elapsed execution seconds consume tokens. Plan quota is spent first, then non-expiring purchased tokens are used automatically.
No. Purchased tokens are non-expiring and remain available after your plan quota resets.
Sign in to continue into chat or billing, or contact us if you need an enterprise rollout.