Bring your data into the agent you already use

---
name: meev-data
description: Answer questions about the user's own search and AI-search performance by calling meev's read-only REST API (meev.ai) — rankings, AI visibility and citations, competitors, backlinks, content, topical authority, and keyword gaps for the domains the user owns. Use when the user asks where they rank, whether AI answers mention or cite them, who is outranking them, which pages lost traffic, or what to write next.
---

# meev data

Answer the user's questions about their search + AI-visibility performance by
calling meev's read-only REST API. Every result is scoped to the domains the
user owns. The API can only read: it never edits, publishes, or spends, so never
tell the user you changed anything on their behalf.

## Setup (once)

1. The user mints an API key at
   https://meev.ai/dashboard/settings/api-keys — it's shown once, so they copy
   it immediately. Store it as `MEEV_API_KEY` in the user's secrets manager
   (`.env.local` for local dev, the platform's env store for deployed apps).
   Never commit it or print it back in full.
2. Base URL: `https://meev.ai/api/public/v1`
3. Send the key on every request as an `x-api-key` header (or
   `Authorization: Bearer <key>`).

## How responses work

- Success: `{ "success": true, "data": ... }`.
- Failure: `{ "success": false, "error": { "code": "...", "message": "..." } }`
  with the matching HTTP status (400 bad request, 401 missing/invalid key,
  403 the key doesn't own that domain, 404 unknown resource, 429 rate limited).
- Always start by listing domains to get a `domainId`, then query the
  per-domain resources with it.
- The full, always-current machine-readable reference is
  https://meev.ai/api/public/v1/openapi.json — fetch it to discover every
  endpoint and its exact response shape. Treat it as authoritative over the
  list below.

## Core endpoints

Account & domains:
```
GET /domains                              the websites the user manages (get the id)
GET /domains/{id}                         business, voice, and positioning profile
GET /account                              plan, limits, and usage
```

Search & SEO:
```
GET /domains/{id}/rankings                organic ranking posture + top keywords
GET /domains/{id}/search-performance      clicks, impressions, and queries
GET /domains/{id}/keyword-gaps            keywords competitors rank for that you don't
GET /domains/{id}/index-coverage          which pages are indexed vs not
```

AI visibility:
```
GET /domains/{id}/ai-visibility           mentions + citations across AI search
GET /domains/{id}/ai-visibility/citations which sources AI answers cite
```

Competitors, backlinks & content:
```
GET /domains/{id}/competitors             who wins the queries you want
GET /domains/{id}/backlinks               referring domains + authority
GET /domains/{id}/content                 themes, cadence, and coverage
GET /domains/{id}/topical-authority       your topical map + gaps
```

## Example request

```
curl https://meev.ai/api/public/v1/domains/{id}/rankings \
  -H "x-api-key: $MEEV_API_KEY"
```

## Rules

- Read-only. Never claim you edited, published, or spent anything.
- Only the user's own domains resolve; a 403 means the key doesn't own that
  domain, not that you should retry.
- If a resource comes back empty, say the data isn't captured yet. Do NOT
  invent numbers.
- Answer from the JSON: cite the concrete figures (rank, delta, clicks, %),
  don't hand-wave.
- For anything not covered above, read the OpenAPI spec before guessing a path.