AttestPage
Checks a quote on its live page: exact, fuzzy or none, offsets and a signed receipt. US$0.01 per call; POST url, quote.
The wallet the 402 directs payment to. Its full payment record is on the merchant page.
Asset 0x036CbD53842c5426634e7929541eC2318f3dCF7e
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service; most of the catalog is unregistered.
Recent payments · which agents last used it
Every indexed settlement paid to this service’s wallet, newest first. The index does not record which endpoint a payment was for, so if this wallet serves more than one endpoint, the rows include payments for the others. Paged up to the newest 5,000; the full history is on the merchant page.
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xb4dd…3d310xe8f2…53e6 | Base Sepolia | $0.002 | 100% | payAI | 25d ago | 0xbc696e…b1363e |
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying: a price here is a claim, not a quote.
Pay 0.01 USDC on Base Sepolia to 0xe8F2…653E6. The signed payment is good for 2 minutes.
- Paid to
- 0xe8F2…653E6
- USD Coin (Base Sepolia) contract
- 0x036C…dCF7e
- Payment window
- 2 minutes
- As published
- 10000 smallest units
The catalog’s raw entry
[
{
"asset": "0x036CbD53842c5426634e7929541eC2318f3dCF7e",
"extra": {
"name": "USDC",
"version": "2"
},
"payTo": "0xe8F27F699b583B188446e5A92c2A489f121653E6",
"amount": "10000",
"scheme": "exact",
"network": "eip155:84532",
"maxTimeoutSeconds": 120
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"url": "https://www.iana.org/help/example-domains",
"match": "fuzzy",
"quote": "These domains may be used as illustrative examples in documents",
"case_sensitive": false
},
"type": "http",
"method": "POST",
"bodyType": "json",
"discoverable": true
},
"output": {
"type": "json",
"example": {
"page": {
"http_status": 200,
"content_kind": "real"
},
"tier": "paid",
"result": {
"end": 234,
"match": "exact",
"score": 1,
"start": 171,
"context": "...maintained for documentation purposes. These domains may be used as illustrative examples in documents without prior coordination with us...",
"occurrences": 1,
"normalised_sha256": "…"
},
"receipt": "eyJ…"
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"required": [
"url",
"quote"
],
"properties": {
"url": {
"type": "string",
"description": "http(s) URL of the page to check (max 2,048 characters). The whole request body is capped at 64 KB."
},
"match": {
"enum": [
"exact",
"fuzzy",
"passages"
],
"type": "string",
"description": "exact; fuzzy (default), which also accepts small differences; or passages, for a paraphrased claim: the 3 passages that share most of its words, scored, as evidence for you to judge (not a verdict)."
},
"quote": {
"type": "string",
"description": "Text to look for on the page, or with match \"passages\" the claim to find support for (max 1,000 characters after normalisation)."
},
"threshold": {
"type": "number",
"maximum": 1,
"minimum": 0.5,
"description": "Fuzzy similarity needed, default 0.9."
},
"case_sensitive": {
"type": "boolean",
"description": "Default false; must be false with match \"passages\"."
}
},
"additionalProperties": false
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
},
"discoverable": {
"type": "boolean",
"const": true
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object",
"required": [
"result",
"page",
"receipt"
],
"properties": {
"page": {
"type": "object",
"description": "Page verdict and evidence, including server_ip, tls and headers (the network evidence also signed into the receipt; null on an edge server)."
},
"tier": {
"type": "string"
},
"advice": {
"type": "string"
},
"result": {
"type": "object",
"description": "match, score, start, end, context, occurrences, normalised_sha256; on a none, nearest (the closest span: start, end, text, score, diff; charged like any answer); with match \"passages\" also passages [{ start, end, score, text, missing, flags }], scorer and note; on a PDF the match and each passage also give pdf_page and pdf_page_end (1-based)."
},
"receipt": {
"type": "string"
},
"injection_flags": {
"type": "array"
}
}
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-10-21 17:58Z
- Last indexed by Roundhouse
- 2026-10-27 22:45Z
- Last enriched (probe, favicon, geo)
- –
- x402 version
- 2
- Max timeout
- 120s
- Liveness probe
- Not probed
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent: it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service AttestPage and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=AttestPage' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://s2h6qt73jtzlgbgnnfacln2poq.srv.us/v1/verify/quote, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://preview.roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://preview.roundhouseai.io/skill.md first — it is the whole procedure.