# Delx Commerce — EVM Receipt Status Check

> Delx Commerce — EVM Receipt Status 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 and interprets an EVM transaction receipt status code to determine whether the transaction succeeded or failed

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/evm-receipt-status-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-receipt-status-check-2f78a153
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_K9Hiv_Y_BPO8umBSAVBLR

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-receipt-status-check-2f78a153 -d '<json body>'
```

Example prompt: Can you check whether this EVM receipt status code '1' means the transaction succeeded or failed?

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call, no-signup way to validate EVM transaction receipt status codes deterministically. It is ideal for autonomous agents operating on-chain that need to verify transaction outcomes without retaining data, with cryptographic evidence of computation. Prefer this over manual parsing when you need an auditable, verifiable check.

## Known failure modes

- Missing or empty status field returns a validation error
- Status value outside expected EVM range may return an unexpected result
- Malformed input JSON causes a 400-level error
- Payment failure via x402 protocol prevents endpoint access

## 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 interpreted status (integer), a success boolean, the operation schema identifier, and verifiable evidence including a SHA-256 hash of the input and confirmation that no external calls were made and no data was retained.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "status": {
   "type": "string",
   "maxLength": 8192,
   "description": "Status supplied to EVM Receipt Status Check; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "status": 1,
   "success": true
  },
  "schema": "delx/util-evm-receipt-status-check/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "d954b90ce0d80b3772a5290150d29163df1d54523da6b2375e282ddf4b82cffa",
   "external_calls": 0
  },
  "operation": "evm_preflight:evm_receipt_status_check"
 }
}
```

## More

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