# Revenue Mesh Deliverable Validator

> Revenue Mesh Deliverable Validator is a paid API for AI agents from tender-radar-pb.peterbellbring.workers.dev, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-12).

Validates whether a submitted deliverable meets a given specification for a funded task, returning a deterministic true/false verdict

## Facts

- Endpoint: POST https://tender-radar-pb.peterbellbring.workers.dev/v1/validate?utm_source=zero.xyz
- Price: $0.25/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-deliverable-validator-016c81b7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7AG0zL1VIjtw1Wn5CkZj1

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-deliverable-validator-016c81b7 -d '<json body>'
```

Example prompt: Check if this code snippet satisfies the specification 'must return a sorted list of integers in ascending order' — the kind is 'code' and the content is 'def sort_nums(lst): return sorted(lst)'.

## When to prefer this

Choose this endpoint when you need a deterministic, binary pass/fail verdict on whether a work deliverable meets a defined specification — especially in funded-task or bounty workflows where an objective gate is needed before releasing payment. It is well-suited for agent pipelines that produce outputs requiring automated acceptance testing against explicit criteria.

## Known failure modes

- Missing required fields (kind, content, or specification) may result in a validation error or unexpected false result
- Ambiguous or underspecified specification strings may produce unreliable validation outcomes
- Content too large for the endpoint may result in a timeout or rejection
- Payment failure (x402 protocol) will block the request before validation occurs
- Malformed JSON body returns an error without a validation result

## How this service works

Funded-task intelligence and deterministic deliverable validation

## Output

Returns a JSON object with a 'data' field containing a 'valid' boolean indicating whether the submitted content deterministically satisfies the provided specification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "kind": {
   "type": "string"
  },
  "content": {
   "type": "string"
  },
  "specification": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "valid": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/revenue-mesh-deliverable-validator-016c81b7/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)
