Score exit timing before a slash API
Subtract the unbonding time and the withdrawal delay from the soonest caller-supplied slash horizon. The buffer is that remainder in hours. The feasibility score is the buffer divided by the soonest horizon, and it is zero when the buffer is negative. No queue is read from a network.
The Score exit timing before a slash operation is part of the Cross Network Slashing Exposure API on BRAINIAC.software. Subtract the unbonding time and the withdrawal delay from the soonest caller-supplied slash horizon. The buffer is that remainder in hours. The feasibility score is the buffer divided by the soonest horizon, and it is zero when the buffer is negative. No queue is read from a network. It is exposed as POST /api/v1/restaking-risk/exit-window and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied vault, collateral, and slashing records processed locally Caller-supplied slashing window durations processed locally Limitations: Amounts are integers in the caller-supplied unit. No balance is fetched. The same underlying collateral is counted once. Gross exposure counts each allocation. A reuse group is shared backing only when the request says those allocations list the same units. Simultaneous losses are capped at 100% of a shared slice. Sequential losses use the balance left by earlier events. Prices and conversion rates are used only when supplied. No price is invented. A modeled loss is not proof that a slash occurred. A slashing window fit is arithmetic on the supplied durations. It does not show that a network will finish the process in time. slashing-correlation caps each operator at 100 percent of its own stake. The correlation score is the share of stake listed on more than one network. exit-window uses the soonest supplied slash horizon. A negative buffer scores zero feasibility. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Calculate cross-network slashing exposure, Score cross-network slashing correlation, Check slashing window feasibility. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/restaking-risk/exit-windowExample request
curl -i -X POST "https://www.brainiac.software/api/v1/restaking-risk/exit-window" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"unbonding_hours": 24,
"withdrawal_delay_hours": 18,
"events": [
{
"network": "eigenlayer",
"hours_until_slash": 72
},
{
"network": "symbiotic",
"hours_until_slash": 96
}
]
}
JSONAn unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.
FAQ
- Do I need an API key? No. Pay the listed USDC amount with x402.
- What network? Base (eip155:8453), USDC.
- Is this an official determination? No. Results are for human review against the cited sources.
Related operations
- Calculate cross-network slashing exposure — $0.05 USDC
- Score cross-network slashing correlation — $0.04 USDC
- Check slashing window feasibility — $0.05 USDC