# BountyVerdict GitHub Issue Preflight Check

> BountyVerdict GitHub Issue Preflight Check is a paid API for AI agents from bountyverdict-agent-production.mimirslab.workers.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Analyzes a public GitHub issue URL and returns AVOID, CAUTION, or VIABLE verdict with evidence before an agent invests effort coding a bounty fix.

## Facts

- Endpoint: POST https://bountyverdict-agent-production.mimirslab.workers.dev/api/verdict
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bountyverdict-github-issue-preflight-check-c401d7fc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9C7xMCWPdJsF8P0IgCEpJ

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 bountyverdict-github-issue-preflight-check-c401d7fc -d '<json body>'
```

Example prompt: Before I start coding, check if this GitHub bounty is still worth pursuing: https://github.com/some-org/some-repo/issues/42 — I want to know if it's VIABLE, CAUTION, or AVOID, and whether the repo allows AI contributions.

## When to prefer this

Use this endpoint when an AI agent is about to begin coding work on a GitHub bounty issue and needs to quickly determine whether the issue is still open, unclaimed, reward-bearing, and AI-contribution-friendly — before wasting compute and developer time. Prefer this over manually reading GitHub threads when you need a structured AVOID/CAUTION/VIABLE signal with evidence. Use the sibling comparison endpoint instead when you have multiple bounty candidates to rank.

## Known failure modes

- Invalid or non-public GitHub issue URL returns a 400 or validation error
- GitHub rate limit exhausted returns reduced coverage or error
- Issue URL points to a private repository — returns inaccessible error
- Network timeout reaching GitHub API — returns partial result or error
- Malformed issue URL that doesn't match required pattern returns schema validation failure

## Output

Returns a JSON object with a verdict (AVOID, CAUTION, or VIABLE), a numeric score from 0–100, a summary sentence, an array of signals (each with label, impact, hard_stop flag, and evidence URL), issue metadata (title, state, repository), contribution policy coverage, and scan coverage stats (comments scanned, timeline events, linked PRs found, policy documents scanned, GitHub rate limit remaining), plus a checked_at timestamp.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bountyverdict-github-issue-preflight-check-c401d7fc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bountyverdict-agent-production.mimirslab.workers.dev](https://www.zero.xyz/host/bountyverdict-agent-production.mimirslab.workers.dev/llms.txt)