# Blinka Rescue Pro

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

Analyzes a failed or stalled AI agent run and returns a structured recovery plan with root-cause findings, blockers, artifact review, and the smallest authorized next action for handoff.

## Facts

- Endpoint: POST https://blinka-machine-mouths.netlify.app/rescue-pro?utm_source=zero.xyz
- Price: $3/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-pro-62c96c93
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yXCLJZjaJDNaxII1K7q0T

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-pro-62c96c93 -d '<json body>'
```

Example prompt: My deploy agent just crashed — the goal was to build and deploy the service, here's the run log showing a TypeError in the deploy helper, and here's the helper code as a Python artifact. Can you diagnose what went wrong, review the code, and tell me the single smallest next action the next agent should take, given it has access to edit_file and run_tests?

## When to prefer this

Choose this endpoint when an AI agent run has failed, stalled, or looped and you need a structured, evidence-grounded recovery plan rather than a simple retry. It is especially valuable when you have a run log plus a code or config artifact to review together, and when you need a safe handoff contract specifying exactly which tools the next agent is authorized to use. Prefer this over cheaper triage endpoints (like Blinka Rescue Signal) when you need full artifact static analysis, a detailed repair sequence, and a formal continuation contract with authority boundaries.

## Known failure modes

- Missing or empty run_log may result in low-confidence recovery with no actionable findings
- Artifact too large or malformed may cause artifact review to be skipped or truncated
- Incorrect artifact_kind enum causes wrong review path (code vs text analysis)
- Tool names in available_tools that don't match exact names may produce unauthorized tool recommendations
- Ambiguous or very short goal description reduces precision of blocker identification
- Non-Python code artifacts receive weaker static analysis than Python artifacts

## 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 containing: an overall recovery status (continue/blocked/done), a list of priority findings and evidence-backed blockers, a step-by-step repair sequence, the single smallest recommended next action (with tool name and reason), a structured artifact review (issues, suggestions, confidence, executed=false), a continuation handoff contract specifying allowed tools and authority boundaries, and a confidence score for the recovery assessment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "goal": {
   "type": "string",
   "description": "The bounded task the failed run was trying to accomplish."
  },
  "run_log": {
   "type": "string",
   "description": "Transcript, tool results, errors, or state summary from the failed/stalled run."
  },
  "artifact": {
   "type": "string",
   "description": "Optional code, config, diff, or text artifact related to the failure. It is reviewed but never executed."
  },
  "language": {
   "type": "string",
   "description": "Programming language hint for code artifacts; currently Python receives the strongest static checks."
  },
  "constraints": {
   "type": "string",
   "description": "Optional hard constraints such as read-only, no-network, or do-not-touch paths."
  },
  "artifact_kind": {
   "enum": [
    "code",
    "text"
   ],
   "type": "string",
   "description": "How the artifact should be reviewed."
  },
  "artifact_intent": {
   "type": "string",
   "description": "What the artifact is supposed to do or communicate; defaults to goal."
  },
  "available_tools": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "Exact tool names the next agent is allowed to use."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "handoff": {
   "status": "continue",
   "unknowns": [],
   "allowed_tools": [
    "edit_file",
    "run_tests",
    "request_user_input"
   ],
   "do_not_repeat": [
    "Rerun the unchanged failing deploy helper."
   ],
   "smallest_next_action": {
    "kind": "tool_call",
    "tool": "edit_file",
    "reason": "Correct the identified helper defect before rerunning deployment.",
    "arguments": {}
   }
  },
  "service": "blinka-rescue-pro",
  "recovery": {
   "ok": true,
   "status": "continue",
   "blockers": [
    {
     "item": "The deploy helper crashes.",
     "evidence": "Deploy helper crashed with TypeError"
    }
   ],
   "retained": false,
   "unknowns": [],
   "completed": [
    "Build completed."
   ],
   "confidence": 0.92,
   "next_action": {
    "kind": "tool_call",
    "tool": "edit_file",
    "reason": "Correct the identified helper defect before rerunning deployment.",
    "arguments": {}
   },
   "do_not_repeat": [
    "Rerun the unchanged failing deploy helper."
   ],
   "state_summary": "The build completed; the deploy helper is the failing stage.",
   "continuation_contract": {
    "schema": "blinka-continuation-handoff.v1",
    "retained": false,
    "allowed_tools": [
     "edit_file",
     "run_tests",
     "request_user_input"
    ],
    "evidence_scope": [
     "goal",
     "run_log",
     "constraints",
     "available_tools"
    ],
    "authority_source": "caller_supplied_available_tools",
    "identity_verdict": null,
    "unknowns_preserved": true,
    "research_enrollment": false,
    "state_claims_source": "caller_supplied_evidence_only",
    "continuation_executed": false,
    "permission_non_inheritance": true,
    "next_action_tool_authorized": true,
    "authority_inherited_from_failed_run": false
   }
  },
  "retained": false,
  "confidence": 0.92,
  "artifact_review": {
   "kind": "code",
   "intent": "A stateless deployment helper that does not leak state between calls.",
   "issues": [],
   "passed": false,
   "executed": false,
   "confidence": 0.96,
   "suggestions": []
  },
  "repair_sequence": [
   "Use None as the default and allocate a new container inside the function.",
   "Correct the identified helper defect before rerunning deployment."
  ],
  "priority_findings": [
   "Workflow blocker: The deploy helper crashes.",
   "Artifact HIGH: Mutable default argument is shared across calls and can accumulate state unexpectedly."
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blinka-rescue-pro-62c96c93/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)