passlisted in Coinbase#3 by calls of 9 on this host
0.1 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
- 4
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-08-21 03:55 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.1 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 33 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.
feeds sanctions screen answers POST requests at x402.payperbyte.io; it is listed in the Coinbase registry and TOLL files it under identity.
feeds sanctions screen is priced at 0.1 USDC on Base.
The request to feeds sanctions screen is a json body with the field name.
Its example response has the fields _note, answer and attestation.
feeds sanctions screen answered the sweep of 2026-09-16 with a valid 402, as at every sweep since 2026-09-11.
feeds sanctions screen shares x402.payperbyte.io with 8 other listed endpoints and is tied 3rd by calls with 1 other.
feeds sanctions screen takes 11% of the calls counted across x402.payperbyte.io.
The registry's counters give feeds sanctions screen 4 calls and 2 unique payers over 30 days.
The last call to feeds sanctions screen came 27 days before the snapshot, 2026-08-21.
Closest in price to feeds sanctions screen within identity: eu company check at data.greeneris.io and pay tier3 at api.truthbear.co.
feeds sanctions screen is priced above 86% of comparable listings in identity.
Within identity, 77% of endpoints with counters have fewer calls.
The wallet paid by feeds sanctions screen is the payee of 10 endpoints on one host.
The seller's tags on feeds sanctions screen are payperbyte, sanctions-screen, ofac and compliance.
Exactly this price appears on 44 other listings in identity.
the payment options, as of 2026-09-16 21:17 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.1 USDC | exact | 0xffFf4B…AFE0DB |
the checks, as of 2026-09-16 06:25 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-16 06:25 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 06:41 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:10 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:01 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:19 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 13:17 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-21 03:55 UTC · method · live
The input and output block
{
"input": {
"body": {
"name": "Lazarus Group"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"_note": "Excerpt of a real answer (live service, 2026-07-01); hash/signature elided, signals/consolidated trimmed. Every answer pins the exact OFAC list version (published date + sha256 + entry count) it was judged against. Screening signal, not legal advice. The EIP-712 receipt — domain chainId 421614 = Arbitrum Sepolia, a frozen signing namespace, not a settlement rail — proves who signed these exact bytes (authenticity + tamper-evidence), not that the screening result is correct. Recompute keccak256(canonical answer bytes) and recover the signer before acting.",
"answer": {
"v": "sanctions-screen/v1",
"query": {
"name": "Lazarus Group",
"chain": null,
"address": null
},
"score": 0,
"reasons": [
"name exactly matches OFAC SDN primary name \"LAZARUS GROUP\": entry #27307 \"LAZARUS GROUP\" [DPRK3] — list published 2026-06-30"
],
"verdict": "BLOCK",
"list_state": {
"sdn": {
"stale": false,
"source": "OFAC SDN (Specially Designated Nationals and Blocked Persons)",
"entry_count": 19129,
"content_sha256": "a04efa5d60104ebd35fc08b6891811120d151bf37801fbd3c01e64380198f099",
"published_date": "2026-06-30"
}
},
"methodology": "ss-v1"
},
"attestation": {
"domain": {
"name": "BYTE Library",
"chainId": 421614,
"version": "1",
"verifyingContract": "0x44729bB148F46d8Db509E47b0453edc271e06e95"
},
"signer": "0x344ECaCDe6566294c31397445c98b62a3EEEA456",
"signature": "0x…",
"payloadHash": "0x…"
}
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-16 21:17 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "feeds sanctions screen on x402.payperbyte.io", snapshot of 2026-09-16 21:17 UTC. https://tollindex.com/e/x402-payperbyte-io-feeds-sanctions-screen-d85f43/at/2026-09-16T21-17Z. Accessed [access date].
BibTeX
@misc{toll-e-x402-payperbyte-io-feeds-sanctions-screen-d85f43-2026-09-16T21-17Z,
author = {TOLL},
title = {feeds sanctions screen on x402.payperbyte.io},
howpublished = {\url{https://tollindex.com/e/x402-payperbyte-io-feeds-sanctions-screen-d85f43/at/2026-09-16T21-17Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-16 21:17 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.