Skip to content
Sign inStart free trial
Docs

Connect an AI agent

Create a read-only agent key in the client's settings, then connect Claude Code with one terminal command. The agent can list the client's open fixes in priority order and read one fix's searches, evidence and instructions, including what not to change. It can't edit the site or mark fixes done; you log its change note.

What it doesn't do: The agent reads the latest synced data. Fetching fixes never runs a sync, spends credits or changes a fix's status.

Updated

The copy prompt for one fix: the client, page, issue, searches, evidence, fix and what not to change.
Client › Opportunities › Copy prompt · Sample data

1. Create a key

Open the client, then Settings › AI agent, and click Create read-only key. Keys start with rua_, cover one client and are stored as a hash. Copy the key right away: “It won't be shown again after you leave this page.”

The same panel has Replace key and Revoke access, and shows when the key was last used.

2. Connect Claude Code

In the site's project folder, run the command the panel shows. It already holds the client's ID and, right after you create a key, the key itself:

claude mcp add --transport http --scope local rankupside-<client id> https://rankupside.com/api/mcp --header "Authorization: Bearer YOUR_API_KEY"

The connection is saved for that project only. Open Claude Code in the same folder.

3. Ask for the fixes

Try the prompt from the panel:

Pull this client’s SEO fixes. Read the evidence and instructions for the highest-priority fix, then help me implement it.

The agent reads the latest synced data. Fetching fixes never runs a sync, spends credits or changes a fix's status.

The two tools

MCP tools the agent can call
ToolWhat it returnsInputs
list_fixesThe client's open fixes in priority order, each with page, cause, effort and estimated clicks at stake, plus the last sync date.offset, and limit up to 50
get_fixOne open fix's searches, evidence, current page details and complete instructions, including what not to change.The fix's key from list_fixes

Both tools are marked read-only to the agent.

Other agents

Any agent that speaks MCP can use the server URL https://rankupside.com/api/mcp. Agents that don't can call the read-only JSON API with the same key:

curl https://rankupside.com/api/agent/fixes \
  -H "Authorization: Bearer YOUR_API_KEY"

# One fix, with its full evidence and prompt
curl "https://rankupside.com/api/agent/fixes?key=<fix key>" \
  -H "Authorization: Bearer YOUR_API_KEY"
  • Requests from a browser on another website are rejected.
  • Each key gets 60 requests a minute. Past that, the API answers 429 with Retry-After: 60.

Close the loop

When the work is done, open the fix in RankUpside and click Mark done with the agent's change note. The prompt asks the agent to end with that one-line note. Tracking then compares the page with the 4 weeks before the change, for 8 weeks, and reads “consistent with the change” when it moves.

How fixes are ranked: Ranked fixes. What the key can and can't reach: Data and permissions and Security.

Prefer pasting?

Copy prompt on any fix, or Copy all on the fix list, works without a key. Paste it into any AI assistant. Revoking a key doesn't affect it.

Something missing or out of date? Email hello@rankupside.com.

Questions.

Can the agent change my client's website through RankUpside?
No. The key only reads that client's open fixes. Any edit happens in your own project, where you review it.
Does an agent key work for every client?
No. Each key is limited to one client. Create a separate key in each client's settings.
What happens when I revoke a key?
Agents using it stop reading that client's fixes right away. Copy prompt still works.
Is the fix data sent to Anthropic or other AI companies?
Only when you connect an agent or paste a prompt. What you send is then handled under that AI service's terms.