# Revenue Mesh Submission Packet

> 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

## Facts

- Endpoint: POST https://tender-radar-pb.peterbellbring.workers.dev/v1/submission-packet?utm_source=zero.xyz
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/revenue-mesh-submission-packet-32ab630a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_C-qbVRZQxwdoN83GROmnX

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability revenue-mesh-submission-packet-32ab630a -d '<json body>'
```

Example prompt: Can you validate my deliverable submission for the funded task with canonical key 'task-abc-123'? The deliverable is at https://example.com/my-work-output — I need to get the claim message so I can collect the reward.

## When to prefer this

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.

## Known failure modes

- 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

## 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.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "canonical_key": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "claim_message": "..."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/revenue-mesh-submission-packet-32ab630a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tender-radar-pb.peterbellbring.workers.dev](https://www.zero.xyz/host/tender-radar-pb.peterbellbring.workers.dev/llms.txt)