# Delx Commerce — EVM Deadline Check

> Delx Commerce — EVM Deadline Check 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).

Validates whether a given Unix epoch timestamp meets a minimum lead-time window before a deadline, used for EVM transaction preflight checks.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/evm-deadline-check?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-deadline-check-558ecfe7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lEfgfwWkH43PPTTlSiPSw

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-deadline-check-558ecfe7 -d '<json body>'
```

Example prompt: Check if current time 1718000000 gives enough lead time before EVM deadline 1718000600, with a minimum lead of 60 seconds.

## When to prefer this

Use this endpoint when an AI agent or automated system needs a verifiable, tamper-evident preflight check that a given deadline epoch has sufficient lead time before initiating an EVM blockchain transaction. Prefer it over client-side arithmetic when you need a cryptographic evidence hash (SHA-256 of inputs) and a structured pass/fail result for auditability, particularly in DeFi or smart contract orchestration workflows.

## Known failure modes

- Missing required fields (now_epoch, deadline_epoch, minimum_lead_seconds) result in validation error
- Deadline already passed (deadline_epoch < now_epoch) may return within_window: false
- Payment not provided or insufficient USDC results in HTTP 402 rejection
- Integer overflow for extremely large epoch values
- Malformed request body returns HTTP 400

## 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 computed lead_seconds between now and the deadline, a within_window boolean indicating whether the minimum lead time is satisfied, the minimum and maximum lead seconds bounds, a pass/fail status, the operation name, and a verifiable evidence block including an input SHA-256 hash and confirmation that no data was retained and no external calls were made.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "now_epoch": {
   "type": "integer",
   "description": "Now Epoch supplied to EVM Deadline Check; used only for this bounded calculation and processed in memory without retention."
  },
  "deadline_epoch": {
   "type": "integer",
   "description": "Deadline Epoch supplied to EVM Deadline Check; used only for this bounded calculation and processed in memory without retention."
  },
  "minimum_lead_seconds": {
   "type": "integer",
   "description": "Minimum Lead Seconds supplied to EVM Deadline Check; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "lead_seconds": 300,
   "within_window": true,
   "maximum_lead_seconds": 9223372036854776000,
   "minimum_lead_seconds": 60
  },
  "schema": "delx/util-evm-deadline-check/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "6837bc595d9c82af4770ef6b89ff2cab040826dc0d84c5e6251a7516cefbedb6",
   "external_calls": 0
  },
  "operation": "evm_preflight:evm_deadline_check"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-evm-deadline-check-558ecfe7/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)