Score cross-network slashing correlation API

Cap each operator's network weights at 100 percent of its stake, then weight that exposure by stake. The correlation score is the share of stake that sits on more than one network. Weights are the caller's risk weights. No stake is fetched.

The Score cross-network slashing correlation operation is part of the Cross Network Slashing Exposure API on BRAINIAC.software. Cap each operator's network weights at 100 percent of its stake, then weight that exposure by stake. The correlation score is the share of stake that sits on more than one network. Weights are the caller's risk weights. No stake is fetched. It is exposed as POST /api/v1/restaking-risk/slashing-correlation 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, Check slashing window feasibility, Score exit timing before a slash. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/restaking-risk/slashing-correlation

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/restaking-risk/slashing-correlation" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "operators": [
    {
      "id": "op-a",
      "stake": 1000,
      "networks": [
        {
          "id": "eigenlayer",
          "weight": 60
        },
        {
          "id": "symbiotic",
          "weight": 50
        }
      ]
    },
    {
      "id": "op-b",
      "stake": 1000,
      "networks": [
        {
          "id": "eigenlayer",
          "weight": 20
        }
      ]
    }
  ]
}
JSON

An 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 APIs

Cross Network Slashing Exposure APIFull docsHow it works