Utilities · x402 · early usage

Providers each build their signing string differently — some sign only the body, others…

by sicher.halowerk.com · discovered, not yet claimed by its owner · updated 2026-10-08

30d calls4

30d payers4

MethodPOST

Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Providers each build their signing string differently — some sign only the body, others prepend a timestamp, an id, or a version marker in a fixed order — and getting that order wrong produces a mismatch that looks exactly like an attack. This checks the signature the way the named provider actually specifies, with constant-time comparison, and returns the string that was signed so a mismatch can be debugged instead of guessed at.

Tags: bazaar

Call contract

Method: POST
Input: json
Output: json
Last paid call: 2026-10-08

Input example from Bazaar metadata

{
  "body": "{\"synthetic\":true,\"event\":\"documentation-example\"}",
  "provider": "github",
  "secret": "HALOWERK-public-synthetic-example-never-use-for-authentication",
  "signature": "sha256=fdfaa7380ce9e369a7d90e8651603bb777a4f008dd3070b056d2b59122d602f8"
}

No output exampleProvider did not publish one in Bazaar metadata.

Use with an agent

Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
Inspect. Fetch /resources/55189.json for the price and payment options.
Pay. Call GET https://sicher.halowerk.com/v1/webhook-signature. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price: $0.002 / request
Protocol: x402 v2
Auth: No account or API key. Pay per request.
Networks: Base
Demand: 4 calls · 4 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

Scheme	Network	Asset	Amount	Pay to	Timeout
exact	Base eip155:8453	USDC	$0.002	0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E	300s

accepts[] (raw JSON)

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "2000",
    "amountUsd": 0.002,
    "maxTimeoutSeconds": 300
  }
]

Examples

curl

curl "https://sicher.halowerk.com/v1/webhook-signature"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid

JavaScript

const res = await fetch("https://sicher.halowerk.com/v1/webhook-signature");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}

Python

import httpx
res = httpx.get("https://sicher.halowerk.com/v1/webhook-signature")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider: sicher.halowerk.com
Endpoint: https://sicher.halowerk.com/v1/webhook-signature
Machine-readable: /resources/55189.json