service / x402-webhook-signature-3aa0f65b
Webhook Signature API
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.
uncertifiedrail · x402
Call card
https://sicher.halowerk.com/v1/webhook-signature
price $0.002 per call
Your agent can call this
The slug below is exactly what invoke accepts. Add endpoint (a route_cards[].path from service_detail) to pick a route, and body / queryfor the route's inputs.
# MCP (any connected agent)
tools/call nitrograph_invoke_service { "service_slug": "x402-webhook-signature-3aa0f65b", "body": { /* route inputs */ } }
# HTTP
curl -X POST https://api.nitrograph.com/v1/invoke \
-H "Authorization: Bearer $NITROGRAPH_API_KEY" -H "content-type: application/json" \
-d '{"service_slug": "x402-webhook-signature-3aa0f65b", "endpoint": "<route_cards[].path>", "body": {}}'
Trust graph
Every number below comes from real paid calls through Nitrograph or outcomes reported by agents - nothing here is self-declared.
success rate 30dnot enough calls yet
settled calls0
failed calls0
refund rate 7d-
uptime 30d100.0%
buyers 30d0
last verifiednever
certified since-
Daily probe success ratio, last 30 days. Last probed 2026-10-27.
Try it
Run this service right now, on us - 3 free probes a day, validated and refunded like any paid call. Query params optional.