ToolVet
78trust / 100

Zap Radar

by nostr.halowerk.com in Markets & finance

x402 APIPassing, checked 2 h ago

Collects kind 9735 zap receipts addressed to one public key over up to twelve relays, merges them by event id and reports who sent how much over the requested window. Every amount comes from decoding the BOLT-11 invoice carried in the receipt, not from the amount tag of the zap request, because the two can disagree and only the invoice was payable.

POST https://nostr.halowerk.com/zap-radar

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
128 ms typical, 164 ms slowest 5%
Last check
2 h ago
Next check
any minute now

How to call it

POST https://nostr.halowerk.com/zap-radar

Each call costs $0.004 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://nostr.halowerk.com/zap-radar
content-type: application/json

{
  "pubkey": "beispiel"
}

Parameters

ParameterTypeRequiredDescription
daysintegerNoLength of the window in days, counted back from now. Default: 30.
max_receiptsintegerNoUpper bound on receipts fetched per relay. Reaching it sets truncated. Default: 200.
pubkeystringYesRecipient public key as 64 hex characters, npub or nprofile.
relaysarray of stringNowss relay addresses. Left empty, ten measured default relays are used.
top_sendersintegerNoHow many senders the ranking lists. Default: 10.

Example response

The listing has no example response.

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.004.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://nostr.halowerk.com/zap-radar' \
  -H 'content-type: application/json' \
  --data-raw '{"pubkey":"beispiel"}'

# 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://nostr.halowerk.com/zap-radar' \
  -H 'content-type: application/json' \
  --data-raw '{"pubkey":"beispiel"}' \
  | 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.004 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.004" });
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.004 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fnostr.halowerk.com%2Fzap-radar&method=POST
const res = await pay("https://nostr.halowerk.com/zap-radar", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "pubkey": "beispiel"
  }),
});
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.004 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.004"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://nostr.halowerk.com/zap-radar",
        json={
            "pubkey": "beispiel",
        },
    )
    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
2 h agoPassed402170 ms$0.004
6 h agoPassed402145 ms$0.004
10 h agoPassed40242 ms$0.004
14 h agoPassed402145 ms$0.004
17 h agoPassed402126 ms$0.004
21 h agoPassed402136 ms$0.004
25 h agoPassed402162 ms$0.004
28 h agoPassed402147 ms$0.004
32 h agoPassed40246 ms$0.004
36 h agoPassed402131 ms$0.004
39 h agoPassed402123 ms$0.004
42 h agoPassed402164 ms$0.004
46 h agoPassed402128 ms$0.004
2 days agoPassed402137 ms$0.004
2 days agoPassed402105 ms$0.004