# BountyVerifier API

> BountyVerifier API is a paid API for AI agents from bounty-verifier-api.planet-teacher.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-10).

Verifies public GitHub bounty issues with evidence-backed analysis, returning a verdict, reward amount, and funding confidence level.

## Facts

- Endpoint: POST https://bounty-verifier-api.planet-teacher.workers.dev/verify?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bountyverifier-api-f30728aa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tXC4g15FriYqKRDJV4sZa

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 bountyverifier-api-f30728aa -d '<json body>'
```

Example prompt: Can you verify whether this GitHub bounty issue is legit and worth pursuing? Here's the link: https://github.com/owner/repo/issues/123 — I want to know the reward amount and how confident we should be that it's actually funded.

## When to prefer this

Use this endpoint when an agent or developer needs a quick, evidence-backed assessment of whether a GitHub bounty issue is worth pursuing, including reward size and funding credibility. It is the right choice when you want a structured verdict rather than raw issue text, and when you need to programmatically screen multiple bounties. Prefer it over manually reading GitHub issues when speed or automation is required.

## Known failure modes

- Invalid or inaccessible GitHub issue URL — returns an error if the URL cannot be resolved or the issue is private
- Issue has no bounty label or reward information — may return a low-confidence or null verdict
- GitHub rate limiting or API unavailability — upstream fetch failure could result in an error response
- Stale bounty data — funding status may not reflect real-time changes to the issue
- Ambiguous reward denominations — issues listing rewards in non-standard currencies may return uncertain amounts

## How this service works

Evidence-backed verification of public GitHub bounty issues for agents and developers.

## Output

A JSON object containing the bounty reward amount and currency (e.g. 20 USDC), a verdict recommending whether to pursue the issue, the original GitHub issue URL, and a funding confidence level (e.g. 'stated_not_verified') indicating how trustworthy the bounty claim is.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "reward": {
   "amount": 20,
   "currency": "USDC"
  },
  "verdict": "pursue",
  "sourceUrl": "https://github.com/owner/repo/issues/123",
  "fundingConfidence": "stated_not_verified"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bountyverifier-api-f30728aa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bounty-verifier-api.planet-teacher.workers.dev](https://www.zero.xyz/host/bounty-verifier-api.planet-teacher.workers.dev/llms.txt)