X402 Check
by Horizon Pulse in Developer tools
x402 developer tool. Use before paying an unknown x402 endpoint, or to debug your own. GET with required url (optional method GET/POST, body JSON for POST probes). Sends one unpaid request and never pays. Returns JSON: httpStatus, isX402, x402Version, decoded accepts (network, asset label, amount in USD, payTo and whether payTo is an EOA or contract), discovery metadata presence, and pass/warn/fail checks with a summary. Private targets are blocked. Errors are not charged.
https://horizonpulse.dev/api/x402-check- Price
- $0.01
- per call in USDC
- Uptime
- 28.6%
- last 30 days
- Response time
- 252 ms
- 577 ms slowest 5%
- Last check
- Failed
- 4 h ago, next any minute now
Reliability
Latest check failed 4 h ago: Amount "0.01" is not in atomic token units
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://horizonpulse.dev/api/x402-check
Each call costs $0.01 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://horizonpulse.dev/api/x402-check?method=GET&url=https%3A%2F%2Fhorizonpulse.dev%2Fapi%2FpulseParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | No | Optional JSON body (<=8KB, URL-encoded) sent with a POST probe, for endpoints that validate input before returning 402. Implies POST. |
method | string | No | HTTP method for the unpaid probe: GET (default; one POST retry on 405) or POST. |
url | string | Yes | Absolute http(s) URL of the x402 endpoint to audit (required). Private/localhost blocked. |
Example response
The provider's example. We can't check it without paying.
Example response, 52 lines
{
"accepts": [
{
"amountUsd": "$0.005",
"assetLabel": "USDC (Base)",
"network": "eip155:8453",
"payTo": "0x5b32c973596078a967562ca652761404f19be0e9",
"payToType": "eoa"
}
],
"challengeSource": "header",
"checks": [
{
"id": "status_402",
"level": "pass"
},
{
"id": "challenge",
"level": "pass"
},
{
"id": "version",
"level": "pass"
},
{
"id": "payto_type",
"level": "info"
},
{
"id": "discovery",
"level": "pass"
}
],
"discovery": {
"hasInputSchema": true,
"hasOutputExample": true,
"method": "GET",
"present": true
},
"elapsedMs": 201,
"httpStatus": 402,
"isX402": true,
"method": "GET",
"ok": true,
"summary": {
"fail": 0,
"pass": 4,
"warn": 0
},
"target": "https://horizonpulse.dev/api/pulse",
"x402Version": 2
}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.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://horizonpulse.dev/api/x402-check?method=GET&url=https%3A%2F%2Fhorizonpulse.dev%2Fapi%2Fpulse'
# 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://horizonpulse.dev/api/x402-check?method=GET&url=https%3A%2F%2Fhorizonpulse.dev%2Fapi%2Fpulse' \
| 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fhorizonpulse.dev%2Fapi%2Fx402-check
const res = await pay("https://horizonpulse.dev/api/x402-check?method=GET&url=https%3A%2F%2Fhorizonpulse.dev%2Fapi%2Fpulse");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://horizonpulse.dev/api/x402-check?method=GET&url=https%3A%2F%2Fhorizonpulse.dev%2Fapi%2Fpulse")
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 |
|---|---|---|---|---|
| 4 h ago | Amount "0.01" is not in atomic token units | 402 | 250 ms | $0.01 |
| 10 h ago | Amount "0.01" is not in atomic token units | 402 | 444 ms | $0.01 |
| 14 h ago | Amount "0.01" is not in atomic token units | 402 | 391 ms | $0.01 |
| 19 h ago | Amount "0.01" is not in atomic token units | 402 | 227 ms | $0.01 |
| 24 h ago | Amount "0.01" is not in atomic token units | 402 | 262 ms | $0.01 |
Show 10 older checks
| 28 h ago | Amount "0.01" is not in atomic token units | 402 | 331 ms | $0.01 |
| 33 h ago | Amount "0.01" is not in atomic token units | 402 | 340 ms | $0.01 |
| 38 h ago | Amount "0.01" is not in atomic token units | 402 | 215 ms | $0.01 |
| 43 h ago | Amount "0.01" is not in atomic token units | 402 | 261 ms | $0.01 |
| 47 h ago | Amount "0.01" is not in atomic token units | 402 | 192 ms | $0.01 |
| 2 days ago | Amount "0.01" is not in atomic token units | 402 | 151 ms | $0.01 |
| 2 days ago | Amount "0.01" is not in atomic token units | 402 | 300 ms | $0.01 |
| 3 days ago | Amount "0.01" is not in atomic token units | 402 | 273 ms | $0.01 |
| 3 days ago | Amount "0.01" is not in atomic token units | 402 | 280 ms | $0.01 |
| 3 days ago | Amount "0.01" is not in atomic token units | 402 | 248 ms | $0.01 |