passlisted in Coinbase#3 by calls of 31 on this host
0.01 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
- 12
- Unique payers, trailing 30 days
- 3
- Last called
- 2026-09-06 06:23 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 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.
Among the 31 endpoints on lionx402.com, entity sanctions screen json is 3rd by calls.
The request to entity sanctions screen json is the query parameter name.
Its example response has the fields verdict, asset_id, resolved and sanctioned.
entity sanctions screen json drew 12 calls from 3 unique payers in the trailing 30 days, about 4 calls per payer.
entity sanctions screen json was last called 10 days before the snapshot.
The declared price is 0.01 USDC on Base.
entity sanctions screen json takes 7% of the calls counted across lionx402.com.
TOLL files entity sanctions screen json under identity: a GET endpoint on lionx402.com, listed in the Coinbase registry.
entity sanctions screen json answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to entity sanctions screen json within identity: screening match at api.relaystation.ai and services reputation lookup at api.craigmbrown.com.
entity sanctions screen json is priced above 31% of comparable listings in identity.
Across identity, 1,501 endpoints carry counters and entity sanctions screen json out-counts 95% of them.
The payee wallet is shared by 34 listings across 3 hosts.
The seller's tags on entity sanctions screen json are sanctions, ofac, eu and un.
The price of entity sanctions screen json is declared by 516 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.01 USDC | exact | 0x68e3E7…3c85B5 |
the checks, as of 2026-09-15 05:27 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:27 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-09-06 06:23 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"name": "Bank Melli Iran"
}
},
"output": {
"type": "json",
"example": {
"verdict": "BLOCK",
"asset_id": "LION_ENTITY_SANCTIONS_001",
"resolved": true,
"sanctioned": true
}
}
}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, "entity sanctions screen json on lionx402.com", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/lionx402-com-api-x402-entity-sanctions-screen-json-6f4c53/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-lionx402-com-api-x402-entity-sanctions-screen-json-6f4c53-2026-09-15T21-20Z,
author = {TOLL},
title = {entity sanctions screen json on lionx402.com},
howpublished = {\url{https://tollindex.com/e/lionx402-com-api-x402-entity-sanctions-screen-json-6f4c53/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.