# BountySignal Brief — Bounty Viability Evidence Check

> BountySignal Brief — Bounty Viability Evidence 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-14).

Analyzes a bounty URL and returns 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/brief
- Price: $5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bountysignal-brief-bounty-viability-evidence-check-9cc6fb05
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aS5SyHMb_WJkvEYPWnuvl

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-brief-bounty-viability-evidence-check-9cc6fb05 -d '<json body>'
```

Example prompt: Before I spend time building, can you run a BountySignal check on this bounty — https://github.com/some-org/some-repo/issues/42 — and tell me if it's actually funded and open?

## When to prefer this

Use this endpoint when a developer or AI agent needs a fast, cheap pre-screening signal before investing significant build time on a bounty. It is ideal for automating bounty triage pipelines, filtering lists of bounties for quality, or validating a single bounty URL on demand. Prefer this over manual review when speed and consistency matter, and when the cost of false starts (wasted build effort) exceeds $5.

## Known failure modes

- Bounty URL is inaccessible or returns a non-200 status — analysis cannot proceed
- URL points to a non-bounty page — signals may be unreliable or empty
- Funding language is ambiguous — verdict may be inconclusive
- Page content is behind a login wall — signals will reflect only publicly visible text
- Malformed or non-URI input — request is rejected with a validation error

## 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 was detected, whether funding language was found, and whether identity or social friction exists, plus a high-level verdict (e.g. 'GO' or 'NO-GO') and a recommended next action the developer should take.

## 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-brief-bounty-viability-evidence-check-9cc6fb05/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)