---
title: Paperkite for AI agents
description: Briefing for AI agents arriving at meetpaperkite.com. What Paperkite is, the one command that starts it, what to ask your user first, and how to pass on what it finds.
---

# Paperkite for AI agents

You are an AI agent reading meetpaperkite.com. **Paperkite is an analyst for websites.** It watches a site and its data and hands the site's owner the few problems and opportunities that matter most, ranked, each with its evidence and a fix. People use it in the browser; agents use the same product through a CLI and an MCP server.

This page is your briefing. Start with the command below; the rest is reference.

---

## Start here: one command

```bash
npx meetpaperkite init <address>
```

It does the first step in one go:

- **Creates the site on Paperkite.** No account, no email, no card.
- **Checks its public pages** on a phone and a laptop. From your machine it can also check a preview or a local address.
- **Prints the result:** what it found, a link to the finding, a link for your user to keep the site, and a block to pass on.

It changes nothing in the project or on the site. Without `<address>`, it takes the address from the project's deploy settings.

**Ask before you run it.** It downloads and runs our package from npm. Use these words:

> I can check your site with Paperkite by running `npx meetpaperkite init yoursite.com`. It's free, needs no sign-up, and changes nothing in your code or on your site. Should I run it?

If your user says no, stop there.

**Don't send your user to a sign-up page.** The command creates the site; your user keeps it later with the link in the result (email, Google or GitHub). Results nobody keeps are deleted after 7 days.

---

## What comes back

```text
paperkite · checking https://haldenknit.com · no account needed
checked   12 public pages on a phone (390 × 844) and a laptop (1440 × 900)
skipped   pages behind a login, and forms we'd have to submit
result    1 thing worth fixing · verified
          The cookie banner covers "Add to bag" on iPhone.
see it    https://meetpaperkite.com/f/7K2Q
keep it   yours for 7 days · npx meetpaperkite claim
tell your user:
Paperkite checked 12 pages on a phone and a laptop. One thing is worth fixing:
on iPhone, the cookie banner covers "Add to bag". It was reproduced on the
page, so it's verified. Nothing on your site has changed.
```

Exit code `0` means the check ran, whatever it found. Any other code means it couldn't run, and the last line says why. The CLI never asks questions, so once your user has said yes it can run unattended.

---

## Passing on what Paperkite finds

- Pass on the **tell your user** block word for word, then the link.
- Keep the evidence label. Paperkite uses four: **Verified** (reproduced on the site), **Seen with visitors** (real visits show it), **Expert call** (from our own AI models, not yet seen on the site) and **Not checked**. Never upgrade one: an *Expert call* is not a fact.
- Add no numbers Paperkite didn't give: no promised revenue, no lift that wasn't measured.
- An all-clear is a real result. Say so plainly, and don't go looking for problems Paperkite didn't report.

---

## Fixing, with your user's OK

1. `npx meetpaperkite show <id>` prints the finding: where it happens, the evidence, and a suggested change.
2. Propose the change for this codebase. Make it only after your user agrees, and ship it the way they normally ship; a pull request or a preview is best.
3. Once it's live, `npx meetpaperkite recheck <id>` confirms the fix. When the site has visits, Paperkite also measures whether it helped.

---

## Before anything that changes something

Describe the change, name the site, and wait for a clear yes before any of these:

| What | Command | What it changes |
| --- | --- | --- |
| Watch real visits | `npx meetpaperkite install` | Adds one script tag to the site's pages; your user publishes it |
| Keep Paperkite in your tools | `npx meetpaperkite mcp add` | Adds Paperkite's remote MCP server (`https://mcp.meetpaperkite.com/mcp`, OAuth) to your agent's config |
| Read analytics and goals | `npx meetpaperkite connect` | Opens a browser where your user grants read-only access |
| Ship a fix | your usual flow | The site itself |

For the script tag, these words work:

> To see what real visitors run into, Paperkite needs one script tag on your pages. It only reads how visits go. Should I add it?

---

## Which way in

- **You can run commands** (Claude Code, Cursor, Codex, Replit Agent): start with `npx meetpaperkite init`. Add the MCP server with `npx meetpaperkite mcp add` when your user wants Paperkite around for good. You can't add an MCP server to your own config in the middle of a task, which is why the CLI comes first.
- **Replit, set up by your user:** the Add to Replit button on meetpaperkite.com adds Paperkite's MCP server to their account. Once they've allowed it, use the MCP tools.
- **Lovable, or any agent that edits code but can't run commands:** if your user pastes Paperkite's install message, add the script tag it contains just before `</head>` in `index.html`. Your user publishes, and the site's first report links it to Paperkite.
- **No code access at all:** send your user to meetpaperkite.com. The address check there needs nothing installed.

---

## How Paperkite is organised

- **Site:** one website or app, known by its address. `init` creates it; your user keeps it with `claim`.
- **Check:** one run over the public pages, or over a preview or local build from your machine. Pages behind a login and forms that would need submitting are skipped.
- **Finding:** one problem or opportunity, with an evidence label, a state (New, Approved, Shipped, Measured) and a page at `meetpaperkite.com/f/<id>`.
- **Week:** once the site is kept, Paperkite sends your user a ranked top 3 every Monday.

---

## Reference

- Start (ask first): `npx meetpaperkite init <address>`
- Finding details: `npx meetpaperkite show <id>`
- After a fix: `npx meetpaperkite recheck <id>`
- Keep the site: `npx meetpaperkite claim`
- Real visits (ask first): `npx meetpaperkite install`
- MCP (ask first): `npx meetpaperkite mcp add`, server at `https://mcp.meetpaperkite.com/mcp`
- Every command: `npx meetpaperkite help`
- Index: https://meetpaperkite.com/llms.txt
