Screen
by AgentReader in Search & web
OFAC sanctions screening: fuzzy-match a person/entity/vessel name (transliteration-aware - Arabic and Slavic romanization variants) or look up a crypto address against the official OFAC SDN and Consolidated lists. Returns verdict (match/possible_match/clear), scored matches with programs and aliases, and full list-version provenance. Lists re-ingested every 6 hours.
https://agentreader.dev/screen- Price
- $0.05
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 675 ms
- 1.2 s slowest 5%
- Last check
- Passed
- 1 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://agentreader.dev/screen
Each call costs $0.05 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://agentreader.dev/screen?name=Usama+bin+LadinParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | No | Crypto address to screen against OFAC-listed digital currency addresses |
name | string | No | Person, entity or vessel name to screen (one of name/address required) |
type | string | No | Filter matches: individual | entity | vessel | aircraft | all (default all) |
Example response
The provider's example. We can't check it without paying.
Example response, 32 lines
{
"matches": [
{
"list": "OFAC-SDN",
"matchedName": "BIN LADIN, Usama",
"matchedNameKind": "primary",
"name": "BIN LADIN, Usama",
"programs": [
"SDGT"
],
"score": 1,
"type": "individual",
"uid": 6365
}
],
"provenance": {
"entryCount": 17203,
"ingestedAt": "2026-08-10T02:00:00.000Z",
"listPublished": "Fri, 07 Aug 2026 18:36:51 GMT",
"lists": [
"OFAC-SDN",
"OFAC-CONS"
],
"matcher": "agentreader-screen/1.0"
},
"query": {
"name": "Usama bin Ladin",
"normalized": "usama bin ladin",
"type": "all"
},
"verdict": "match"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.05.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://agentreader.dev/screen?name=Usama+bin+Ladin'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://agentreader.dev/screen?name=Usama+bin+Ladin' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fagentreader.dev%2Fscreen
const res = await pay("https://agentreader.dev/screen?name=Usama+bin+Ladin");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://agentreader.dev/screen?name=Usama+bin+Ladin")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 1 h ago | Passed | 402 | 493 ms | $0.05 |
| 6 h ago | Passed | 402 | 769 ms | $0.05 |
| 11 h ago | Passed | 402 | 1.2 s | $0.05 |
| 16 h ago | Passed | 402 | 634 ms | $0.05 |
| 20 h ago | Passed | 402 | 1.2 s | $0.05 |
Show 10 older checks
| 25 h ago | Passed | 402 | 972 ms | $0.05 |
| 29 h ago | Passed | 402 | 954 ms | $0.05 |
| 33 h ago | Passed | 402 | 710 ms | $0.05 |
| 37 h ago | Passed | 402 | 693 ms | $0.05 |
| 42 h ago | Passed | 402 | 1.0 s | $0.05 |
| 46 h ago | Passed | 402 | 559 ms | $0.05 |
| 2 days ago | Passed | 402 | 642 ms | $0.05 |
| 2 days ago | Passed | 402 | 675 ms | $0.05 |
| 2 days ago | Passed | 402 | 542 ms | $0.05 |
| 3 days ago | Passed | 402 | 733 ms | $0.05 |