---
name: paperboy
description: Use Paperboy to suggest SEO topics for a site, write a fact-checked article, fact check any URL or draft, publish, and read Search Console performance. Use when the user asks about blog content, SEO articles, fact checking claims or sources, or how their articles are ranking.
---

# Paperboy

Paperboy writes SEO articles and fact checks every cited claim against the saved text of its source.
Docs: https://paperboyseo.com/docs

## Setup

Needs the Paperboy MCP server, or an API key in `PAPERBOY_API_KEY`.

    claude mcp add --transport http paperboy https://paperboyseo.com/mcp --header "Authorization: Bearer pb_live_..."

Never write the key into a file in the project.

## Tools and credit costs

- `get_sites`: list sites. Free. Always start here to get the site id.
- `suggest_topics`: next articles with the reason for each. 1 credit.
- `write_article`: start an article. 12 credits, back if it fails. Returns an id at once.
- `get_article`: status, verdict and sources. Free. Poll every 30 seconds after `write_article` until the status is `published` or `needs_review`.
- `check_claims`: fact check a URL or pasted Markdown. 2 credits.
- `publish_article`: publish an article that passed. Free.
- `get_performance` and `get_queries`: Search Console clicks, impressions, position and queries. Free.

## Rules

1. Say what a call costs before you make a spending call, and ask first when the user did not ask for it.
2. Never publish without the user's go-ahead. Leave `publish` at false in `write_article`, show the article and the verdict, then call `publish_article` only after they approve.
3. If the verdict has a failed check, show the flagged claims and their fixes. Do not publish around it.
4. If a call says `payment_required`, tell the user to add credits at https://paperboyseo.com/app/settings/api. Do not retry.
5. Reading data is free. Prefer `get_performance` before suggesting new topics.