# x402 Payment Requirements Probe

> x402 Payment Requirements Probe is a paid API for AI agents from well-012-x402-probe.rainmaker-wells.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-27).

Probes a public HTTPS URL to detect x402 payment requirements without paying, returning status, latency, parsed payment details, and network/price info.

## Facts

- Endpoint: POST https://well-012-x402-probe.rainmaker-wells.workers.dev/api/x402-probe?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-27
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-payment-requirements-probe-c5f77a55
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Pb9qogp2TEsSUOmUISAip

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-payment-requirements-probe-c5f77a55 -d '<json body>'
```

Example prompt: Can you probe https://api.example.com/premium-data to see if it requires x402 payment — I want to know the minimum price, which networks are supported, and whether the payment-requirements header is valid, without actually paying anything?

## When to prefer this

Use this endpoint when you need to inspect whether a URL enforces x402 payment requirements before committing any funds, or when you want to programmatically discover pricing and network details of an x402-gated resource. Prefer this over manually inspecting HTTP headers when you need structured, parsed output including minimum price, network list, and schema validity in a single call.

## Known failure modes

- Non-HTTPS URLs (http, file, data, localhost, private IPs) are rejected immediately
- Requests exceeding ~12 seconds timeout are aborted
- Responses larger than ~200KB are truncated or rejected
- More than 5 redirects causes the probe to fail
- If the target URL is unreachable, returns connection error details
- Malformed x402 headers may result in parse errors reflected in the response

## How this service works

Unpaid probe of a public https URL for x402 payment requirements ($0.005 USDC). Never pays. Returns HTTP status, latency, whether 402/payment-requirements parse, networks, min price, schema flag. https only; caps ~12s, 200KB, 5 redirects. Factual only; as is, no guarantee. Not a rating or certification. Provided as is, with no warranty or guarantee of accuracy or fitness. Nothing is stored.

## Output

Returns an object containing the HTTP status code of the probed URL, measured latency, a boolean indicating whether a 402 response was detected, parsed payment-requirements details (if present), supported blockchain networks, minimum price, and a flag indicating schema validity — all without making any payment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "https URL of an x402 resource or MCP origin to probe unpaid. http/file/data/localhost/private IPs rejected."
  },
  "method": {
   "type": "string",
   "description": "Optional HTTP method: GET (default) or POST (empty JSON body)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-payment-requirements-probe-c5f77a55/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from well-012-x402-probe.rainmaker-wells.workers.dev](https://www.zero.xyz/host/well-012-x402-probe.rainmaker-wells.workers.dev/llms.txt)