# ZKsync Era Transaction Finality Lookup

> ZKsync Era Transaction Finality Lookup is a paid API for AI agents from b2a-finality.b2a-finality-endpoint.workers.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-29).

Returns the rollup-reported confirmation level, execution status, and optional Ethereum L1 cross-check evidence for a ZKsync Era transaction hash.

## Facts

- Endpoint: GET https://b2a-finality.b2a-finality-endpoint.workers.dev/v1/finality?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/zksync-era-transaction-finality-lookup-64280c73
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wUTHZb7n5xGUQNvKgbqZR

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 zksync-era-transaction-finality-lookup-64280c73
```

Example prompt: Can you do a deep finality check on ZKsync transaction 0x3a1b2c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b and tell me its confirmation level, whether it succeeded or reverted, and include the L1 cross-check of the commit, prove, and execute transactions?

## When to prefer this

Choose this endpoint when you need authoritative, evidence-backed finality status for a ZKsync Era transaction — especially when you need to verify L1 settlement (commit, prove, execute) rather than just rollup-level confirmation. The signed provenance receipt makes it suitable for audit trails and automated payment release workflows. Prefer the deep tier when L1 finality certainty is required (e.g., large withdrawals, cross-chain bridges, compliance checks). Use standard tier for faster, cheaper rollup-level confirmation checks.

## Known failure modes

- Invalid or malformed transaction hash (not matching ^0x[0-9a-fA-F]{64}$) returns a validation error
- Transaction not found on ZKsync returns inconclusive confirmation_level with missing data listed
- Deep depth requested but L1 data not yet available results in partial evidence with missing fields noted
- Unsupported chain value (anything other than 'zksync') returns a schema validation error
- Payment failure (insufficient USDC or x402 protocol error) blocks the response
- Network timeout from ZKsync or Ethereum RPC during deep cross-check may produce partial results

## How this service works

ZKsync Era transaction finality lookup. Returns the rollup-reported confirmation level, execution status and supporting evidence for one transaction hash. A deeper tier adds an independent Ethereum L1 cross-check of the commit, prove and execute transactions. Responses include a signed provenance receipt and list any missing data.

## Output

A JSON response containing: schema_version, confirmation_level enum (pending, sequencer_confirmed, l1_data_posted, l1_proven, finalized, inconclusive), execution_status enum (success, reverted, unknown), a finality tier label, an evidence array with supporting on-chain data, a signed provenance receipt object, and a list of any missing data fields. The deep tier additionally includes L1 cross-check data for the commit, prove, and execute transactions on Ethereum mainnet.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "chain",
      "tx"
     ],
     "properties": {
      "tx": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{64}$",
       "description": "32-byte transaction hash on that rollup"
      },
      "chain": {
       "enum": [
        "zksync"
       ],
       "type": "string",
       "description": "Rollup identifier (zksync)"
      },
      "depth": {
       "enum": [
        "standard",
        "deep"
       ],
       "type": "string",
       "description": "Finality depth: standard, or deep (zksync only, adds the L1 cross-check)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "schema_version",
      "evidence",
      "missing",
      "receipt"
     ],
     "properties": {
      "tier": {
       "enum": [
        "standard",
        "deep",
        "batch"
       ],
       "type": "string"
      },
      "missing": {
       "type": "array"
      },
      "receipt": {
       "type": "object"
      },
      "evidence": {
       "type": "array"
      },
      "schema_version": {
       "type": "string"
      },
      "execution_status": {
       "enum": [
        "success",
        "reverted",
        "unknown"
       ],
       "type": "string"
      },
      "confirmation_level": {
       "enum": [
        "pending",
        "sequencer_confirmed",
        "l1_data_posted",
        "l1_proven",
        "finalized",
        "inconclusive"
       ],
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zksync-era-transaction-finality-lookup-64280c73/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from b2a-finality.b2a-finality-endpoint.workers.dev](https://www.zero.xyz/host/b2a-finality.b2a-finality-endpoint.workers.dev/llms.txt)