Back to Browse
Revenue Mesh Submission Packet
x402
Revenue Mesh Submission Packet is a paid API for AI agents from tender-radar-pb.peterbellbring.workers.dev, paid per call via x402, $1/call, status unknown (last checked 2026-10-12).
Validates a funded-task deliverable submission by checking a URL against a canonical task key and returning a claim message for payout
Price / call$1
Success—
StatusUnknown
How this service works
Funded-task intelligence and deterministic deliverable validation
Output
A JSON object containing a 'data' field with a 'claim_message' string, which serves as cryptographic or structured proof that the submitted deliverable passed deterministic validation and qualifies for the associated task payout.
Example use cases
Bounty deliverable claim after completion
“I finished the funded task with canonical key 'bounty-xyz-789' and my submission is hosted at https://myrepo.com/output — can you validate it and get me the claim message so I can get paid?”
Automated agent pipeline task verification
“My agent just finished the work for canonical task 'pipeline-task-001' and published the result to https://agent-output.example.com/result — validate the submission and return the claim message so the workflow can proceed to payment.”
Freelance proof-of-work submission check
“I submitted my deliverable at https://docs.example.com/my-report for the funded task 'report-task-042' — can you run it through the deterministic validator and tell me if I get a valid claim message?”
Technical details
Endpoint
POSThttps://tender-radar-pb.peterbellbring.workers.dev/v1/submission-packet?utm_source=zero.xyzWhen to prefer
Use this endpoint when an agent or user has completed a funded task and needs to programmatically submit a deliverable URL against a canonical task key to receive a deterministic pass/fail result and a claim message for payout. It is purpose-built for bounty, grant, or funded-task workflows where the validation logic is pre-specified and the output is a structured claim credential, not a human review.
Side effects
- Invalid or unreachable URL returns a validation failure with no claim message
- Mismatched canonical_key causes rejection if the key does not correspond to any funded task
- Missing required fields (url or canonical_key) results in a 400-level error
- URL content does not satisfy the deterministic validation criteria, returning a failed status
- Payment of 1 USDC not provided triggers a 402 Payment Required response before any validation occurs
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| url | string | |
| canonical_key | string |
Output
Schema · Response
{
"type": "json",
"example": {
"data": {
"claim_message": "..."
}
}
}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"