Score bridge leg consistency API

Group caller-supplied source and destination legs by message id. A message is consistent when both legs succeeded for the same amount. The recovery index is the hardest leg: a pending destination after a successful source scores lower than two matching successes. No chain is queried.

The Score bridge leg consistency operation is part of the Bridge Partial Failure Audit API on BRAINIAC.software. Group caller-supplied source and destination legs by message id. A message is consistent when both legs succeeded for the same amount. The recovery index is the hardest leg: a pending destination after a successful source scores lower than two matching successes. No chain is queried. It is exposed as POST /api/v1/crypto-operations/bridge-leg-consistency 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 bridge operations, transaction receipts, event logs, and field mappings processed locally Limitations: Only the records in the request are compared. Chain state and transaction finality are not checked. A missing source or destination record does not prove that a bridge transfer failed. Event logs are not decoded unless fieldMapping names the message identifier and the other fields to read. Token addresses on different chains are not treated as the same asset. Amounts are compared with the supplied decimals, fee, and conversion rate. No exchange rate is fetched. bridge-leg-consistency scores the supplied legs only. The recovery index is the hardest message, not an average. 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 Audit bridge partial failure. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/crypto-operations/bridge-leg-consistency

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/crypto-operations/bridge-leg-consistency" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "legs": [
    {
      "message_id": "a",
      "role": "source",
      "status": "success",
      "amount": 1000000
    },
    {
      "message_id": "a",
      "role": "destination",
      "status": "success",
      "amount": 1000000
    },
    {
      "message_id": "b",
      "role": "source",
      "status": "success",
      "amount": 500000
    },
    {
      "message_id": "b",
      "role": "destination",
      "status": "pending",
      "amount": 0
    }
  ]
}
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

Bridge Partial Failure Audit APIFull docsHow it works