Sato Hub
Answer

Which x402 endpoints actually work?

10 of the 12 paid x402 endpoints Sato Hub reached answered HTTP 402 with valid payment terms in the last 7 days. Nothing was paid, so delivery is not measured, as of 2026-10-22.

  • Answered from live data2026-10-22

Also asked as Which x402 endpoints answer a payment request?

The paid x402 endpoints that answered, named as /x402/verified names them. A paid endpoint is a URL a project names as paid in its own /.well-known/x402 manifest, which is where an HTTP 402 is expected. Answering means an unpaid request got status 402 and a payment payload a client could parse in the last 7 days. Nothing is paid, so what paying returns is not measured, and a reply is not a statement that the service works once paid. A URL that gave no answer is unknown, not failed, and is not named here. Across all 130 URLs that declare x402, most of them listing pages where no 402 is expected, 10 answered.

Endpoint hostNetwork (declared)Asset · schemeFacilitator answers /supportedLast checked
blockrun.aieip155:84530x833589…2913 · exactnot read2026-10-22
dripstack.xyzeip155:84530x833589…2913 · exactnot read2026-10-22
emblemvault.aieip155:84530x833589…2913 · exactnot read2026-10-22
laso.financeeip155:84530x833589…2913 · exactnot read2026-10-22
minia2a.ukeip155:84530x833589…2913 · exactnot read2026-10-22
nanoparse.appeip155:84530x833589…2913 · exactnot read2026-10-22
satohub.aieip155:84530x833589…2913 · exactnot read2026-10-22
skim402.comeip155:84530x833589…2913 · exactnot read2026-10-22
x402-bazaar-rank.x402-bazaar-rank-worker.workers.deveip155:84530x833589…2913 · exactnot read2026-10-22
x402-ping.palmbeachpete.workers.deveip155:84530x833589…2913 · exactnot read2026-10-22
How this was answeredShowHide

The x402 verification lane's own folds, handed in by loadAnswerContext() in lib/answerContext.ts over the latest banked probe (venue x402_verify): x402FunnelFrom() in lib/numbers/x402Endpoints.ts for the counts, isVerified() in lib/x402VerifiedView.ts for which endpoints stand, x402WorkingLadder() in lib/pageAnswers.ts for the stages. One unpaid GET per declared URL, 10 s deadline, no payment sent. The figure and its date are those of /x402/verified and /numbers/x402-endpoints-that-answer, not a second reading. The paid resources that answered are the ones named, as /x402/verified names them; "work" here means a reply with valid payment terms on the date shown.

Every answer on this page is produced by one named function over Sato Hub's live records on the date shown. Nothing is typed by hand, no figure is carried over from a previous day, and an answer with nothing behind it says unknown rather than zero. The Sato Score measures how open, active and verifiable a project is — it is not a safety, quality or returns grade.

Go deeper

x402 verified: every declared endpoint and what it answered →How many x402 payment endpoints answer a payment request →Which platforms and facilitators support x402 →x402 on Sato Hub: endpoints, facilitators and sellers →Which x402 endpoints answered a paid request recently? →How can an AI agent pay another agent? →

More questions

Reference

QuestionsShowHide
SourcesShowHide

Sources — the projects' own repositories and docs

Cite this pageShowHide

Cite this page

Sato Hub. "Which x402 endpoints actually work?." Sato Hub, updated 2026-10-22, accessed 2026-10-22. https://satohub.ai/answers/which-x402-endpoints-actually-work

Data last refreshed 2026-10-22; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0 and the machine-readable copy is linked in the page's Dataset metadata.