Skip to content

MCP and API

API keys and limits

Create, scope and revoke the keys that the MCP server and REST API use, and the limits that apply to them.

One key works for both the MCP server and the REST API. Keys belong to your user account, and you manage them in Settings → API & MCP.

Create a key#

  1. Name it after where it will live

    Use names like "Claude Code" or "Reporting script", so you know which key to revoke if one leaks. Names can be up to 60 characters.

  2. Choose its projects

    All my projects covers every project you own or have joined. Only (project name) limits the key to one project. With a single-project key, you can leave out project_id in tool calls.

  3. Choose its access

    Read only can read articles, Search Console and Analytics data, the content plan and rank tracking. Read & write can also add and edit content plan items, start article generation, edit article drafts and change tracked keywords.

  4. Copy it now

    Click Create key. The full key is shown once, then only its first characters (for example sf_live_a1b2c3…). If you lose it, create a new key and revoke the old one.

A newly created key, shown once with its copy button

Send the key#

Send it as a bearer token on every request:

http
Authorization: Bearer sf_live_your_key_here

An X-API-Key: sf_live_your_key_here header works too.

Revoke a key#

In the Active keys list, click the trash icon next to the key and confirm. Anything using it stops working immediately. Each row shows when the key was created and last used, which helps you spot keys you no longer need.

You can have up to 10 active keys at a time.

Who can use the API#

API and MCP access is included in every paid plan and during your trial. A key stops working while your subscription is inactive, and returns 402 subscription_required until you reactivate it. Keys don't expire otherwise.

A key can only read projects you own or have been invited to. A project that isn't on a paid plan returns 402 project_unpaid.

Limits#

LimitValue
Requests60 per minute, per key
Active keys10 per account
Paid SEO dataAbout 5,000 credits a day per account, free during the beta. Resets at 00:00 UTC
Article generationCounts toward your plan's monthly articles
Tracked keywordsCount toward your plan's keyword limit

When you go over the request limit, the response is 429 rate_limited with a Retry-After: 60 header.