# Revenue Mesh Claimability Check

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

Determines whether a funded task or deliverable is eligible to be claimed, given a URL and canonical key

## Facts

- Endpoint: POST https://tender-radar-pb.peterbellbring.workers.dev/v1/claimability?utm_source=zero.xyz
- Price: $0.5/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-claimability-check-3c138980
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iUizldLS-qT-jOd5dh8mL

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-claimability-check-3c138980 -d '<json body>'
```

Example prompt: Can you check whether the deliverable at https://example.com/submission is eligible to be claimed using the canonical key 'task-abc-123'?

## When to prefer this

Use this endpoint when you need to programmatically verify whether a specific deliverable URL qualifies for a funded-task claim before attempting to execute the claim. It is particularly suited for automated pipelines that must gate claim actions on deterministic eligibility decisions, avoiding wasted claim attempts or payment failures.

## Known failure modes

- Invalid or missing URL returns an error or non-eligible decision
- Unknown canonical key results in ineligible or not-found response
- Network timeout from the worker endpoint
- Malformed input schema causes rejection
- Task already claimed may return ineligible decision

## How this service works

Funded-task intelligence and deterministic deliverable validation

## Output

Returns a JSON object containing a 'data' field with a 'decision' property indicating whether the task or deliverable is eligible (e.g. 'eligible') for claiming based on the provided URL and canonical key.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "decision": "eligible"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/revenue-mesh-claimability-check-3c138980/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)