# BountySignal Micro Evidence Check

> BountySignal Micro Evidence Check is a paid API for AI agents from bountysignal-radar.kwashi3345kaluwat2.chatgpt.site, paid per call via x402, $0.01/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.kwashi3345kaluwat2.chatgpt.site/api/x402/micro
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bountysignal-micro-evidence-check-0bf5348b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vpvgYy8ASVmieK7JQumbM

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-micro-evidence-check-0bf5348b -d '<json body>'
```

Example prompt: Before I spend time on this, can you run a BountySignal check on https://github.com/someorg/somerepo/issues/42 and tell me if it looks funded and open — give me the GO or NO-GO verdict?

## When to prefer this

Choose this endpoint when an AI agent or developer wants a fast, cheap ($0.01) pre-flight check on a specific bounty URL before investing meaningful build time. It is ideal for automated pipelines that process many bounty opportunities and need a binary GO/NO-GO signal to triage effort. Prefer it over manual review when speed and cost efficiency matter, and when signals like funding language, closed status, and identity friction are the key decision factors.

## Known failure modes

- Invalid or unreachable bounty URL returns an error or empty signals
- Bounty platform uses JavaScript-rendered content that cannot be scraped, resulting in inconclusive signals
- Private or auth-gated bounty pages may return no usable data
- Incorrect URL format triggers validation error
- Payment failure for the $0.01 USDC micro-payment results in 402 response and no analysis

## 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 bounty URL, a signals object with boolean flags for closedLanguageFound, fundingLanguageFound, and identityOrSocialFriction, a verdict string (e.g. 'GO' or 'NO-GO'), and a nextAction recommendation 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-micro-evidence-check-0bf5348b/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)