REST + MCP

The REST API and the MCP server.

Create a key in your workspace. Read the list of tools. Call a tool with the parameters described by its JSON Schema.

Get started

  1. Create a personal key under API keys.
  2. Call GET /v1/tools to get the name and parameters of each tool.
  3. Call POST /v1/execute with a tool from the catalogue.
Manage my keys

REST API

API : https://api.tagavo.com

TAGAVO_URL="https://api.tagavo.com"
curl "$TAGAVO_URL/v1/execute" \
  -H "Authorization: Bearer $TAGAVO_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: research-unique-request-001" \
  --data '{"tool":"TOOL_FROM_CATALOGUE","arguments":{}}'

Replace TOOL_FROM_CATALOGUE with a tool name and put its required parameters in arguments. Send a unique Idempotency-Key for each analysis (16 to 128 characters: letters, digits, - or _). API keys and account sign-in are separate ways to authenticate.

RouteUse
GET /v1/toolsTool list and JSON Schema
POST /v1/executeRuns an analysis. Idempotency-Key header required
GET /v1/historyYour past analyses
GET /v1/usageUsage counters and limits
GET /v1/watchlistSaved searches and their monitoring state
GET /v1/export?id=REQUEST_ID&format=csvOne analysis result as CSV (or format=json)
POST /v1/reportsJSON or PDF report from 1 to 10 of your successful analyses
GET /v1/alertsYour change alerts

OpenAPI 3.1 ↗

Reports and monitoring

POST /v1/reports combines 1 to 10 of your successful analyses, given by their requestId. Choose kind (niche, tags or seo), format (json or pdf) and locale (fr or en). The report reads the saved results: it runs no new analysis. Any part without data is marked as missing. The report does not promise sales or profit. An analysis that is not yours returns 404. An analysis without a successful result returns 409.

GET /v1/alerts returns your alerts, newest first (50 by default, 100 at most). Each alert gives the search, the date and each figure before and after. Turning on monitoring, running a check and marking an alert as read are done on the site. With an API key, these actions return 403.

MCP

https://api.tagavo.com/mcp

HTTP endpoint: /mcp. Authenticate with your personal key as a Bearer token. MCP 2026 uses server/discover, tools/list and tools/call, without initialize. Use a compatible SDK to supply the required headers and metadata. Older clients can negotiate 2025-11-25 through initialize. tools/list returns only active tools.

In tools/call, put the tool parameters in input and add a unique idempotencyKey. Each tool’s schema is in the tools/list response.

Retry without running two analyses

A 202 response gives the requestId of your queued or running analysis. Read GET /v1/history?id=REQUEST_ID to follow that result without starting another analysis. Wait at least 5 seconds between reads, then increase the delay when needed. Respect Retry-After after a 429 or 503 response. After a dropped connection with no requestId, repeat the same request with the same idempotency key. If the result stays unknown, check its status with the same ID. A new key would start another analysis. Reusing a key with different parameters returns 409.

A confirmed failure releases reserved credits. Attempts remain subject to rate and abuse controls. An uncertain outcome keeps its reservation while it is checked. Unavailable data is never replaced with a made-up value.