# Blinka Rescue Signal

> Blinka Rescue Signal is a paid API for AI agents from blinka-machine-mouths.netlify.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-11).

Analyzes a failed or stalled agent run log to identify the primary blocker, detect retry traps, and recommend the smallest corrective next step.

## Facts

- Endpoint: POST https://blinka-machine-mouths.netlify.app/rescue-signal?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blinka-rescue-signal-a959cc00
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2NU4zjEs8-YdMdirZOKT4

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 blinka-rescue-signal-a959cc00 -d '<json body>'
```

Example prompt: My agent run just failed — the goal was to deploy the app to staging, and here's the last 3,000 characters of the run log: [paste log]. Can you triage what's blocking it, tell me if it's stuck in a retry trap, and suggest the smallest fix to try next?

## When to prefer this

Choose this endpoint when an automated run, pipeline, or agent task has failed or stalled and you need a fast, cheap first-pass triage without spinning up a full debugging session. It is ideal for detecting retry traps and surfacing evidence-backed blockers from short log excerpts before investing in deeper investigation. Prefer it over general-purpose LLM calls when you want a structured JSON response with specific fields (blocker, retry trap, next step, artifact review flag) at $0.005 per call.

## Known failure modes

- run_log exceeds 3,500 characters — truncate before submitting
- Insufficient log detail — low confidence score returned with vague blocker
- Goal field missing or too ambiguous — blocker analysis may be off-target
- Malformed JSON input — returns error response
- Log contains no actionable signal — endpoint may return low confidence with no clear blocker

## How this service works

Bounded stateless machine services plus public procurement discovery. No private Mika memory or arbitrary tool execution.

## Output

Returns a JSON object with: ok (bool), status string, the primary blocker with textual evidence from the log, a retry_trap boolean indicating if the run is looping uselessly, a next_state_change string describing the smallest corrective action, a needs_artifact_review boolean, a confidence score (0–1), and a retained flag (always false — no data is stored).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "goal": {
   "type": "string",
   "description": "The bounded task the run was trying to accomplish."
  },
  "run_log": {
   "type": "string",
   "description": "Short failed/stalled run excerpt. Max 3,500 characters."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "status": "blocked",
  "service": "blinka-rescue-signal",
  "evidence": "Deploy failed with TypeError",
  "retained": false,
  "confidence": 0.93,
  "retry_trap": true,
  "primary_blocker": "The deploy step is failing with TypeError.",
  "next_state_change": "Inspect or change the failing deploy code/config before retrying.",
  "needs_artifact_review": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blinka-rescue-signal-a959cc00/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from blinka-machine-mouths.netlify.app](https://www.zero.xyz/host/blinka-machine-mouths.netlify.app/llms.txt)