Zap Receipt Check
by nostr.halowerk.com in Markets & finance
Takes a kind 9735 receipt directly or fetches it from relays by event id, then runs eight named checks and reports each one separately with its reason. The receipt signature and the signature of the zap request enclosed in the description tag are verified per BIP-340. The invoice is decoded and its amount is compared against the amount tag of the zap request, since those two can disagree and only the invoice was payable.
POST https://nostr.halowerk.com/zap-receipt-check
Last 30 days
Status and outage history · Atom feed
- Uptime
- 100%
- Response time
- 138 ms typical, 203 ms slowest 5%
- Last check
- 2 h ago
- Next check
- any minute now
How to call it
POST https://nostr.halowerk.com/zap-receipt-check
Each call costs $0.002 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-receipt-check
content-type: application/json
{
"event_id": "beispiel",
"receipt": {}
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
event_id | string | No | Event id of the receipt as hex, note or nevent. Fetched from the relays when receipt is not given. |
receipt | object | No | The complete kind 9735 event. Either this or event_id is required. |
recipient_lightning_address | string | No | Lightning address of the recipient, for example name@domain. Given, the issuer is compared against the nostrPubkey published there. |
relays | array of string | No | wss relay addresses used when fetching by event_id. |
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.002.
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-receipt-check' \
-H 'content-type: application/json' \
--data-raw '{"event_id":"beispiel","receipt":{}}'
# 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-receipt-check' \
-H 'content-type: application/json' \
--data-raw '{"event_id":"beispiel","receipt":{}}' \
| 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.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
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.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fnostr.halowerk.com%2Fzap-receipt-check&method=POST
const res = await pay("https://nostr.halowerk.com/zap-receipt-check", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"event_id": "beispiel",
"receipt": {}
}),
});
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.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
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-receipt-check",
json={
"event_id": "beispiel",
"receipt": {},
},
)
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 | 108 ms | $0.002 |
| 6 h ago | Passed | 402 | 195 ms | $0.002 |
| 10 h ago | Passed | 402 | 139 ms | $0.002 |
| 13 h ago | Passed | 402 | 138 ms | $0.002 |
| 17 h ago | Passed | 402 | 187 ms | $0.002 |
| 21 h ago | Passed | 402 | 131 ms | $0.002 |
| 25 h ago | Passed | 402 | 160 ms | $0.002 |
| 28 h ago | Passed | 402 | 134 ms | $0.002 |
| 32 h ago | Passed | 402 | 153 ms | $0.002 |
| 36 h ago | Passed | 402 | 131 ms | $0.002 |
| 39 h ago | Passed | 402 | 141 ms | $0.002 |
| 43 h ago | Passed | 402 | 138 ms | $0.002 |
| 46 h ago | Passed | 402 | 188 ms | $0.002 |
| 2 days ago | Passed | 402 | 131 ms | $0.002 |
| 2 days ago | Passed | 402 | 120 ms | $0.002 |