# Diffbot Event Extraction via Locus x402

> Diffbot Event Extraction via Locus x402 is a paid API for AI agents from diffbot.x402.paywithlocus.com, paid per call via x402, $0.0042/call, status unknown (last checked 2026-09-13).

Extracts structured data from event pages on the web, returning parsed event details via Diffbot's AI extraction engine, paid per-call with USDC.

## Facts

- Endpoint: POST https://diffbot.x402.paywithlocus.com/diffbot/event
- Price: $0.0042/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/diffbot-event-extraction-via-locus-x402-5df8e4b8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RMIvLYS6DPTQWUXpjL1GD

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 diffbot-event-extraction-via-locus-x402-5df8e4b8 -d '<json body>'
```

Example prompt: Can you extract the structured event details from this page — https://www.eventbrite.com/e/some-event-123 — and also pull in any comments or discussion threads on the page?

## When to prefer this

Choose this endpoint when you need to extract structured data specifically from event pages (conferences, meetups, community events, etc.) and want per-call micropayment billing via USDC x402 rather than a subscription. Prefer this over generic scrapers when you want Diffbot's AI-powered field extraction with automatic event schema detection. It is especially useful in agentic workflows where you want to enrich event data on demand without managing API keys or subscriptions.

## Known failure modes

- Invalid or unreachable URL returns an error or empty data object
- Timeout exceeded if the target page loads slowly and timeout parameter is too low
- Non-event pages may return empty or poorly structured data since the endpoint is tuned for events
- Payment failure if USDC authorization is insufficient
- Rate limiting or access restrictions on the target website may result in incomplete extraction

## How this service works

Locus public pay-per-use API

## Output

Returns a JSON object with a `data` field containing the structured event extraction (title, date, location, description, and any requested extra fields), a `payment` object showing USDC settled and authorized amounts, a `request` object with a UUID and status URL for tracking, and a `success` boolean.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "fields": {
   "type": "string"
  },
  "timeout": {
   "type": "number"
  },
  "discussion": {
   "type": "boolean"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "payment": {
   "scheme": "exact",
   "settledUsdc": "0.001000",
   "authorizedMaxUsdc": "0.001000"
  },
  "request": {
   "id": "00000000-0000-4000-8000-000000000000",
   "statusUrl": "/requests/00000000-0000-4000-8000-000000000000"
  },
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/diffbot-event-extraction-via-locus-x402-5df8e4b8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from diffbot.x402.paywithlocus.com](https://www.zero.xyz/host/diffbot.x402.paywithlocus.com/llms.txt)