API Status Check

List the APIs and developer platforms this service monitors, optionally filtered by category. Statuses come from the most recently published monitor snapshot, not a live probe, and can be up to a day old — check monitorCheckedAt, and call get_api_status when the caller needs the status right now.

{
  "type": "object",
  "properties": {
    "category": {
      "description": "Category slug to filter by, e.g. \"ai\" — omit for all categories.",
      "type": "string"
    },
    "limit": {
      "description": "Max results (default 25).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Find monitored APIs by name, slug, category or description. Use this to resolve a product name the user mentioned into the slug the other tools take.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "Free-text query, e.g. \"openai\" or \"payments\"."
    },
    "limit": {
      "description": "Max results (default 25).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Probe a monitored API endpoint at call time and return up/degraded/down with the response time. This is the tool to reach for when a user asks "is X down?" — it makes a real request rather than reading the hourly cache.

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "minLength": 1,
      "description": "API slug, e.g. \"openai\". Use search_apis to resolve a name."
    }
  },
  "required": [
    "slug"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Everything the most recent monitor run found down or degraded, across all categories. Returns an empty list when the monitor snapshot is missing or stale — an empty list is therefore not proof that everything is healthy; check monitorLastRun.

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Uptime percentages, response-time stats and recorded data points for one API over a time range. History is retained for 30 days; an API added recently will have few or no data points, which reads as null percentages rather than 100%.

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "minLength": 1,
      "description": "API slug, e.g. \"openai\"."
    },
    "range": {
      "description": "Window to return data points for (default 24h).",
      "type": "string",
      "enum": [
        "24h",
        "7d",
        "30d"
      ]
    }
  },
  "required": [
    "slug"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Real incidents a vendor published on its own status page, newest first, with start/end times, duration, severity, affected components and a link to the vendor’s incident page. Use this for "has X been flaky lately?" — it is the vendor’s own record, not our probes. Services without a public Statuspage endpoint return covered:false rather than an empty list.

{
  "type": "object",
  "properties": {
    "service": {
      "type": "string",
      "minLength": 1,
      "description": "API slug, e.g. \"openai\". Use search_apis to resolve a name."
    },
    "window": {
      "description": "Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d).",
      "type": "string",
      "enum": [
        "7d",
        "30d",
        "90d",
        "180d",
        "365d",
        "all"
      ]
    },
    "limit": {
      "description": "Max incidents (default 25).",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "required": [
    "service"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Given several service slugs, return a scorecard ranked worst-first: incident count, total downtime minutes, mean time to resolve, and the longest incident over a window. Use this to answer "which vendor in my stack is least reliable?" — it compares services across vendors, which a vendor’s own monitoring tool cannot. Services with no archive are listed separately as uncovered instead of being ranked as flawless.

{
  "type": "object",
  "properties": {
    "services": {
      "minItems": 1,
      "maxItems": 25,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      },
      "description": "API slugs to compare, e.g. [\"openai\",\"anthropic\",\"vercel\"]."
    },
    "window": {
      "description": "Time window: 7d, 30d, 90d, 180d, 365d, all (default 90d).",
      "type": "string",
      "enum": [
        "7d",
        "30d",
        "90d",
        "180d",
        "365d",
        "all"
      ]
    }
  },
  "required": [
    "services"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Category slugs and how many monitored APIs sit in each. Use the slugs with list_apis.

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}