# Delx EVM Confirmation Count

> Delx EVM Confirmation Count is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Calculates the number of block confirmations between a current block and an inclusion block on an EVM-compatible blockchain.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/evm-confirmation-count
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-evm-confirmation-count-b466752f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qTdSMBjN1nxIJ3g54DXPl

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 delx-evm-confirmation-count-b466752f -d '<json body>'
```

Example prompt: Check how many block confirmations my transaction has — it was included at block 18999987 and the current block is 19000000.

## When to prefer this

Use this endpoint when you need a lightweight, deterministic, in-memory calculation of EVM block confirmations without any external RPC calls or blockchain node dependencies. Ideal for agent preflight checks before executing downstream actions that require transaction finality, especially when you already have both block numbers available and want a governed, auditable computation with no data retention.

## Known failure modes

- Missing required fields (current_block or inclusion_block) returns a validation error
- current_block less than inclusion_block may return negative confirmation count or error
- Non-integer block values cause schema validation failure
- Network or server errors return 5xx responses

## How this service works

EVM Confirmation Count: EVM Confirmation Count calculates confirmations from inclusion and current block numbers from bounded caller-supplied values without an external provider. Call EVM Confirmation Count before signing, submitting, replacing, or accepting an EVM/Base transaction assembled from caller-owned data. Returns normalized transaction evidence, calculated budget or shape findings, and a fail-closed preflight status for EVM Confirmation Count as versioned deterministic JSON. Price: $0…

## Output

Returns a JSON object with whether the transaction is final (boolean), the number of confirmations computed (integer), and the number of required confirmations for finality. Also includes an evidence block confirming no data was retained, the SHA-256 hash of the input, and zero external calls were made.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "current_block": {
   "type": "integer",
   "description": "Current Block supplied to EVM Confirmation Count; used only for this bounded calculation and processed in memory without retention."
  },
  "inclusion_block": {
   "type": "integer",
   "description": "Inclusion Block supplied to EVM Confirmation Count; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "final": true,
   "confirmations": 13,
   "required_confirmations": 1
  },
  "schema": "delx/util-evm-confirmation-count/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "c64aaf04c19ec735e8d0e6149944a1c600034b3f834d1e7729e324ba8cf54b5f",
   "external_calls": 0
  },
  "operation": "evm_preflight:evm_confirmation_count"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-evm-confirmation-count-b466752f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)