Check Full
by Kertivo Shield (full) in Onchain & crypto
Full-history address-poisoning check before you send USDC on Base. Same risk/lookalike/seenBefore logic as /address/check, but funding history comes from ONE Blockscout index call (x402, up to the sender's 500 most recent Base USDC transfers; v2 page fallback) so coverage is usually the sender's full Base USDC history. Body {from, to}. Not charged if the index is down. Cheap partial/RPC tier: POST /address/check ($0.001).
https://paycheck.hectichustle.workers.dev/address/check/full- Price
- $0.005
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 584 ms
- 890 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://paycheck.hectichustle.workers.dev/address/check/full
Each call costs $0.005 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://paycheck.hectichustle.workers.dev/address/check/full
content-type: application/json
{
"from": "0xfc1e390266f3b29179b5d63a7937a689d1e5279a",
"to": "0xccd53f97ddfdf6939028698803dfe20fac455d07"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
contacts | array of string | No | Optional: up to 50 addresses you already trust (address book). 'to' is compared offline against them, so a lookalike of a contact is flagged even outside the scanned history. |
from | string | Yes | Sender address |
to | string | Yes | Intended recipient |
Example response
The provider's example. We can't check it without paying.
Example response, 40 lines
{
"coverage": {
"complete": true,
"counterparties": 10,
"coveragePct": 100,
"historyComplete": true,
"indexer": "blockscout x402 (paid page)",
"indexerPages": 1,
"lowCoverage": false,
"rpcCalls": 1,
"scannedFrom": 0,
"scannedTo": 52410000,
"source": "blockscout",
"transfersSeen": 12,
"windowBlocks": 52410000,
"windowFrom": 0,
"windowTo": 52410000
},
"from": "0xfc1e390266f3b29179b5d63a7937a689d1e5279a",
"lookalikes": [
{
"address": "0xccd560c57ca850ec6465008fdbc55d3b32b75d07",
"dustTransfers": 1,
"inbound": 0,
"lastBlock": 52377228,
"outbound": 1,
"pattern": "dust_or_zero_value",
"realOut": 0,
"sampleTx": "0xf34c5e5ecd6a10e63133633f3d0108019f2667bd6c0557390e01dd6c8ca4ddd4"
}
],
"mode": "live_paid_full",
"priceCharged": "0.005 USDC",
"reasons": [
"you have paid 'to' before, but 1 lookalike(s) also appear (poisoning attempt): keep using the full address you verified"
],
"risk": "medium",
"seenBefore": true,
"to": "0xccd53f97ddfdf6939028698803dfe20fac455d07"
}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.005.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://paycheck.hectichustle.workers.dev/address/check/full' \
-H 'content-type: application/json' \
--data-raw '{"from":"0xfc1e390266f3b29179b5d63a7937a689d1e5279a","to":"0xccd53f97ddfdf6939028698803dfe20fac455d07"}'
# 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://paycheck.hectichustle.workers.dev/address/check/full' \
-H 'content-type: application/json' \
--data-raw '{"from":"0xfc1e390266f3b29179b5d63a7937a689d1e5279a","to":"0xccd53f97ddfdf6939028698803dfe20fac455d07"}' \
| 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.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
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.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fpaycheck.hectichustle.workers.dev%2Faddress%2Fcheck%2Ffull&method=POST
const res = await pay("https://paycheck.hectichustle.workers.dev/address/check/full", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"from": "0xfc1e390266f3b29179b5d63a7937a689d1e5279a",
"to": "0xccd53f97ddfdf6939028698803dfe20fac455d07"
}),
});
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.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://paycheck.hectichustle.workers.dev/address/check/full",
json={
"from": "0xfc1e390266f3b29179b5d63a7937a689d1e5279a",
"to": "0xccd53f97ddfdf6939028698803dfe20fac455d07",
},
)
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 |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 535 ms | $0.005 |
| 7 h ago | Passed | 402 | 447 ms | $0.005 |
| 12 h ago | Passed | 402 | 584 ms | $0.005 |
| 17 h ago | Passed | 402 | 456 ms | $0.005 |
| 22 h ago | Passed | 402 | 771 ms | $0.005 |
Show 10 older checks
| 26 h ago | Passed | 402 | 740 ms | $0.005 |
| 31 h ago | Passed | 402 | 752 ms | $0.005 |
| 36 h ago | Passed | 402 | 758 ms | $0.005 |
| 40 h ago | Passed | 402 | 402 ms | $0.005 |
| 44 h ago | Passed | 402 | 694 ms | $0.005 |
| 2 days ago | Passed | 402 | 611 ms | $0.005 |
| 2 days ago | Passed | 402 | 557 ms | $0.005 |
| 2 days ago | Passed | 402 | 659 ms | $0.005 |
| 3 days ago | Passed | 402 | 577 ms | $0.005 |
| 3 days ago | Passed | 402 | 706 ms | $0.005 |