# BountyDueDiligence

> BountyDueDiligence is a paid API for AI agents from bounty-due-diligence.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Analyzes a GitHub bounty issue for competition, staleness, maintainer inactivity, and payout risk before an autonomous agent invests compute in an implementation.

## Facts

- Endpoint: POST https://bounty-due-diligence.vercel.app/v1/analyze
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bountyduediligence-5d954caa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_10Zrj1ll7k16jIGM9Khxq

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 bountyduediligence-5d954caa -d '<json body>'
```

Example prompt: Before I start coding, can you run a due-diligence check on this GitHub bounty issue — https://github.com/org/repo/issues/123 — and tell me if it's worth pursuing or if there are already competing PRs and too much risk?

## When to prefer this

Use this endpoint when an autonomous coding agent needs to decide whether to invest compute in implementing a solution for a GitHub bounty issue. It is specifically designed for the pre-flight, before-coding stage — not for general GitHub issue search or code review. Prefer it over manual inspection when running at scale across many bounty issues, or when compute cost per attempt is meaningful and you want to filter out lost causes early.

## Known failure modes

- Invalid or non-public GitHub issue URL returns an error
- Issue has no associated bounty or reward — reward fields may be null or confidence 'low'
- Rate limiting if many calls are made in rapid succession
- Payment not received or insufficient USDC causes a 402 response
- Repository is private and inaccessible — analysis cannot be completed
- GitHub API rate limits may cause transient failures or incomplete data

## How this service works

Pre-flight due diligence for GitHub bounty issues: competing PRs, staleness, maintainer inactivity, saturation and payout-risk signals, before an autonomous coding agent spends compute on implementation.

## Output

Returns a structured JSON object with a verdict (e.g. NO_GO or GO), an overall winnability score (0-100), a list of reasons, the count and URLs of competing/closing PRs, the issue state and number, the advertised reward amount, reward confidence level, and the repository identifier. The full paid response includes complete competition detail, repo activity metrics, and granular risk signals.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "issue_url": {
   "type": "string",
   "format": "uri",
   "description": "A public GitHub issue URL"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "note": "This is a truncated example. The paid response includes full competition detail, repo activity, and risk signals.",
  "decision": {
   "reasons": [
    "...full reasoning in the paid response..."
   ],
   "verdict": "NO_GO",
   "overall_winnability_score": 12
  },
  "repository": "org/repo",
  "competition": {
   "exact_closing_prs": [
    "...one or more PRs already claim this..."
   ],
   "competing_pr_count": 2
  },
  "issue_state": "open",
  "issue_number": 123,
  "advertised_reward": 90,
  "reward_confidence": "high"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bountyduediligence-5d954caa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bounty-due-diligence.vercel.app](https://www.zero.xyz/host/bounty-due-diligence.vercel.app/llms.txt)