# Bridge Exploit History & Leaderboard

> Bridge Exploit History & Leaderboard is a paid API for AI agents from api.agentstools.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns the hack history for a named cross-chain bridge (incidents, USD lost, funds recovered, attack techniques) or a ranked leaderboard of all bridge exploits by USD lost when no bridge is specified.

## Facts

- Endpoint: GET https://api.agentstools.dev/bridge/exploits
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bridge-exploit-history-leaderboard-386861cb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d_fJ23qsEqrocnANcAiFr

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 bridge-exploit-history-leaderboard-386861cb
```

Example prompt: Pull up the full hack history for the Wormhole bridge — I want to see every exploit incident, total USD lost, whether any funds were recovered, and what attack techniques were used.

## When to prefer this

Use this endpoint when you need DeFi bridge-specific exploit data: hack track records, USD loss totals, recovery rates, or attack method breakdowns. Prefer over generic crypto news searches when you need structured, normalized, comparable data across multiple bridge incidents sourced from DefiLlama.

## Known failure modes

- Bridge name not recognized — returns empty or error if the slug/alias cannot be resolved to a covered bridge
- No hacks on record for the specified bridge — returns empty incidents list
- DefiLlama source data unavailable — upstream data fetch may fail
- Invalid query parameter format — unrecognized parameter key ignored

## How this service works

Bridge exploit track record: for one bridge, its hack history (incidents, total USD lost, funds returned, worst technique); with no bridge, a ranked leaderboard of every bridge hack by USD lost. Sourced from DefiLlama's hack dataset, joined and normalized by us.

## Output

For a named bridge: a structured record of all hack incidents including dates, USD amounts lost, funds returned, and exploit techniques. With no bridge parameter: a ranked leaderboard of every bridge hack across all covered bridges sorted by USD lost, enabling cross-bridge security comparison.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [],
     "properties": {
      "bridge": {
       "type": "string",
       "description": "Bridge name, slug or alias (e.g. Stargate, Across, Wormhole, Arbitrum, CCTP). Resolved case-insensitively to the covered set."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bridge-exploit-history-leaderboard-386861cb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agentstools.dev](https://www.zero.xyz/host/api.agentstools.dev/llms.txt)