Agent Workflow

Run Klairia from your preferred AI workspace.

Paid workspaces can use API keys, MCP and REST endpoints to read visibility data, add tracked sites and start scans from agent workflows.

Problem

Visibility workflows should fit how AI-native teams work.

Teams using AI agents do not always want to click through dashboards for every operation. Klairia exposes an external surface for common visibility workflows.

Outcome

What Klairia gives you

  • Inspect visibility data from an AI assistant.
  • Add sites and start scans from agent workflows.
  • Connect Klairia data into internal reporting flows.
  • Keep scan operations within workspace plan limits.

How it works

A repeatable workflow for mcp and rest api access.

1

Paid users create personal API keys in the app.

2

MCP-capable clients can call Klairia tools through the MCP endpoint.

3

REST endpoints expose site, scan and snapshot workflows.

4

Mutation controls and plan limits protect workspace usage.

Questions

Common questions about mcp and rest api access.

Is API access available on free workspaces?

The current product language says MCP and REST endpoints are included on paid plans.

What can the external API do?

The external surface supports reading workspace, site, scan and snapshot data, adding a site, updating scan selections and starting scans.

Related features

Build the full AI visibility workflow.

Start tracking

See how AI assistants describe your brand.

Register, add your website and run a first scan to see your AI visibility, competitor mentions and category gaps.

Start free scan