Visibility

List alerts

What the latest run flagged: prompts losing across several engines, engines that won nothing, and site-audit problems.

GEThttps://api.vidrys.com/v1/projects/{project_id}/alerts

Plan: Grow and above
Key: read
Rate cost: 1 unit
MCP tool: list_alerts

List alerts

curl --request GET \
  --url "https://api.vidrys.com/v1/projects/{project_id}/alerts" \
  --header "Authorization: Bearer $VIDRYS_API_KEY"

200 · success

{
  "alerts": [
    {
      "message": "3 platforms not recommending you for 'best invoicing software for freelancers in India'",
      "tone": "warning",
      "platform": "chatgpt"
    },
    {
      "message": "Win rate dropped to 0% — content needs attention",
      "tone": "warning",
      "platform": "gemini"
    },
    {
      "message": "AEO: AI crawlers blocked in robots.txt",
      "tone": "warning",
      "platform": null
    }
  ]
}

Authorization

Sent as a header on every request.

Authorizationstringrequired

A Vidrys API key, sent as Bearer vidrys_sk_…. A read key is enough. See Authentication.

Path parameters

project_idstringrequired

The project's id, from List projects.

Response · 200

application/json

alertsobject[]

Newest run's alerts, at most 8.

+Show child attributes

messagestring

The alert, as the dashboard shows it.

tonestringnullable

Severity.

Values:warning

platformstringnullable

The engine it concerns. Null for site-audit alerts.

Values:chatgptperplexitygeminicopilotai_overviewsclaude

Errors

404 not_found	The project or item doesn't exist in this workspace. A project from another workspace also returns 404, never 403.
401 unauthorized	No key was sent, or the key is unknown, revoked or expired, or the member who created it has left the workspace or been deactivated.
402 plan_required	The workspace's plan doesn't include API access. It's included on Grow, Scale and Custom.
403 workspace_not_approved	The workspace is still waiting for approval, or wasn't approved.
429 rate_limited	Too many requests this minute. Wait for the number of seconds in the `Retry-After` header, then retry.

Every code, and what to retry, is in Errors.