# Delx Commerce EVM Confirmation Count

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

Computes the number of EVM block confirmations for a transaction given its inclusion block and current block, returning finality status.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/evm-confirmation-count?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-evm-confirmation-count-15fe87b3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tk_bDZxSGNwae-kaGMR5f

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-commerce-evm-confirmation-count-15fe87b3 -d '<json body>'
```

Example prompt: My transaction was included at block 21500000 and the current block is 21500013 — how many confirmations does it have and is it considered final?

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call, verifiable computation of EVM confirmation depth without standing up your own node or indexer. Ideal for AI agents that need to gate downstream actions on transaction finality without retaining sensitive data. Prefer this over full node RPC calls when you only have block numbers and need a simple finality boolean with auditability proof.

## Known failure modes

- Missing required fields (current_block or inclusion_block not provided) — likely returns validation error
- current_block less than inclusion_block — nonsensical input may return error or negative confirmation count
- Non-integer values passed for block numbers — schema validation failure
- Payment failure via x402 protocol — 402 response if USDC payment not completed

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

Returns a JSON object with the number of confirmations (current_block minus inclusion_block), whether the transaction is considered final (boolean), the required number of confirmations, processing status (pass/fail), and an evidence object confirming no data was retained and no external calls were made — along with an input SHA-256 hash for auditability.

## 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-commerce-evm-confirmation-count-15fe87b3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from commerce.delx.ai](https://www.zero.xyz/host/commerce.delx.ai/llms.txt)