Back to Browse
three.ws DeFi Hack Check API
x402
three.ws DeFi Hack Check API is a paid API for AI agents from three.ws, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-11).
Returns a feed of recent DeFi/crypto protocol hack incidents with stats on stolen funds, filterable by protocol name
Price / call$0.002
Success—
StatusUnknown
How this service works
Make a 3D AI agent from a selfie in 60 seconds. Drop one HTML tag to embed it on any website. Agents think on IBM watsonx.ai (Granite); optionally charge per chat with built-in micropayments.
Output
A JSON object containing: a list of hack incidents (date, protocol name, whether a bridge was involved, chains affected, attack technique, USD amount stolen, amount returned, classification, source URL); aggregate stats for the past 12 months (incident count, total stolen, bridge hack share percentage, all-time total stolen); match count; and a verdict field indicating whether results are protocol-specific or market-wide.
Example use cases
Protocol due diligence before investing
“Before I put money into this new DeFi protocol, can you check if it or anything called 'Euler' has ever been hacked and how much was lost?”
Market-wide DeFi exploit summary
“Give me a summary of the biggest DeFi hacks over the last 12 months — show me up to 20 incidents, newest first, across all protocols.”
Bridge hack risk assessment
“What share of recent crypto exploits targeted bridges specifically? Pull the latest market-wide hack stats for me.”
Technical details
Endpoint
GEThttps://three.ws/api/x402/hack-check?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need structured, queryable data on DeFi hack incidents with financial statistics — especially useful for protocol risk assessment, security audits, investment due diligence, or monitoring the DeFi exploit landscape. Prefer it over general web search when you need machine-readable incident records with USD amounts, techniques, and chain details rather than news articles.
Side effects
- No incidents found for a queried protocol name returns empty matches array
- limit parameter out of range (must be 1-50) returns validation error
- Payment not included or insufficient USDC triggers 402 Payment Required
- Protocol name substring match may return false positives for short or common terms
- Stale data if incident database has not been recently updated
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object |
Output
Schema · Response
{
"type": "json",
"example": {
"ts": "2026-07-11T10:00:00Z",
"query": null,
"stats": {
"incidents_12mo": 61,
"total_stolen_12mo": 890000000,
"bridge_hack_share_pct": 34.2,
"total_stolen_all_time": 12100000000
},
"matches": 5,
"verdict": "market-wide",
"incidents": [
{
"date": "2026-06-28T00:00:00.000Z",
"name": "Example Protocol",
"bridge": false,
"chains": [
"Ethereum"
],
"source": "https://example.com/post-mortem",
"technique": "Price oracle manipulation",
"amount_usd": 12000000,
"returned_usd": null,
"classification": "DeFi"
}
],
"total_lost_usd": 412000000
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"