13trust / 100

Sanctions Address

by Saylor Innovations Sanctions Scr in Security & trust

x402 APIFailing, checked 28 min ago

OFAC sanctions screening for a crypto wallet address against the U.S. Treasury SDN list

GET
https://saylorinnovations.com/api/sanctions/address/:address
Price
$0.002
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
28 min ago, next in 30 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 28 min ago: Expected HTTP 402, got 400

Status and outage history · Atom feed

How to call it

GET https://saylorinnovations.com/api/sanctions/address/:address

Each call costs $0.002 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

The listing has no example input.

GET https://saylorinnovations.com/api/sanctions/address/:address

Example response

The provider's example. We can't check it without paying.

{
  "address": "0x0330070FD38Ec3bB94F58FA55D40368271E9e54A",
  "currencies": [
    "ETH"
  ],
  "entity": {
    "name": "AMNOKGANG TECHNOLOGY DEVELOPMENT COMPANY",
    "programs": [
      "DPRK4"
    ],
    "sdn_id": 36345,
    "type": "entity"
  },
  "sanctioned": true
}

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.002.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://saylorinnovations.com/api/sanctions/address/:address'

# 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://saylorinnovations.com/api/sanctions/address/:address' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
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.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsaylorinnovations.com%2Fapi%2Fsanctions%2Faddress%2F%3Aaddress
const res = await pay("https://saylorinnovations.com/api/sanctions/address/:address");
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.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://saylorinnovations.com/api/sanctions/address/:address")
    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

WhenResultHTTPTimePrice
28 min agoExpected HTTP 402, got 400400365 ms-
5 h agoExpected HTTP 402, got 400400264 ms-
10 h agoExpected HTTP 402, got 400400580 ms-
15 h agoExpected HTTP 402, got 400400563 ms-
19 h agoExpected HTTP 402, got 400400542 ms-
Show 10 older checks
24 h agoExpected HTTP 402, got 400400538 ms-
28 h agoExpected HTTP 402, got 400400528 ms-
33 h agoExpected HTTP 402, got 4004001.4 s-
37 h agoExpected HTTP 402, got 400400265 ms-
41 h agoExpected HTTP 402, got 400400863 ms-
46 h agoExpected HTTP 402, got 400400277 ms-
2 days agoExpected HTTP 402, got 400400254 ms-
2 days agoExpected HTTP 402, got 400400494 ms-
2 days agoExpected HTTP 402, got 400400294 ms-
3 days agoExpected HTTP 402, got 4004001.2 s-