# BountySignal Starter — Bounty Viability Check

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

Analyzes a bounty URL and returns signals indicating whether the bounty is likely to pay out, delivering a GO/NO-GO verdict before a developer invests build time.

## Facts

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

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

Example prompt: Before I spend a week on this, can you check whether this bounty at https://example.com/bounty/123 is actually funded and likely to pay — give me a GO or NO-GO verdict?

## When to prefer this

Use this endpoint when an agent or developer needs a quick, low-cost ($5) pre-flight check on a bounty before committing engineering effort. It is best suited for filtering open-source, crypto, or developer bounty listings for payment viability signals. Prefer it over manual review when processing multiple bounties autonomously or when time-to-decision matters.

## Known failure modes

- Invalid or unreachable bounty URL returns an error or indeterminate verdict
- Bounty page behind authentication may not be scrapeable, yielding incomplete signals
- False positives/negatives if bounty language is ambiguous or non-standard
- Payment failure (x402) if USDC balance is insufficient
- Duplicate sibling endpoints on the domain may indicate an unstable or test deployment

## 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 bounty URL, a signals object containing boolean flags (closedLanguageFound, fundingLanguageFound, identityOrSocialFriction), a verdict string (e.g. 'GO'), and a nextAction string recommending what the developer or agent should do next.

## 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-starter-bounty-viability-check-9f286e15/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)