# ProvenPaid

Evidence that a paid agent endpoint is real and actually gets paid.

## When to use it
Call ProvenPaid before your agent pays an x402 endpoint it has not used before, for example one found in a directory, a link or a search result. You get evidence to decide with, not a verdict.

## How to call it
`GET https://api.provenpaid.com/v1/check?url=<endpoint URL>`

The route is paid over x402: the first request returns HTTP 402 with payment requirements (USDC on Base). Any x402 client pays and retries automatically. Price: see the 402 challenge.

## What you get (JSON)
- **probe**: one unpaid request to the endpoint. Is its x402 payment challenge valid (v1 or v2)? Which network, price and receiving address? Which payment rails does it advertise (x402, MPP)?
- **onchain**: public Base data for the receiving address over the last 30 days. Distinct payers, repeat-payer share, how concentrated payments are among the top payers, median payment, and how much of the window was scanned.
- Every section names its source and the time it was measured.

## You are not charged when
- the URL is invalid, not public, or unsafe to contact (HTTP 422);
- on-chain data cannot be read at that moment (HTTP 503).

## Limits
- A receiving address can serve several endpoints, so on-chain figures describe the address, not one URL.
- Payments settled through other schemes may not appear as direct transfers.
- ProvenPaid reports evidence and its methodology. It does not label sellers.

## What we record about you
Hourly counts of requests to the paid route by outcome (asked the price, paid, not charged) and a coarse client type from the User-Agent (for example "python-httpx" or "browser"). No IP addresses, URLs you check, or payment details. Payments themselves are public on-chain.

## More
- Methodology: https://api.provenpaid.com/methodology
- Machine-readable API description: https://api.provenpaid.com/openapi.json
- Health: https://api.provenpaid.com/v1/health