# Saylor Innovations Data Desk – Data Breach Catalogue

> Saylor Innovations Data Desk – Data Breach Catalogue is a paid API for AI agents from saylorinnovations.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-28).

Returns recent data breaches from Have I Been Pwned, filterable by recency, with accounts affected, data exposed, passwords flag, dates, and summaries

## Facts

- Endpoint: GET https://saylorinnovations.com/api/breach/recent-breaches?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/saylor-innovations-data-desk-data-breach-catalogue-3c66d0c9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_deehKQnpR3TzRNXrn3JCE

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability saylor-innovations-data-desk-data-breach-catalogue-3c66d0c9
```

Example prompt: Pull the 15 most recent data breaches from the Have I Been Pwned catalogue — I want to see which ones exposed passwords and how many accounts were affected for each.

## When to prefer this

Choose this endpoint when you need a ready-filtered, summarized view of recent data breaches sourced from Have I Been Pwned without building your own HIBP integration — especially useful when you want recency filtering (last N days) and breach metadata (passwords flag, accounts affected, verification status) in a single call. Prefer this over direct HIBP API access when operating within an x402 micropayment agent workflow at $0.01 per call.

## Known failure modes

- Invalid 'days' parameter (non-numeric string) may return an error or be ignored
- limit out of range (>30 or <1) may default to 10 or return an error
- No breaches in the specified time window returns empty breaches array with matches: 0
- Upstream HIBP API unavailability may cause timeout or error response
- Missing required input/method fields returns a schema validation error

## How this service works

Data breach catalogue from Have I Been Pwned filterable by name or recency - accounts affected, data exposed, passwords flag, dates and a summary

## Output

A JSON object containing the number of matching breaches, an array of breach records (each with name, domain, breach date, date added to HIBP, accounts affected, data classes exposed, passwords exposed flag, verified and sensitive flags, and a summary), plus total accounts across matched breaches, the filter applied, and the data source attribution.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "days": {
       "type": "string",
       "description": "optional only breaches added in the last N days"
      },
      "limit": {
       "type": "string",
       "description": "optional 1-30, default 10"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "required": [
      "matches",
      "breaches"
     ],
     "properties": {
      "note": {
       "type": "string",
       "description": "Caveat or context for reading the result"
      },
      "filter": {
       "type": "object",
       "properties": {
        "q": {
         "description": "Name filter applied"
        },
        "days": {
         "type": [
          "number",
          "null"
         ],
         "description": "Number of days"
        }
       },
       "description": "Filter applied: name search and recency window in days"
      },
      "source": {
       "type": "string",
       "description": "Data source the values come from"
      },
      "matches": {
       "type": "number",
       "description": "Matching items"
      },
      "breaches": {
       "type": "array",
       "items": {
        "type": "object",
        "properties": {
         "id": {
          "description": "Identifier of the record"
         },
         "name": {
          "description": "Name"
         },
         "added": {
          "type": [
           "string",
           "null"
          ],
          "description": "Date added to Have I Been Pwned"
         },
         "domain": {
          "description": "Domain name"
         },
         "summary": {
          "description": "Short summary"
         },
         "accounts": {
          "type": [
           "number",
           "null"
          ],
          "description": "Accounts affected"
         },
         "verified": {
          "type": [
           "boolean",
           "null"
          ],
     
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/saylor-innovations-data-desk-data-breach-catalogue-3c66d0c9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from saylorinnovations.com](https://www.zero.xyz/host/saylorinnovations.com/llms.txt)