passabsent from every registry#3 by calls of 2 on this host
0.01 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-09-24 17:09 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-08-25 18:37 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 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 63 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.
x402.payperbyte.io serves feeds cctp attestation latency, a POST endpoint that TOLL places in identity, listed in neither registry at the last pull.
A call to feeds cctp attestation latency costs 0.01 USDC on Base, as declared.
feeds cctp attestation latency takes a json body with the fields path and chain.
A response from feeds cctp attestation latency, as declared, includes _note, answer and attestation.
The daily sweep got a valid payment challenge from feeds cctp attestation latency on 2026-09-23, as at every sweep since 2026-09-11.
feeds cctp attestation latency is one of 2 listed endpoints on x402.payperbyte.io, 3rd by calls among them.
feeds cctp attestation latency takes 6% of the calls counted across x402.payperbyte.io.
In the trailing 30 days: one call, one payer.
feeds cctp attestation latency was last called 49 days before the snapshot.
Closest in price to feeds cctp attestation latency within identity: verify job at livecheck.fly.dev and screening match at api.relaystation.ai.
Among comparable prices in identity, feeds cctp attestation latency sits above 34% of them.
Its payee wallet receives for 10 listed endpoints on one host.
The seller's tags on feeds cctp attestation latency are payperbyte, cctp, attestation-latency and circle.
feeds cctp attestation latency was missing from the Coinbase registry at the pull of 2026-09-24, confirmed at the pull of 2026-09-25; that is registry presence, not liveness.
The price of feeds cctp attestation latency is declared by 707 other listings in identity too.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-09-24 17:09 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0xffFf4B…AFE0DB |
the checks, as of 2026-09-23 06:11 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-23 06:11 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 06:21 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 06:44 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-20 19:22 UTC | pass | 0 | daily-2026-09-20 |
| 2026-09-19 04:45 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 10:39 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 04:41 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 04:41 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 04:39 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:35 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:33 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:49 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 10:23 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-08-25 18:37 UTC · method
The input and output block
{
"input": {
"body": {
"path": "fast",
"chain": "base"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"_note": "Excerpt of a real answer (live service, 2026-08-25, post FD HIGH-2 clamp fix); hash/signature elided, other buckets trimmed. Every figure is a BOUNDED observation (burn -> first poll seeing complete), never an exact measurement — min_s is floored at 0 (a bounded observation cannot precede the burn it bounds; an earlier example briefly shipped an unclamped negative value from L2-clock-skew artifacts, fixed 2026-08-25). Percentiles are withheld below an 8-measured-sample floor. Fast and Standard are separate settlement paths and are never blended into one percentile. The embedded EIP-712 receipt (domain chainId 421614 = Arbitrum Sepolia, a frozen signing namespace, not a settlement rail) proves who signed these exact bytes — not that the measured latency will hold for your own transfer.",
"answer": {
"query": {
"path": "fast",
"chain": "base"
},
"ruleset": "cctp-lat-v1",
"coverage": {
"status": "observed"
},
"distributions": {
"base/fast": {
"max_s": 7999,
"min_s": 0,
"p50_s": 1753,
"p95_s": 7265,
"p99_s": 7583,
"samples": 27753,
"measured_samples": 37,
"percentiles_reported": true,
"percentiles_withheld_because": null
}
},
"observation_count": 27753
},
"attestation": {
"domain": {
"name": "BYTE Library",
"chainId": 421614,
"version": "1"
},
"signer": "0x…",
"signature": "0x…",
"payloadHash": "0x…"
}
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "feeds cctp attestation latency on x402.payperbyte.io". https://tollindex.com/e/x402-payperbyte-io-feeds-cctp-attestation-latency-49cdba. Accessed [access date].
BibTeX
@misc{toll-e-x402-payperbyte-io-feeds-cctp-attestation-latency-49cdba-2026-10-13,
author = {TOLL},
title = {feeds cctp attestation latency on x402.payperbyte.io},
howpublished = {\url{https://tollindex.com/e/x402-payperbyte-io-feeds-cctp-attestation-latency-49cdba}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.