# Bounty Claimability API

> Bounty Claimability API is a paid API for AI agents from bounty-claimability-api.vercel.app, paid per call via x402, $0.99/call, status unknown (last checked 2026-09-16).

Audits a public GitHub issue URL to assess whether a posted bounty is legitimately claimable, returning a risk score, verdict, and recommendation.

## Facts

- Endpoint: GET https://bounty-claimability-api.vercel.app/api/audit
- Price: $0.99/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bounty-claimability-api-3595da60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RnoEM9kN7BNqNQ8UAeaOo

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 bounty-claimability-api-3595da60
```

Example prompt: Before I start working on this GitHub issue, can you audit it for bounty claimability and tell me the risk score, verdict, and whether the $100 payout is realistic? Here's the URL: https://github.com/some-org/some-repo/issues/42

## When to prefer this

Use this endpoint when an agent or user needs structured, scored due diligence on a specific GitHub bounty before committing development time — especially when payout legitimacy, claimability conditions, or risk factors are unclear. Prefer this over manual inspection when speed and a consistent scoring rubric matter.

## Known failure modes

- Invalid or non-public GitHub issue URL returns an error
- Issue has no bounty label or reward information, resulting in low score or null reward
- GitHub rate limits or access restrictions block the audit
- Bounty details are ambiguous, producing a low-confidence score with cautionary recommendation
- Network timeout from Vercel cold start

## How this service works

Paid x402 due diligence for GitHub bounties.

## Output

A JSON object containing a list of identified risks, a numeric claimability score (0–100), a verdict string (e.g. 'viable'), a plain-English recommendation, and the advertised reward amount in USD.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "Public GitHub issue URL to audit for bounty claimability"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "risks": [],
  "score": 72,
  "verdict": "viable",
  "recommendation": "Plausible target; verify payout rules.",
  "advertisedRewardUsd": 100
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-claimability-api-3595da60/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bounty-claimability-api.vercel.app](https://www.zero.xyz/host/bounty-claimability-api.vercel.app/llms.txt)
