# Bounty Claimability API – Batch Audit

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

Audits up to 10 GitHub issue URLs in one call and returns a claimability score and verdict for each bounty.

## Facts

- Endpoint: GET https://bounty-claimability-api.vercel.app/api/audit-batch
- Price: $7.99/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bounty-claimability-api-batch-audit-2c109329
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QpQUqrrcymy1fRYzFpYXy

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-batch-audit-2c109329
```

Example prompt: Can you audit these three GitHub issue bounties and tell me which ones are actually claimable? https://github.com/org/repo/issues/42, https://github.com/org/repo/issues/57, https://github.com/org/repo/issues/88

## When to prefer this

Use this endpoint when you need structured, scored due diligence on GitHub issue bounties before committing developer time or funds. It is especially valuable for batch pre-screening (up to 10 at once) in automated bounty-hunting pipelines, compared to manually reviewing each issue. Prefer it over generic GitHub API calls when you need an opinionated claimability verdict rather than raw issue metadata.

## Known failure modes

- Empty or missing 'urls' array returns a validation error
- More than 10 URLs in a single request exceeds the maxItems limit and is rejected
- Non-GitHub or private/inaccessible issue URLs may return ok:false or low scores
- Payment failure via x402 protocol prevents the audit from running
- Malformed URLs cause parsing errors in the batch

## How this service works

Paid x402 due diligence for GitHub bounties.

## Output

Returns a JSON object with a count of audited issues and a results array. Each element includes an 'ok' boolean and an 'audit' object containing a numeric score (0–100) and a string verdict (e.g. 'good') indicating how claimable the bounty is.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "urls": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 10,
   "minItems": 1,
   "description": "1-10 public GitHub issue URLs"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 1,
  "results": [
   {
    "ok": true,
    "audit": {
     "score": 84,
     "verdict": "good"
    }
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-claimability-api-batch-audit-2c109329/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)