Sanciones Recientes Pago
by Vextorium in Security & trust
Recent additions to the EU consolidated sanctions list (persons and entities designated in the last N days) with program (country or regime), type and date. Keep a compliance screen up to date.
https://api.vextorium.com/sanciones-recientes-pago- Price
- $0.004
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 3 h ago, next any minute now
Reliability
Latest check failed 3 h ago: Amount "0.004" is not in atomic token units
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://api.vextorium.com/sanciones-recientes-pago
Each call costs $0.004 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.
POST https://api.vextorium.com/sanciones-recientes-pago
content-type: application/json
{
"dias": 120
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
dias | integer | No | 1-365 (default 30) |
Example response
The provider's example. We can't check it without paying.
Example response, 28 lines
{
"altas": 227,
"designaciones": [
{
"alias": 4,
"fecha": "2026-07-23",
"nombre": "Andrei Doronin",
"programa": "UKR",
"referencia": "EU.14452.59",
"tipo": "persona"
},
{
"alias": 3,
"fecha": "2026-07-23",
"nombre": "Rimma Falalejevová",
"programa": "UKR",
"referencia": "EU.14453.58",
"tipo": "persona"
}
],
"dias": 120,
"fuente": "Lista consolidada de sanciones financieras de la UE (Comisión Europea)",
"por_programa": {
"BLR": 2,
"IRN": 3,
"UKR": 222
}
}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.004.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.vextorium.com/sanciones-recientes-pago' \
-H 'content-type: application/json' \
--data-raw '{"dias":120}'
# 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 - -X POST 'https://api.vextorium.com/sanciones-recientes-pago' \
-H 'content-type: application/json' \
--data-raw '{"dias":120}' \
| 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.004 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.004" });
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.004 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.vextorium.com%2Fsanciones-recientes-pago&method=POST
const res = await pay("https://api.vextorium.com/sanciones-recientes-pago", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"dias": 120
}),
});
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.004 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.004"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.vextorium.com/sanciones-recientes-pago",
json={
"dias": 120,
},
)
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 |
|---|---|---|---|---|
| 3 h ago | Amount "0.004" is not in atomic token units | 402 | 109 ms | $0.004 |
| 8 h ago | Amount "0.004" is not in atomic token units | 402 | 79 ms | $0.004 |
| 13 h ago | Amount "0.004" is not in atomic token units | 402 | 223 ms | $0.004 |
| 17 h ago | Amount "0.004" is not in atomic token units | 402 | 168 ms | $0.004 |
| 22 h ago | Amount "0.004" is not in atomic token units | 402 | 187 ms | $0.004 |
Show 10 older checks
| 27 h ago | Amount "0.004" is not in atomic token units | 402 | 105 ms | $0.004 |
| 32 h ago | Amount "0.004" is not in atomic token units | 402 | 92 ms | $0.004 |
| 36 h ago | Amount "0.004" is not in atomic token units | 402 | 131 ms | $0.004 |
| 41 h ago | Amount "0.004" is not in atomic token units | 402 | 247 ms | $0.004 |
| 46 h ago | Amount "0.004" is not in atomic token units | 402 | 98 ms | $0.004 |
| 2 days ago | Amount "0.004" is not in atomic token units | 402 | 79 ms | $0.004 |
| 2 days ago | Amount "0.004" is not in atomic token units | 402 | 76 ms | $0.004 |
| 2 days ago | Amount "0.004" is not in atomic token units | 402 | 83 ms | $0.004 |
| 3 days ago | Amount "0.004" is not in atomic token units | 402 | 114 ms | $0.004 |
| 3 days ago | Amount "0.004" is not in atomic token units | 402 | 238 ms | $0.004 |