# BRAINIAC Restaking Risk Exit Window Analyzer

> BRAINIAC Restaking Risk Exit Window Analyzer is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-13).

Computes the exit feasibility score and time buffer for safely exiting a restaking position given unbonding delays, withdrawal delays, and upcoming slash events.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/restaking-risk/exit-window?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-restaking-risk-exit-window-analyzer-3b7c557d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__8Em3mu92zsvuqqutESTj

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 brainiac-restaking-risk-exit-window-analyzer-3b7c557d -d '<json body>'
```

Example prompt: I have a restaking position on EigenLayer with a slash event coming in 48 hours — my unbonding period is 72 hours and my withdrawal delay is 24 hours. What's my exit feasibility score and how many hours of buffer do I actually have?

## When to prefer this

Use this endpoint when an AI agent or DeFi risk system needs to quantify whether a restaking position can be safely exited before one or more slash events, factoring in both unbonding and withdrawal delays. It is specifically designed for restaking risk scenarios (e.g. EigenLayer, Symbiotic, Karak) rather than generic staking or lending protocols. Prefer this over manual calculation when multiple slash events on different networks need to be evaluated simultaneously.

## Known failure modes

- Missing required `events` array or `hours_until_slash` field returns a validation error
- Providing 0 or negative `hours_until_slash` violates the exclusiveMinimum constraint and is rejected
- Providing more than 20 events in the array exceeds `maxItems` and fails validation
- Network name exceeding 80 characters is rejected
- Unbonding or withdrawal delay exceeding 8760 hours (1 year) is rejected
- Payment failure via x402 results in a 402 response and no computation

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object with two fields: `time_buffer_hours` (integer representing how many hours of buffer exist between when an exit could complete and the earliest slash event) and `exit_feasibility_score` (integer 0–100 indicating how feasible a safe exit is, where higher is safer).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "events": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "network",
     "hours_until_slash"
    ],
    "properties": {
     "network": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "hours_until_slash": {
      "type": "integer",
      "maximum": 8760,
      "exclusiveMinimum": 0
     }
    },
    "additionalProperties": false
   },
   "maxItems": 20,
   "minItems": 1
  },
  "unbonding_hours": {
   "type": "integer",
   "maximum": 8760,
   "minimum": 0
  },
  "withdrawal_delay_hours": {
   "type": "integer",
   "maximum": 8760,
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "time_buffer_hours": 30,
  "exit_feasibility_score": 42
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-restaking-risk-exit-window-analyzer-3b7c557d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
