# Kairo Bounty Scan API

> Kairo Bounty Scan API is a paid API for AI agents from kairo-x402.kairo-ships.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-13).

Scans a GitHub repository (and optionally a specific issue) for bounty risk signals, determining if a crypto bounty is safe to attempt and collectable.

## Facts

- Endpoint: GET https://kairo-x402.kairo-ships.workers.dev/api/bounty-scan
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kairo-bounty-scan-api-9e37632b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WFGzQ1aK1nstsn9BA78UD

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 kairo-bounty-scan-api-9e37632b
```

Example prompt: Can you scan the repo owner/repo-name on GitHub — specifically issue #15 — and tell me whether the crypto bounty there is safe to attempt and actually collectable?

## When to prefer this

Choose this endpoint when an AI agent or developer needs to quickly vet a GitHub-hosted crypto bounty before investing time in it — especially in crypto-native workflows where no account signup or KYC is feasible and pay-per-call via x402/USDC on Base is preferred. It is specifically designed for bounty risk classification, not general code analysis or vulnerability scanning.

## Known failure modes

- Missing or invalid 'repo' parameter (owner/name format required) returns an error
- Non-existent GitHub repository causes a failed lookup
- Issue number provided does not exist in the specified repo
- Rate limiting or upstream GitHub API unavailability
- Payment failure or x402 protocol error prevents the call from completing

## How this service works

Crypto-native ($0.02 USDC on Base, x402) utility endpoints for agents. No accounts, no KYC — pay-per-call.

## Output

Returns a JSON object with the repo name, risk level (clean/low/medium/high/critical), whether the bounty is crypto-collectable, a safe_to_attempt boolean, the issue number and star count (if available), an array of specific findings explaining any risk signals, and an optional note.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "repo"
 ],
 "properties": {
  "repo": {
   "type": "string",
   "description": "owner/name"
  },
  "issue": {
   "type": "integer"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "repo",
  "risk",
  "crypto_collectable",
  "safe_to_attempt",
  "findings"
 ],
 "properties": {
  "note": {
   "type": "string"
  },
  "repo": {
   "type": "string"
  },
  "risk": {
   "enum": [
    "clean",
    "low",
    "medium",
    "high",
    "critical"
   ],
   "type": "string"
  },
  "issue": {
   "type": [
    "integer",
    "null"
   ]
  },
  "stars": {
   "type": [
    "integer",
    "null"
   ]
  },
  "findings": {
   "type": "array",
   "items": {
    "type": "object"
   }
  },
  "safe_to_attempt": {
   "type": "boolean"
  },
  "crypto_collectable": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kairo-bounty-scan-api-9e37632b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from kairo-x402.kairo-ships.workers.dev](https://www.zero.xyz/host/kairo-x402.kairo-ships.workers.dev/llms.txt)