# Bounty Radar

> Static GitHub bounty intelligence feed for developers and coding agents.

Bounty Radar helps developers and coding agents shortlist GitHub issues with
public payout signals before investing time in a PR. It scores bounty/reward
keywords, Base/USDC/x402/MergeWork payment rail terms, amount-like text,
payout address hints, labels, repository quality, stale issue risk, and an
opportunity class with effort score for quick-win triage.

Live app: https://go165.github.io/bounty-radar/
Repository: https://github.com/go165/bounty-radar
Agent discovery: https://go165.github.io/bounty-radar/.well-known/agent.json

## Machine-Readable Endpoints

- JSON feed: https://go165.github.io/bounty-radar/feed/latest.json
- CSV feed: https://go165.github.io/bounty-radar/feed/latest.csv
- RSS feed: https://go165.github.io/bounty-radar/feed/latest.xml
- Manifest: https://go165.github.io/bounty-radar/feed/manifest.json
- JSON Schema: https://go165.github.io/bounty-radar/feed/schema.json

## Local Commands

```bash
npm test
npm run shortlist -- --min-score 50 --require-amount --require-rail --limit 10
npm run shortlist -- --min-score 30 --opportunity quick-win --max-effort-score 30 --limit 10
npm run shortlist -- --preset x402 --format json
npm run audit:shortlist -- --limit 8 --require-rail --min-amount-usd 50 --max-competition-score 40
node scripts/mcp-server.mjs
```

## Integration Notes

- Use `docs/agent-handoff.md` for endpoint contracts, a minimal consumer, CLI
  filters, and review rules.
- Use `examples/github-action-digest.yml` to publish a scheduled shortlist to a
  GitHub Actions job summary.
- Use `node scripts/mcp-server.mjs` to expose `search_bounties` and `get_bounty` as MCP stdio
  tools for agents that prefer tool calls over shell commands.
- Use `docs/claim-before-coding.md` and
  `examples/github-action-claim-before-coding.yml` to audit issue comments and
  related PRs before choosing bounty work.
- Use `examples/paid-alert-api` or `x402-paid-api-starter` to wrap the feed as a
  402-style paid alert API.
- Treat scores as triage hints. Verify payout terms, maintainer history,
  acceptance criteria, and payment rules manually before opening a PR.
- Do not use the feed for spam comments, bulk outreach, or misleading bounty
  claims.