API reference

Every /v1/ai/* endpoint, live from /openapi.json. One key — admin-issued or self-served in the console — drives REST, A2A and MCP; each tool takes its own smallest scope.

Updated 2026-11-08

On this page

Pick your path

One key — admin-issued or self-served in the console — drives all three. Humans start with REST; agents usually start with MCP.

REST

Copy-paste curl for every /v1/ai/* endpoint, live from openapi.json. Counts against the monthly quota.

Read the reference below

MCP

43 MCP tools for agents on the same key — read-only by default, two writes need confirm; daily limits, never touches the monthly quota.

Plug an agent in

A2A + skill

Agent card plus a read → fix → verify skill loop. Same key, same daily limits as MCP.

Read the skill

Need a key? Create one in Console → Access (Read-only or Read + write) or ask an admin. Authentication covers scopes, presets and failure codes.

Live endpoints

Same origin as this page. Set two variables once per shell — the curls below reuse $SEO_WATCH_KEY, never a pasted secret.

Shell

export API="https://<your-host>"
export SEO_WATCH_KEY=<YOUR_API_KEY>

Paths with {id} need a real id — create a site first and copy it from the response.

Rows expand in place — open one to see params, response fields and a curl example.

Method & path

Loading endpoints…

Errors

Every failure uses { error: { code, message }, requestId? }. Find each code's trigger and fix in the stable error table.