Paymaster Check
by Paymaster Check in Onchain & crypto
๐ Given a paymaster address, audits whether it's a healthy, active gas sponsor. Reads its UserOperationEvents across both EntryPoints: sponsored op volume, distinct accounts served, success rate, total gas sponsored, and concentration (the share coming from its single busiest app). The read to run before integrating a paymaster (Coinbase / Pimlico / Alchemy / custom), or judging who funds a counterparty's gas. paymaster= required, days= optional (default 30, max 90). Not financial advice.
https://402.com.tr/api/x402/paymaster-check- Price
- $0.05
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 485 ms
- 647 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
Status and outage history ยท Atom feed ยท Watch with other listings
How to call it
GET https://402.com.tr/api/x402/paymaster-check
Each call costs $0.05 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://402.com.tr/api/x402/paymaster-check?days=7&paymaster=0x2cc0c7981D846b9F2a16276556f6e8cb52BfB633Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
days | string | No | Lookback days (optional) |
paymaster | string | Yes | Paymaster address |
Example response
The provider's example. We can't check it without paying.
{
"checkedAt": "2026-10-11T17:26:27.592Z",
"known": false,
"label": null,
"nativeAaLive": false,
"paymaster": "0x2cc0c7981D846b9F2a16276556f6e8cb52BfB633",
"sponsoredOps": 131547,
"verdict": "healthy_active",
"windowDays": 7
}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.05.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://402.com.tr/api/x402/paymaster-check?days=7&paymaster=0x2cc0c7981D846b9F2a16276556f6e8cb52BfB633'
# 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://402.com.tr/api/x402/paymaster-check?days=7&paymaster=0x2cc0c7981D846b9F2a16276556f6e8cb52BfB633' \
| 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.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
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.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F402.com.tr%2Fapi%2Fx402%2Fpaymaster-check
const res = await pay("https://402.com.tr/api/x402/paymaster-check?days=7&paymaster=0x2cc0c7981D846b9F2a16276556f6e8cb52BfB633");
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.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://402.com.tr/api/x402/paymaster-check?days=7&paymaster=0x2cc0c7981D846b9F2a16276556f6e8cb52BfB633")
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 | Passed | 402 | 505 ms | $0.05 |
| 8 h ago | Passed | 402 | 485 ms | $0.05 |
| 13 h ago | Passed | 402 | 519 ms | $0.05 |
| 17 h ago | Passed | 402 | 509 ms | $0.05 |
| 21 h ago | Passed | 402 | 563 ms | $0.05 |
Show 10 older checks
| 25 h ago | Passed | 402 | 494 ms | $0.05 |
| 30 h ago | Passed | 402 | 524 ms | $0.05 |
| 34 h ago | Passed | 402 | 619 ms | $0.05 |
| 38 h ago | Passed | 402 | 471 ms | $0.05 |
| 43 h ago | Passed | 402 | 491 ms | $0.05 |
| 47 h ago | Passed | 402 | 647 ms | $0.05 |
| 2 days ago | Passed | 402 | 493 ms | $0.05 |
| 2 days ago | Passed | 402 | 345 ms | $0.05 |
| 2 days ago | Passed | 402 | 643 ms | $0.05 |
| 3 days ago | Passed | 402 | 367 ms | $0.05 |