# x402 Delivery Map Dataset

> x402 Delivery Map Dataset is a paid API for AI agents from x402-delivery-map.owenlvll.workers.dev, paid per call via x402, $29/call, status unknown (last checked 2026-09-15).

Returns a CSV dataset of 464 x402 endpoints showing advertised vs. actual prices, payment outcomes, HTTP status codes, response sizes, latencies, content samples, and settlement transaction hashes from a single measurement run on Base.

## Facts

- Endpoint: GET https://x402-delivery-map.owenlvll.workers.dev/data.csv
- Price: $29/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-delivery-map-dataset-b74964ae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nHPu6GHPoWdEisvGKHMlk

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 x402-delivery-map-dataset-b74964ae
```

Example prompt: Can you grab the x402 delivery map dataset — the one with all 464 measured endpoints showing what they actually returned when paid, including settlement status and transaction hashes?

## When to prefer this

Use this endpoint when you need empirical, payment-verified ground-truth data about what x402 endpoints actually return — including price discrepancies, non-delivering endpoints, and on-chain settlement hashes — rather than relying solely on catalog metadata or self-reported descriptions. Prefer this over manually probing x402 endpoints when you need bulk coverage of 464 endpoints in a single structured CSV.

## Known failure modes

- Payment not accepted or underpaid — endpoint requires $29 USDC via x402 before CSV is served
- Dataset may be stale — measurements are from a single point-in-time snapshot (2026-09-06) and do not update
- CSV parsing errors if consumer does not handle quoted fields with embedded commas in response samples
- Network timeout if the Cloudflare Worker is unavailable or rate-limited

## How this service works

Complete x402 endpoint delivery dataset, 464 rows, 22 columns. For each endpoint: the price the catalog advertises, the price its own 402 response demanded, the wallet paid, whether payment settled, the HTTP status returned after paying, response size, content type, latency, a verbatim 600-character sample of what came back, and the settlement transaction hash. Measured 2026-09-06T20:05Z to 2026-09-06T20:28Z on Base. Observations only, no analysis. CSV.

## Output

A downloadable CSV file with 464 rows and 22 columns. Each row represents one measured x402 endpoint and includes: the catalog-advertised price, the price demanded in the 402 response, the wallet that paid, whether payment settled, the HTTP status returned post-payment, response size in bytes, content type, latency in milliseconds, a verbatim 600-character sample of the response body, and the on-chain settlement transaction hash on Base. All measurements were taken between 2026-09-06T20:05Z and 2026-09-06T20:28Z.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-delivery-map-dataset-b74964ae/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-delivery-map.owenlvll.workers.dev](https://www.zero.xyz/host/x402-delivery-map.owenlvll.workers.dev/llms.txt)