# BountySignal Evidence Check

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

Analyzes a bounty URL or text to signal whether the bounty is legitimate and payable before a developer invests build time.

## Facts

- Endpoint: POST https://bountysignal-radar-v2.minhtuan36zzz97948.chatgpt.site/api/x402/hash
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bountysignal-evidence-check-0c586bbe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ew5gPuc1pR68QKHAtVrsU

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-check-0c586bbe -d '<json body>'
```

Example prompt: Before I start building, can you run a BountySignal check on this bounty listing to tell me if it's actually funded and open — here's the text: 'We are offering $5,000 for a working exploit on our login flow, payable in USDC upon verified submission.'

## When to prefer this

Use this endpoint when an AI agent or developer needs a fast, cheap pre-screening signal on a bounty or grant listing before investing significant build or research time. It is particularly valuable in automated pipelines where agents are scanning many bounties and need a programmatic GO/NO-GO filter. Prefer it over manual review when speed and cost efficiency matter, and over generic LLM analysis when you want structured, consistent signal fields rather than free-form opinion.

## Known failure modes

- Missing or invalid 'text' field returns a validation error
- Algo field must be exactly 'sha256' — any other value is rejected
- Empty or very short text may produce low-confidence or inconclusive signals
- Network timeout on the x402 payment layer can prevent the call from completing
- If the bounty page is paywalled or dynamic, the raw text may be incomplete and produce misleading results

## 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 containing boolean flags (closedLanguageFound, fundingLanguageFound, identityOrSocialFriction), a verdict string (e.g. GO or NO-GO), and a nextAction string recommending what the developer should do next before committing effort.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "algo": {
   "type": "string",
   "const": "sha256"
  },
  "text": {
   "type": "string"
  }
 }
}
```

## 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-check-0c586bbe/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)