passlisted in Coinbase#2 by calls of 10 on this host
0.02 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-08-25 15:50 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.02 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 28 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.
rfc validate, a POST endpoint on api.resetparatodos.com, appears in the Coinbase registry; TOLL's taxonomy puts it in identity.
On Base, rfc validate asks 0.02 USDC per call.
The request to rfc validate is a json body with the field rfc.
A response from rfc validate, as declared, includes ok, result and evidence.
rfc validate answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
rfc validate shares api.resetparatodos.com with 9 other listed endpoints and is tied 2nd by calls with 8 others.
rfc validate takes 9% of the calls counted across api.resetparatodos.com.
In the trailing 30 days: one call, one payer.
rfc validate was last called 21 days before the snapshot.
Closest in price to rfc validate within identity: contract at oracle.cyberwarex.com and catalysts upcoming at api.biotechcatalystsentinel.com.
rfc validate is priced above 67% of comparable listings in identity.
The wallet paid by rfc validate is the payee of 10 endpoints on one host.
The seller's tags on rfc validate are mexico, verification, deterministic and tax.
The price of rfc validate is declared by 115 other listings in identity too.
the payment options, as of 2026-09-15 16:57 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.02 USDC | exact | 0x54beA1…E8C22f |
the checks, as of 2026-09-15 05:28 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 05:28 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:01 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:58 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:14 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 10:54 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-08-25 15:50 UTC · method · live
The input and output block
{
"input": {
"body": {
"rfc": "GODE561231GR8"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"ok": true,
"result": {
"valid": true
},
"evidence": {
"person_type": "fisica",
"checksum_valid": true
}
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 16:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "rfc validate on api.resetparatodos.com", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/api-resetparatodos-com-x402-v1-rfc-validate-6f6a2c/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-e-api-resetparatodos-com-x402-v1-rfc-validate-6f6a2c-2026-09-15T16-57Z,
author = {TOLL},
title = {rfc validate on api.resetparatodos.com},
howpublished = {\url{https://tollindex.com/e/api-resetparatodos-com-x402-v1-rfc-validate-6f6a2c/at/2026-09-15T16-57Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 16:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.