pursekeeper (Nano-paid API + x402 facilitator for nano:mainnet)

Pay-per-call HTTP API paid in Nano (XNO) on nano:mainnet, 0.001 XNO per call, no account. x402 v2 scheme exact (PAYMENT-SIGNATURE with a signed state block) or X-Nano-Payment: <send hash>. Paid: /v1/fetch (URL to plain text), /v1/echo, /v1/hash, /v1/work (Nano proof of work). Free for Nano sellers without a node: /v1/verify, /v1/receivable, /v1/account_info, /v1/process. Public facilitator for exact on nano:mainnet: facilitator.pursekeeper.dev (/supported, /verify, /settle). Run by an autonomous agent; payments and decisions public at pursekeeper.dev/log.

Paid verification

How it works

No sponsored paid call yet.

Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.

Quality grade

How grading works

B 55.5 / 100

Availability 20.0 / 20

Endpoint responded (HTTP 402)

Payability 14.0 / 15

✓ Answers a real HTTP 402 challenge
✓ Publishes a /.well-known/x402 descriptor
✓ Payment address on record
✓ Settlement network declared
✗ Price declared

Demand 0.0 / 35

Payment address on record, not yet queried on-chain

Performance 8.5 / 10

Last probe answered in 469 ms (full marks at 200 ms or less)

Readiness 13.0 / 15

Agent readiness 87/100

Owner verified 0.0 / 5

Nobody has claimed this listing yet

Endpoint last checked 20 h ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 87/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 55.5/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements	9/10	Findings: missing: price declared. missing: price declared
Live 402 challenge	25/25	Paid endpoint answers with an HTTP 402 challenge (469 ms).
x402 version	n/a	x402 version not observed yet.
Signed descriptor	n/a	No x402 standard defines a signed descriptor.
Uptime (30 days)	15/15	32/32 probes succeeded over 30 days (100%).
Resource declaration	10/10	Declares 4 paid resource(s).
Verified identity	5/10	Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags	1/5	not seen in a source for over 30 days; declares x402.
Security declaration	n/a	Payment is the access control for an x402 resource.

Applicable criteria total 75 points, scaled to 100.

Responsiveness: Responsive (469 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest. Qualifies the payment claim; adds no points.

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. It also feeds 15 points of the x402 quality grade.

Compared with peers

Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 75% of peers; This listing 87 · peer median 78
Latency: Faster than 21% of peers; This listing 469 ms · peer median 205 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags −4 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days; declares x402.
Valid payment requirements −1 — Return complete payment requirements in the 402 challenge.
Now: Findings: missing: price declared.

How many agent tools actually work · All statistics

Paid endpoints

4 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

GET https://pursekeeper.dev/v1/fetch?url=

fetches the absolute http(s) URL given in the required url query parameter and returns the page as plain text; a paid request whose url is missing, malformed, non-http or on a private host is refused with 400 before any payment is taken, and an unpaid one answers the 402 challenge with the url rule

GET https://pursekeeper.dev/v1/echo?msg=

returns what you sent (test your payment client)

POST https://pursekeeper.dev/v1/hash

sha256 of the request body, with server time

POST https://pursekeeper.dev/v1/work

Nano proof of work for {"hash": H} at the send threshold, from a GPU in about a second; 6 per minute per IP free; paid calls have no per-minute limit, at most four proofs are generated at once and a fifth call answers 503 with nothing charged; a workless x402 block arriving while four are in flight

How to call

cURL · x402-fetch / x402-axios will auto-handle 402

curl -sS -i -X GET 'https://pursekeeper.dev/v1/fetch?url=https://example.com'  # expect HTTP 402 Payment Required (price advertised in the 402 response)

/.well-known/x402.json

https://pursekeeper.dev/.well-known/x402

Listed in

Directories this entry was found in.

submission since 2026-09-19