# BountySignal Evidence Check

> BountySignal Evidence Check is a paid API for AI agents from bountysignal-radar-v2.minhtuan36zzz97948.chatgpt.site, paid per call via x402, $1/call, status unknown (last checked 2026-09-15).

Analyzes a bounty URL and returns a GO/NO-GO verdict with signals indicating whether the bounty is real, funded, and payable before a developer invests build time.

## Facts

- Endpoint: POST https://bountysignal-radar-v2.minhtuan36zzz97948.chatgpt.site/api/x402/standard
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bountysignal-evidence-check-9e97b550
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xK1ZQz1Yg09UtLmufLSU7

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 bountysignal-evidence-check-9e97b550 -d '<json body>'
```

Example prompt: Before I start coding, can you run a BountySignal check on this bounty — https://example.com/bounty — and tell me if it's actually funded and worth pursuing?

## When to prefer this

Use this endpoint when a developer or AI agent needs a fast, low-cost pre-qualification check on a bounty URL before investing meaningful build time. It is especially valuable in automated bounty-hunting pipelines where agents need to triage large numbers of bounties without manual review. Prefer this over manual inspection when speed and cost-efficiency matter, and when you need a structured, machine-readable verdict rather than raw page content.

## Known failure modes

- Invalid or unreachable bounty URL returns an error or empty signals
- Paywalled or login-gated bounty pages may not yield meaningful signals
- False GO verdicts on poorly-structured bounty pages that happen to contain funding language
- Missing funding signals on legitimate bounties hosted on unusual platforms
- Payment failure (x402) if USDC balance is insufficient

## How this service works

A $5 evidence-first check that tells developers and AI agents whether a bounty can actually pay before they build.

## Output

Returns a JSON object with the target URL, a signals object indicating whether closed language, funding language, or identity/social friction was detected, a GO or NO-GO verdict, and a recommended next action string to guide the developer's follow-up steps.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "bounty_url": {
   "type": "string",
   "format": "uri"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "target": "https://example.com/bounty",
  "signals": {
   "closedLanguageFound": false,
   "fundingLanguageFound": true,
   "identityOrSocialFriction": false
  },
  "verdict": "GO",
  "nextAction": "Confirm the sponsor and payout rail manually before investing build time."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bountysignal-evidence-check-9e97b550/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bountysignal-radar-v2.minhtuan36zzz97948.chatgpt.site](https://www.zero.xyz/host/bountysignal-radar-v2.minhtuan36zzz97948.chatgpt.site/llms.txt)