passlisted in Coinbase#3 by calls of 5 on this host
0.25 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-10 16:18 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.25 USDC
- Networks
- 3
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 29 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
verify claim, a POST endpoint on 402oracle.com, appears in the Coinbase registry; TOLL's taxonomy puts it in identity.
Per call, verify claim declares 0.25 USDC on Base.
Requests carry a json body with the field claim.
verify claim accepts payment on Base, Polygon and Arbitrum, 3 options in all, all to one wallet.
A response from verify claim, as declared, includes signature and attestation.
The daily sweep got a valid payment challenge from verify claim on 2026-09-15, as at every sweep since 2026-09-11.
Of 402oracle.com's 5 listings, verify claim ranks tied 3rd by calls with 2 others.
It accounts for 13% of the calls counted across the host.
verify claim drew a single call from a single payer in the trailing 30 days.
The last call to verify claim came 5 days before the snapshot, 2026-09-10.
Closest in price to verify claim within identity: gauge agri region at api.truthbear.co and sanctions check at api.strale.io.
verify claim is near the top of prices in identity; 92% of comparable listings are cheaper.
The wallet paid by verify claim is the payee of 5 endpoints on one host.
Seller tags: verification, fact-check, claim-adjudication and hallucination-guard.
The price of verify claim is declared by 37 other listings in identity too.
the payment options, as of 2026-09-15 21:20 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.25 USDC | exact | 0x7a19cd…9b6f4a |
| Coinbase | eip155: | USDC | 0.25 USDC | exact | 0x7a19cd…9b6f4a |
| Coinbase | eip155: | USDC | 0.25 USDC | exact | 0x7a19cd…9b6f4a |
the checks, as of 2026-09-15 06:55 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 06:55 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:22 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:12 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:42 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 14:39 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-10 16:18 UTC · method · live
The input and output block
{
"input": {
"body": {
"claim": "Company X was founded in 2019."
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"signature": {
"alg": "ES256",
"jwks": "/.well-known/jwks.json"
},
"attestation": {
"type": "claim_verification",
"result": {
"verdict": "supported",
"citations": [
"https://example.com/about"
]
},
"subject": {
"claim": "Company X was founded in 2019."
},
"confidence": 0.8
}
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 21:20 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "verify claim on 402oracle.com", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/402oracle-com-verify-claim-eb5fb0/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-402oracle-com-verify-claim-eb5fb0-2026-09-15T21-20Z,
author = {TOLL},
title = {verify claim on 402oracle.com},
howpublished = {\url{https://tollindex.com/e/402oracle-com-verify-claim-eb5fb0/at/2026-09-15T21-20Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 21:20 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.