ToolVet
16trust / 100

Url Maliciosa Pago

by Vextorium in Security & trust

x402 APIFailing, checked 3 h ago

Check whether a URL or domain is listed in abuse.ch URLhaus as a malware distribution site in the last 30 days: exact URL match and other malicious URLs on the same host, with threat type, online/offline status and date. Use before an agent fetches or opens a link.

POST https://api.vextorium.com/url-maliciosa-pago

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
0.0%
Response time
- typical, - slowest 5%
Last check
3 h ago: Amount "0.002" is not in atomic token units
Next check
any minute now

How to call it

POST https://api.vextorium.com/url-maliciosa-pago

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

From the listing.

POST https://api.vextorium.com/url-maliciosa-pago
content-type: application/json

{
  "url": "https://example.com"
}

Parameters

ParameterTypeRequiredDescription
urlstringYes

Example response

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

{
  "base_de_datos": {
    "actualizada": "2026-10-03T00:59:28+00:00",
    "urls": 15473
  },
  "coincidencia_exacta": null,
  "consulta": "https://example.com",
  "ejemplos": [],
  "fuente": "URLhaus de abuse.ch (CC0), URLs de los últimos 30 días",
  "host": "example.com",
  "listada": false,
  "online_ahora": 0,
  "urls_maliciosas_del_host": 0,
  "veredicto": "no listada"
}

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 -X POST 'https://api.vextorium.com/url-maliciosa-pago' \
  -H 'content-type: application/json' \
  --data-raw '{"url":"https://example.com"}'

# 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/url-maliciosa-pago' \
  -H 'content-type: application/json' \
  --data-raw '{"url":"https://example.com"}' \
  | 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%2Fapi.vextorium.com%2Furl-maliciosa-pago&method=POST
const res = await pay("https://api.vextorium.com/url-maliciosa-pago", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "url": "https://example.com"
  }),
});
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.post(
        "https://api.vextorium.com/url-maliciosa-pago",
        json={
            "url": "https://example.com",
        },
    )
    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
3 h agoAmount "0.002" is not in atomic token units402247 ms$0.002
7 h agoAmount "0.002" is not in atomic token units402139 ms$0.002
12 h agoAmount "0.002" is not in atomic token units40281 ms$0.002
16 h agoAmount "0.002" is not in atomic token units40282 ms$0.002
20 h agoAmount "0.002" is not in atomic token units40295 ms$0.002
25 h agoAmount "0.002" is not in atomic token units40291 ms$0.002
29 h agoAmount "0.002" is not in atomic token units40278 ms$0.002
33 h agoAmount "0.002" is not in atomic token units40291 ms$0.002
37 h agoAmount "0.002" is not in atomic token units40279 ms$0.002
41 h agoAmount "0.002" is not in atomic token units40292 ms$0.002
45 h agoAmount "0.002" is not in atomic token units40281 ms$0.002
2 days agoAmount "0.002" is not in atomic token units40279 ms$0.002
2 days agoAmount "0.002" is not in atomic token units40288 ms$0.002
2 days agoAmount "0.002" is not in atomic token units40290 ms$0.002
3 days agoAmount "0.002" is not in atomic token units40279 ms$0.002