# BountySignal Evidence-First Check

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

Analyzes a bounty URL for funding signals, closed/open status, and identity friction to return a GO/NO-GO verdict before a developer invests build time.

## Facts

- Endpoint: POST https://bountysignal-radar.kwashi3345kaluwat2.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-evidence-first-check-3bafbe9c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-mDeL4GYkRivehyj3X8NU

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-first-check-3bafbe9c -d '<json body>'
```

Example prompt: Before I spend time on this, can you run a BountySignal check on https://hackerone.com/reports/example-bounty to see if it's still open, actually funded, and doesn't require any social friction — so I know if it's a GO?

## When to prefer this

Use this endpoint when a developer or AI agent needs a cheap, fast pre-flight check on a bounty opportunity before committing significant build time. It is purpose-built for bounty viability screening — not general web scraping or generic page analysis — and costs only $5 to avoid wasting hours on a dead or fraudulent listing. Prefer it over manual review when automating a bounty discovery pipeline or processing many bounty URLs at scale.

## Known failure modes

- Invalid or unreachable bounty URL returns an error or inconclusive result
- Bounty page behind authentication may not yield meaningful signals
- Payment failure (insufficient USDC balance or x402 protocol error) blocks the call
- False positives if bounty page uses ambiguous language that resembles closed/funding keywords
- Rate limiting or network timeouts on the target URL crawl

## 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 bounty target URL, a signals object with three boolean fields (closedLanguageFound, fundingLanguageFound, identityOrSocialFriction), a verdict string (e.g. 'GO' or 'NO-GO'), and a nextAction string advising what to do before proceeding.

## 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-first-check-3bafbe9c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bountysignal-radar.kwashi3345kaluwat2.chatgpt.site](https://www.zero.xyz/host/bountysignal-radar.kwashi3345kaluwat2.chatgpt.site/llms.txt)