# BountySignal Bounty Viability Check

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

Analyzes a bounty URL for evidence signals (funding language, closed status, identity friction) and returns a GO/NO-GO verdict before a developer invests build time.

## Facts

- Endpoint: POST https://bountysignal-radar-v2.minhtuan36zzz97948.chatgpt.site/api/x402/micro
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bountysignal-bounty-viability-check-c90f5aa2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gUbrShPFBzsC4vB7xKcyA

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-bounty-viability-check-c90f5aa2 -d '<json body>'
```

Example prompt: Before I spend time on it, check whether this bounty is actually funded and still open: https://example.com/bounty/1234 — give me a GO or NO-GO verdict.

## When to prefer this

Choose this endpoint when an agent or developer needs a fast, cheap pre-flight check on a bounty URL before investing engineering effort. Ideal for automated bounty pipelines that need to filter large lists of opportunities, or for individual developers who want a quick GO/NO-GO signal without manually reading each bounty page. Prefer this over manual review when speed and cost matter, and over general web scrapers when you need bounty-specific signal interpretation (funded, closed, friction).

## Known failure modes

- Invalid or unreachable bounty URL returns an error or empty signals
- Bounty page behind authentication may not be scrapeable, resulting in inconclusive signals
- False negatives if funding language is obscured or non-standard
- False positives if closed language appears in comments rather than the bounty itself
- Network timeouts on slow or rate-limited bounty platforms

## 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 original target URL, a signals object indicating whether closed language, funding language, or identity/social friction was detected on the page, a GO or NO-GO verdict string, and a nextAction recommendation string advising what to do before investing build time.

## 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-bounty-viability-check-c90f5aa2/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)