X402scan Scan
by x402 Trust Scan in Security & trust
Pre-payment trust check of any x402 endpoint, so an agent can filter malformed or unknown (honeypot) endpoints before spending. Reads the target's own 402 terms (reachability, HTTPS, well-formed x402 v2, Bazaar discovery extension) and the public Coinbase CDP catalog (whether the payTo has settled history). Returns tier ESTABLISHED/BASIC/UNVERIFIED, a 0-100 trust_score, per-signal booleans and reasons. It never pays the target; a high tier is not a guarantee. Query: ?url=<x402 endpoint url>
https://gdzlcxskuhupymyxywzm.supabase.co/functions/v1/x402scan/v1/scan- Price
- $0.02
- per call in USDC
- Uptime
- 88.0%
- last 30 days
- Response time
- 1.8 s
- 1.9 s slowest 5%
- Last check
- Failed
- 12 h ago, next in 2 days
Reliability
Latest check failed 12 h ago: Expected HTTP 402, got 404
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://gdzlcxskuhupymyxywzm.supabase.co/functions/v1/x402scan/v1/scan
Each call costs $0.02 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://gdzlcxskuhupymyxywzm.supabase.co/functions/v1/x402scan/v1/scan?url=https%3A%2F%2Fgdzlcxskuhupymyxywzm.supabase.co%2Ffunctions%2Fv1%2Ftokenguard-evm%2Fv1%2FcheckParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Full URL of the x402 endpoint to assess (https) |
Example response
The provider's example. We can't check it without paying.
Example response, 35 lines
{
"payment_options": [
{
"amount_atomic": "10000",
"asset": "0x8335...2913",
"network": "eip155:8453",
"payTo": "0x.....",
"scheme": "exact"
}
],
"reasons": [],
"seller_reputation": [
{
"cataloged_resources": 4,
"in_cdp_catalog": true,
"network_hint": "evm",
"payTo": "0x....."
}
],
"signals": {
"discovery_extension_declared": true,
"discovery_extension_typed": true,
"https": true,
"payment_terms_well_formed": true,
"public_host": true,
"reachable": true,
"returns_402": true,
"seller_has_cdp_settled_history": true,
"x402_terms_parsed": true
},
"tier": "ESTABLISHED",
"trust_score": 85,
"url": "https://example.com/functions/v1/some-service/v1/check",
"well_formed_x402": 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.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://gdzlcxskuhupymyxywzm.supabase.co/functions/v1/x402scan/v1/scan?url=https%3A%2F%2Fgdzlcxskuhupymyxywzm.supabase.co%2Ffunctions%2Fv1%2Ftokenguard-evm%2Fv1%2Fcheck'
# 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://gdzlcxskuhupymyxywzm.supabase.co/functions/v1/x402scan/v1/scan?url=https%3A%2F%2Fgdzlcxskuhupymyxywzm.supabase.co%2Ffunctions%2Fv1%2Ftokenguard-evm%2Fv1%2Fcheck' \
| 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fgdzlcxskuhupymyxywzm.supabase.co%2Ffunctions%2Fv1%2Fx402scan%2Fv1%2Fscan
const res = await pay("https://gdzlcxskuhupymyxywzm.supabase.co/functions/v1/x402scan/v1/scan?url=https%3A%2F%2Fgdzlcxskuhupymyxywzm.supabase.co%2Ffunctions%2Fv1%2Ftokenguard-evm%2Fv1%2Fcheck");
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://gdzlcxskuhupymyxywzm.supabase.co/functions/v1/x402scan/v1/scan?url=https%3A%2F%2Fgdzlcxskuhupymyxywzm.supabase.co%2Ffunctions%2Fv1%2Ftokenguard-evm%2Fv1%2Fcheck")
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 |
|---|---|---|---|---|
| 12 h ago | Expected HTTP 402, got 404 | 404 | 111 ms | - |
| 43 h ago | Expected HTTP 402, got 404 | 404 | 107 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 107 ms | - |
| 4 days ago | Expected HTTP 402, got 404 | 404 | 74 ms | - |
| 4 days ago | Expected HTTP 402, got 404 | 404 | 120 ms | - |
Show 10 older checks
| 5 days ago | Expected HTTP 402, got 404 | 404 | 118 ms | - |
| 5 days ago | Expected HTTP 402, got 404 | 404 | 122 ms | - |
| 6 days ago | Expected HTTP 402, got 404 | 404 | 164 ms | - |
| 6 days ago | Expected HTTP 402, got 404 | 404 | 122 ms | - |
| 6 days ago | Expected HTTP 402, got 404 | 404 | 124 ms | - |
| 7 days ago | Passed | 402 | 1.7 s | $0.02 |
| 7 days ago | Passed | 402 | 1.8 s | $0.02 |
| 7 days ago | Passed | 402 | 1.7 s | $0.02 |
| 8 days ago | Passed | 402 | 1.9 s | $0.02 |
| 8 days ago | Passed | 402 | 1.9 s | $0.02 |