nostr.halowerk.com

Name: nostr.halowerk.com
Price: 0.002 USDC
Availability: InStock

HALOWERK provides paid endpoints that AI agents call and pay for per request via x402 on Base. No account, no API key, no signup.

OtherLiveeip155:8453Exactvia cdp

https://nostr.halowerk.com/zap-receipt-check

Calls · 30d

2→ 0%

This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 20 snapshots so far.

$11.47

Verified settled volume

2,654 settlements proven x402 by their on-chain EIP-3009 marker.

$0.0020

Listed price

As published in the catalog. Always read the live 402 before paying.

Calls · 30d

Upstream's own call count for this endpoint, not ours.

Unique payers · 30d

Last called 2026-08-13 11:34Z

—

Upstream on-chain volume

Reported by the source catalog.

Paid to

0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Live 402 challenge

Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.

{
  "docs": "https://nostr.halowerk.com/llms.txt",
  "name": "nostr_zap_receipt_check",
  "error": "payment_required",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "asset": "USDC",
        "version": "2",
        "eip712Domain": {
          "name": "USD Coin",
          "chainId": 8453,
          "version": "2",
          "verifyingContract": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
        },
        "network_name": "Base Mainnet",
        "assetTransferMethod": "eip3009"
      },
      "payTo": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
      "amount": "2000",
      "scheme": "exact",
      "network": "eip155:8453",
      "currency": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "recipient": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
      "maxTimeoutSeconds": 300
    }
  ],
  "pricing": "https://nostr.halowerk.com/pricing",
  "resource": {
    "url": "https://nostr.halowerk.com/zap-receipt-check",
    "mimeType": "application/json",
    "description": "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."
  },
  "extensions": {
    "bazaar": {
      "info": {
        "input": {
          "body": {
            "receipt": {},
            "event_id": "beispiel"
          },
          "type": "http",
          "method": "POST",
          "bodyType": "json"
        }
      },
      "schema": {
        "type": "object",
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "required": [
          "input"
        ],
        "properties": {
          "input": {
            "type": "object",
            "required": [
              "type",
              "method",
              "bodyType",
              "body"
            ],
            "properties": {
              "body": {
                "type": "object",
                "properties": {
                  "relays": {
                    "type": "array",
                    "items": {
                      "type": "string"
                    },
                    "maxItems": 12,
                    "description": "wss relay addresses used when fetching by event_id."
                  },
                  "receipt": {
                    "type": "object",
                    "description": "The complete kind 9735 event. Either this or event_id is required."
                  },
                  "event_id": {
                    "type": "string",
                    "description": "Event id of the receipt as hex, note or nevent. Fetched from the relays when receipt is not given."
                  },
                  "recipient_lightning_address": {
                    "type": "string",
                    "description": "Lightning address of the recipient, for example name@domain. Given, the issuer is compared against the nostrPubkey published there."
                  }
                },
                "additionalProperties": false
              },
              "type": {
                "type": "string",
                "const": "http"
              },
              "method": {
                "enum": [
                  "POST",
                  "PUT",
                  "PATCH"
                ],
                "type": "string"
              },
              "bodyType": {
                "enum": [
                  "json",
                  "form-data",
                  "text"
                ],
                "type": "string"
              }
            },
            "additionalProperties": false
          }
        }
      }
    }
  },
  "price_usdc": "0.002",
  "description": "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. The invoice description hash is compared against SHA-256 of the description tag, which is the link that ties a specific invoice to a specific zap request; a receipt failing this check carries an invoice that was never issued for it. Recipient and sender in the p and P tags are compared against the zap request. Optionally the recipient LNURL service is read and the receipt issuer is compared against the nostrPubkey it publishes — the check that actually distinguishes a genuine receipt from one signed by any key at all, and the one most implementations omit. The result is a verdict with the failed checks named. One thing is stated plainly in every answer: a zap is a Lightning payment and never touches the Bitcoin chain, so no on-chain confirmation exists or can be produced, and a receipt is evidence issued by the recipient service rather than proof of settlement.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "relays": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 12,
        "description": "wss relay addresses used when fetching by event_id."
      },
      "receipt": {
        "type": "object",
        "description": "The complete kind 9735 event. Either this or event_id is required."
      },
      "event_id": {
        "type": "string",
        "description": "Event id of the receipt as hex, note or nevent. Fetched from the relays when receipt is not given."
      },
      "recipient_lightning_address": {
        "type": "string",
        "description": "Lightning address of the recipient, for example name@domain. Given, the issuer is compared against the nostrPubkey published there."
      }
    },
    "additionalProperties": false
  },
  "price_model": "per_call",
  "x402Version": 2,
  "instructions": "Sign the accepted terms with an x402 client and repeat the request with the payment header.",
  "payment_header": "PAYMENT-SIGNATURE",
  "capability_request": {
    "url": "https://bedarf.halowerk.com/capabilities/request",
    "cost": "free",
    "method": "POST",
    "description": "Missing a capability, or does the scope not fit? Report the need here - no payment required. Similar reports are bundled; the response returns an id you can check back on.",
    "body_example": {
      "max_price": 0.01,
      "description": "what exactly is needed",
      "requested_capability": "short label"
    }
  }
}

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.002USDC≈ $0.002 USD

on Base · exact scheme

Pay 0.002 USDC on Base to 0x2880…C4E5E. The signed payment is good for 5 minutes.

Paid to: 0x2880…C4E5E
USD Coin contract: 0x8335…02913
Payment window: 5 minutes
As published: 2000 smallest units

The catalog’s raw entry

[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "asset": "USDC",
      "version": "2",
      "eip712Domain": {
        "name": "USD Coin",
        "chainId": 8453,
        "version": "2",
        "verifyingContract": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
      },
      "network_name": "Base Mainnet",
      "assetTransferMethod": "eip3009"
    },
    "payTo": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
    "amount": "2000",
    "scheme": "exact",
    "network": "eip155:8453",
    "currency": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "recipient": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
    "maxTimeoutSeconds": 300
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "body": {
          "receipt": {},
          "event_id": "beispiel"
        },
        "type": "http",
        "method": "POST",
        "bodyType": "json"
      }
    },
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method",
            "bodyType",
            "body"
          ],
          "properties": {
            "body": {
              "type": "object",
              "properties": {
                "relays": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  },
                  "maxItems": 12,
                  "description": "wss relay addresses used when fetching by event_id."
                },
                "receipt": {
                  "type": "object",
                  "description": "The complete kind 9735 event. Either this or event_id is required."
                },
                "event_id": {
                  "type": "string",
                  "description": "Event id of the receipt as hex, note or nevent. Fetched from the relays when receipt is not given."
                },
                "recipient_lightning_address": {
                  "type": "string",
                  "description": "Lightning address of the recipient, for example name@domain. Given, the issuer is compared against the nostrPubkey published there."
                }
              },
              "additionalProperties": false
            },
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "POST",
                "PUT",
                "PATCH"
              ],
              "type": "string"
            },
            "bodyType": {
              "enum": [
                "json",
                "form-data",
                "text"
              ],
              "type": "string"
            }
          },
          "additionalProperties": false
        }
      }
    }
  }
}

Provenance

Seen in the source catalog: 2026-08-13 11:34Z
Last indexed by Roundhouse: 2026-09-12 11:20Z
Last enriched (probe, favicon, geo): 2026-09-21 16:15Z
x402 version: 2
Max timeout: 300s
Liveness probe: HTTP 402

Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 20 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md

Show the prompt

Using Roundhouse, look up the x402 service nostr.halowerk.com and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=nostr.halowerk.com'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://nostr.halowerk.com/zap-receipt-check, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.