api.invoket.com
No description published for this endpoint.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"error": "PAYMENT-SIGNATURE header is required. Free trial on request: send the header `X-402-Trial: 1` on this call and on the signed retry to have a free-trial option added to accepts[].",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x4465825B0ac713aA2Fa07Ea29023020804A128ee",
"amount": "10000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
],
"resource": {
"url": "https://api.invoket.com/screen/address",
"tags": [
"compliance",
"verification",
"fraud-prevention",
"regulatory-data",
"weather"
],
"iconUrl": "https://invoket.com/apple-touch-icon.png",
"mimeType": "application/json",
"description": "Before your agent sends funds to a crypto address: check it against the sanctioned addresses published by OFAC (SDN and Consolidated) AND by the EU financial sanctions list - multi-list, where free feeds are OFAC-only - returning the designated entity, its programmes and its designation date behind every hit. Bitcoin, EVM, Tron, Solana and Monero. No transaction analysis, no clustering, no derived addresses, no risk score.",
"serviceName": "Invoket"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"type": "http",
"method": "GET",
"schema": {
"type": "object",
"required": [
"address"
],
"properties": {
"chain": {
"type": "string",
"description": "Optional family: 'bitcoin', 'evm', 'tron', 'solana' or 'monero'. Given, it is LAW - an address that does not have that family's shape is refused (400, unbilled), never reinterpreted as another family. Omitted, the family is inferred from the shape, and the answer says so in chain_family_source. 'other' is never inferred: outside the five named families, a value is an address only if a list publishes it verbatim, otherwise 400 UNRECOGNIZED_ADDRESS_FORMAT - unbilled, because a password or a misplaced IBAN must not be billed as a verdict"
},
"address": {
"type": "string",
"description": "Cryptocurrency address to screen, up to 128 characters (internal whitespace is collapsed - an address copied out of a PDF carries some). Compared on a normalized form whose rule the chain family dictates: EVM lowercased with 0x enforced, base58 case PRESERVED (it is significant), bech32 lowercased"
}
}
},
"headers": {
"accept": "application/json"
},
"queryParams": {
"chain": "bitcoin",
"address": "3My1ffQr5qQzmq4aBFgRqwRYqfB5zPAt8t"
}
},
"output": {
"type": "json",
"schema": {
"type": "object",
"required": [
"data",
"provenance"
],
"properties": {
"data": {
"type": "object",
"required": [
"hits",
"limits",
"lists_screened",
"query",
"verdict"
],
"properties": {
"hits": {
"type": "array",
"items": {
"type": "object",
"required": [
"address_published",
"chain",
"entity_id",
"entity_name",
"list_source",
"listed_on",
"programs"
],
"properties": {
"chain": {
"type": [
"string",
"null"
],
"description": "The chain token as the list publishes it (BTC, ETH, XBT...), verbatim. It does NOT decide the family: when the token contradicts the shape, the shape wins and the token is still reported as published. Null when the list publishes no token"
},
"programs": {
"type": "array",
"items": {
"type": "string"
}
},
"entity_id": {
"type": "string"
},
"listed_on": {
"type": [
"string",
"null"
],
"description": "Date the entity was listed by that authority, as published. Null when the list publishes no date"
},
"entity_name": {
"type": "string"
},
"list_source": {
"type": "string",
"description": "The list that published this designation: 'OFAC-SDN', 'OFAC-CONS', 'EU-FSF' or 'UN'. The EU entries are the multi-list edge: free feeds carry OFAC only"
},
"address_published": {
"type": "string",
"description": "The address exactly as the list publishes it, before normalization - what you quote back to a counterparty"
}
}
},
"description": "One entry per (address, designated entity) pair, never merged: an address published by two authorities, or under two chain tokens, returns several hits. Not capped"
},
"query": {
"type": "object",
"required": [
"address",
"address_normalized",
"chain_family",
"chain_family_source"
],
"properties": {
"address": {
"type": "string"
},
"chain_family": {
"type": "string"
},
"address_normalized": {
"type": "string",
"description": "The form the lookup actually used. Returned so you can reproduce it: a mismatch between your normalization and ours is how a designated address goes unnoticed"
},
"chain_family_source": {
"type": "string",
"description": "'declared' when you passed 'chain', 'inferred' when the family was read off the address shape, 'listed' when the value is outside the five named families and a list publishes it verbatim (this is how Litecoin bech32 and Bitcoin Cash cashaddr addresses stay visible)"
}
}
},
"limits": {
"type": "string",
"description": "Fixed sentence served inside every response: absence from a list is not a safety signal; no transaction analysis, no clustering, no derived addresses; the EIP-55 checksum is not verified and never causes a rejection"
},
"verdict": {
"type": "string",
"description": "Closed enumeration, binary: 'sanctioned' (at least one designation covers this address) or 'not_listed' (no designation covers it, for the lists and snapshot date reported here). Nothing in between - graded risk, proximity or a score would be a judgement, not official data"
},
"lists_screened": {
"type": "array",
"items": {
"type": "object",
"required": [
"addresses",
"list"
],
"properties": {
"list": {
"type": "string"
},
"addresses": {
"type": "integer"
}
}
},
"description": "The four lists screened and how many addresses each contributed, INCLUDING the ones at zero (the UN publishes no crypto address to date): an absence of data is not an absence of checking. Each count is of entries published by that list, not of distinct addresses: an address designated by several lists counts once PER LIST (no cross-list merging), so the total exceeds the number of distinct addresses in the store"
}
}
},
"provenance": {
"type": "object",
"required": [
"fetched_at",
"freshness",
"source"
],
"properties": {
"source": {
"type": "string"
},
"freshness": {
"type": "object",
"required": [
"as_of",
"kind"
],
"properties": {
"kind": {
"type": "string"
},
"as_of": {
"type": "string"
}
}
},
"fetched_at": {
"type": "string"
}
}
}
}
},
"example": {
"data": {
"hits": [
{
"chain": "BTC",
"programs": [
"UKR"
],
"entity_id": "EU:EU.12747.39",
"listed_on": "2025-02-24",
"entity_name": "Garantex",
"list_source": "EU-FSF",
"address_published": "3My1ffQr5qQzmq4aBFgRqwRYqfB5zPAt8t"
}
],
"query": {
"address": "3My1ffQr5qQzmq4aBFgRqwRYqfB5zPAt8t",
"chain_family": "bitcoin",
"address_normalized": "3My1ffQr5qQzmq4aBFgRqwRYqfB5zPAt8t",
"chain_family_source": "inferred"
},
"limits": "Screening covers the designation lists and snapshot date reported above, and only addresses those lists publish themselves. Absence from an official list is not a safety signal. No transaction analysis, no address clustering, no derived or associated addresses, and no risk scoring are performed. EVM addresses are matched case-insensitively; the EIP-55 checksum is not verified and never causes a rejection.",
"verdict": "sanctioned",
"lists_screened": [
{
"list": "EU-FSF",
"addresses": 7
},
{
"list": "OFAC-CONS",
"addresses": 0
},
{
"list": "OFAC-SDN",
"addresses": 961
},
{
"list": "UN",
"addresses": 0
}
]
},
"provenance": {
"source": "ofac-sdn+ofac-consolidated+eu-fsf+un-sc",
"freshness": {
"kind": "snapshot",
"as_of": "2026-07-28T00:00:00Z"
},
"fetched_at": "2026-07-30T06:08:59Z"
}
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method"
],
"properties": {
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"GET",
"HEAD",
"DELETE"
],
"type": "string"
},
"schema": {
"type": "object"
},
"headers": {
"type": "object",
"additionalProperties": {
"type": "string"
}
},
"queryParams": {
"type": "object",
"required": [
"address"
],
"properties": {
"chain": {
"type": "string",
"description": "Optional family: 'bitcoin', 'evm', 'tron', 'solana' or 'monero'. Given, it is LAW - an address that does not have that family's shape is refused (400, unbilled), never reinterpreted as another family. Omitted, the family is inferred from the shape, and the answer says so in chain_family_source. 'other' is never inferred: outside the five named families, a value is an address only if a list publishes it verbatim, otherwise 400 UNRECOGNIZED_ADDRESS_FORMAT - unbilled, because a password or a misplaced IBAN must not be billed as a verdict"
},
"address": {
"type": "string",
"description": "Cryptocurrency address to screen, up to 128 characters (internal whitespace is collapsed - an address copied out of a PDF carries some). Compared on a normalized form whose rule the chain family dictates: EVM lowercased with 0x enforced, base58 case PRESERVED (it is significant), bech32 lowercased"
}
}
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
}
}
},
"x402Version": 2
}Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.01 USDC on Base to 0x4465…128ee. The signed payment is good for 1 minute.
- Paid to
- 0x4465…128ee
- USD Coin contract
- 0x8335…02913
- Payment window
- 1 minute
- As published
- 10000 smallest units
- Returns
- application/json
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x4465825B0ac713aA2Fa07Ea29023020804A128ee",
"scheme": "exact",
"network": "eip155:8453",
"mimeType": "application/json",
"resource": "https://api.invoket.com/screen/address",
"description": "",
"maxAmountRequired": "10000",
"maxTimeoutSeconds": 60
}
]Provenance
- Seen in the source catalog
- 2026-10-19 13:10Z
- Last indexed by Roundhouse
- 2026-10-24 06:16Z
- Last enriched (probe, favicon, geo)
- 2026-10-07 22:16Z
- x402 version
- 1
- Max timeout
- 60s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 30 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service api.invoket.com and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=api.invoket.com' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://api.invoket.com/screen/address, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.