# BountySignal Decision API

> BountySignal Decision API is a paid API for AI agents from bountysignal-radar-v2.minhtuan36zzz97948.chatgpt.site, paid per call via x402, $0.25/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 funded, open, and payable before a developer invests build time.

## Facts

- Endpoint: POST https://bountysignal-radar-v2.minhtuan36zzz97948.chatgpt.site/api/x402/decision
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bountysignal-decision-api-16aa7253
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iqzaXbY9xt_Aogb-shnTh

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-decision-api-16aa7253 -d '<json body>'
```

Example prompt: Before I start working on this, can you run a BountySignal check on https://github.com/example/repo/issues/42 to see if the bounty is actually funded and open — I want a GO or NO-GO before I invest any time.

## When to prefer this

Use this endpoint when an AI agent or developer needs a fast, low-cost pre-screen of a bounty before committing significant development effort. It is especially valuable in automated pipelines that process many bounties and need to filter for legitimacy and payability signals. Prefer this over manual review when speed and cost savings matter, and when a lightweight signal check (rather than deep audit) is sufficient to gate effort.

## Known failure modes

- Invalid or inaccessible bounty URL returns an error or inconclusive signals
- Bounty page behind authentication or paywalls cannot be scraped, leading to missing signals
- False positives on funding language if the page uses similar phrasing for closed bounties
- Payment failure or 402 response if USDC balance is insufficient
- Rate limiting or timeout if the target bounty URL is slow to respond

## 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 containing the target URL, a signals object with boolean flags for closedLanguageFound, fundingLanguageFound, and identityOrSocialFriction, a verdict string (e.g. 'GO' or 'NO-GO'), and a nextAction string with a human-readable recommendation on what to do before committing build effort.

## 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-decision-api-16aa7253/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)