Credits, not seats you never use
Every capability is priced in credits. A run tells you its cost before it starts, so there is no run-away spend and no surprise invoice.
- api: false
- sso: false
- seats: 2
- schedules: 2
- workspaces: 1
- competitors: 3
- tracked keywords: 50
- api: true
- sso: true
- scim: true
- seats: 10000
- schedules: 10000
- workspaces: 1000
- competitors: 100
- audit stream: true
- ip allowlist: true
- tracked keywords: 1000000
- api: false
- sso: false
- seats: 5
- schedules: 20
- workspaces: 3
- competitors: 10
- tracked keywords: 1000
- api: true
- sso: false
- seats: 20
- schedules: 200
- workspaces: 15
- competitors: 25
- tracked keywords: 10000
What credits buy
Each capability is billed for the work it does — a run over twenty keywords costs more than a run over one, and the price is shown before you commit.
Playbooks
A playbook runs several steps in one go. Pick the shortest one that answers your question.
Questions people actually ask
What happens if a run fails?
Credits are returned when a run stops before producing a result. A run that fails part-way is refunded in proportion to the work it did not do.
Do I need my own provider keys?
No. Search and model access are configured once for the platform. You never enter an API key.
Can I see the cost before running?
Yes — every run is priced first, and the Copilot asks before starting anything expensive.
Where does the analysis come from?
From the live result set for your keywords: the pages that rank, measured with the same method, then tested for which differences matter.
Plans include a monthly credit allowance. Runs are priced in credits before they start, and unused credits roll over for 30 days. Plans and allowances shown here are the current list; your workspace shows the price you are on.