Back to Browse
MYCELIX Delivery Receipt Verifier
x402
MYCELIX Delivery Receipt Verifier is a paid API for AI agents from neo-collettive.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).
Verifies an x402 delivery receipt, checking signatures and hop integrity to confirm a payment-gated API response was authentically delivered
Price / call$0.01
Success—
StatusUnknown
How this service works
Verify an x402 delivery receipt (v0.1): seller signature, settlement and refusal rules, hop chain naming who changed the bytes. Signed, logged verdict.
Output
A JSON object with: `ok` (boolean, true if all checks pass), `fails` (array of failure descriptions if any), `notes` (array of informational messages), `signature` (the signed verification result from MYCELIX's log), and `changed_by` (null if unmodified, otherwise indicates which party changed the payload).
Example use cases
Post-payment delivery integrity check
“I just paid for an x402 API call and got back a receipt. Can you verify it using the receipt object, hop public keys, the SHA-256 of what I sent, and the seller's public key to make sure the delivery is authentic and nothing was tampered with?”
Offline audit of past x402 transaction
“I have an x402 delivery receipt from last week and I want to audit it offline. Run the verification with the receipt, the hop keys, buyer body hash, and seller public key and tell me if any checks failed.”
Multi-hop intermediary tamper detection
“We routed an x402 API call through several hops and I'm worried one of them might have modified the response. Please verify the delivery receipt against all the hop public keys and the seller's key to see if anything was changed.”
Technical details
Endpoint
POSThttps://neo-collettive.onrender.com/x402/delivery-receipt-verify?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need to cryptographically verify that an x402 pay-per-call API response was authentically delivered without tampering — especially when routing through multiple hops or intermediaries. Prefer this over manual inspection when you need a signed, loggable proof of verification that can be audited offline. Ideal for agents operating in trustless or multi-party environments where delivery integrity of paid API responses must be provable.
Side effects
- Invalid or malformed receipt object returns ok:false with descriptive fails array
- Signature mismatch on seller public key causes verification failure
- Hop public key mismatch indicates possible intermediary tampering
- Missing required fields (receipt, seller_public_key_b64) cause request rejection
- Network or server unavailability on Render hosting may cause timeouts
- Malformed base64 seller public key causes parsing error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| receipt | object | |
| hop_public_keys | object | |
| buyer_body_sha256 | string | |
| seller_public_key_b64 | string |
Output
Schema · Response
{
"type": "json",
"example": {
"ok": true,
"fails": [],
"notes": [],
"signature": "...",
"changed_by": null
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"