> ## Documentation Index
> Fetch the complete documentation index at: https://docs.seosorted.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Plans, credits and limits

> What an agent can spend, what it needs Pro for, and how scopes narrow a key.

An agent works inside exactly the same limits you do. There is no separate MCP allowance and
no way for a connected agent to do something your plan does not include.

## Monthly credits

|                     | Free | Pro                             |
| ------------------- | ---- | ------------------------------- |
| Articles            | 3    | 30 *(60 or 90 with the add-on)* |
| Site audits         | 1    | Unlimited                       |
| Keyword lookups     | 100  | Unlimited                       |
| AI visibility scans | 1    | 30                              |

Credits are shared between the dashboard and MCP — an article the agent writes is the same
credit as one you write yourself. They reset on the first of the month.

Article credits are counted when a generation **completes**, not when it starts. The MCP
response accounts for in-flight jobs so an agent cannot start more than you can afford.

## Pro-only tools

`list_integrations` and `publish_article` need a paid plan.

They stay visible on the Free plan rather than being hidden, with `[Pro]` in the description,
so the agent can tell you *"publishing needs Pro, here's the link"* instead of wrongly
concluding SeoSorted cannot publish at all. Calling one returns your upgrade link.

## Scopes

You choose these on the approval screen when you connect. They narrow access further,
independently of your plan.

| Scope     | Grants                                                                      |
| --------- | --------------------------------------------------------------------------- |
| `read`    | Everything read-only: profile, keywords, articles, audits, jobs             |
| `content` | Spending credits: `research_keywords`, `run_site_audit`, `generate_article` |
| `publish` | `publish_article`                                                           |

**Publishing is unticked by default.** A connection without it cannot write to your website
even on Pro, even with the right role — the check runs when the tool is called, not just when
the list is built. Tick it only for an agent you want publishing.

## Roles

A connection acts as the person who approved it, and their role is re-checked on every call.
Demote them from Admin to Editor and every connection they approved drops to Editor
immediately. Remove them from the workspace and their connections stop working.

| Role              | Can                                       |
| ----------------- | ----------------------------------------- |
| `VIEWER`          | Read-only tools                           |
| `EDITOR`          | Generate, research, audit, publish        |
| `ADMIN` / `OWNER` | The above, plus minting headless API keys |

## Rate limit

**120 calls per minute, per connection.**

This exists because agents loop. It is not a plan limit — a Pro workspace with unlimited
keyword lookups is still capped here, because "unlimited" is sized for a person clicking, not
a script. Exceeding it returns a message telling the agent to batch its work and retry.

## When something is blocked

Errors are written for the agent to act on, not to hide the reason. Running out of article
credits returns:

> You've used all 3 articles available on the Free plan this month. Your limit resets on
> 1 September. Upgrade: [https://seosorted.ai/dashboard?tab=billing-subscription\&ws=](https://seosorted.ai/dashboard?tab=billing-subscription\&ws=)...

A lapsed subscription reads differently from never having had one — *"Publishing stopped with
your plan. Resubscribe to continue"* rather than *"Publishing is a Pro feature"* — so the
agent tells you the right thing.

## What gets recorded

Every tool call is logged with the connection that made it, the tool, how long it took and
whether it succeeded. If you ever need to answer *"what did the agent do to my site"*, there
is a record.

Credits spent through MCP are attributed to the connection, so MCP usage is distinguishable
from dashboard usage on your billing page.