# Delx EVM Transaction Type Classifier

> Delx EVM Transaction Type Classifier 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).

Classifies an EVM transaction type integer (e.g. 0, 1, 2) into a human-readable category such as 'legacy', 'access_list', or 'dynamic_fee'.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/evm-tx-type-classify?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-evm-transaction-type-classifier-a849033f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4BWKxWc2_ut_fqJWV_xuv

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-transaction-type-classifier-a849033f -d '<json body>'
```

Example prompt: What type of Ethereum transaction is transaction_type 2 — is it legacy, access list, or dynamic fee?

## When to prefer this

Choose this endpoint when you need a fast, cheap, verifiable, in-memory classification of an EVM transaction type integer with no data retention and cryptographic evidence of the computation. Ideal for agent preflight checks before submitting Ethereum/EVM transactions, especially when operating in trustless or audit-sensitive environments. Prefer over custom logic when you want a pay-per-call model with no signup friction.

## Known failure modes

- Invalid or missing transaction_type integer returns an error or unexpected classification
- Unrecognized transaction type integers outside the defined EVM spec may return an unknown/unclassified result
- Network or service downtime returns a non-200 HTTP response
- Payment failure (USDC/x402) prevents the call from completing

## 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 containing the classification label (e.g. 'legacy', 'access_list', 'dynamic_fee'), the echoed transaction_type integer, a status ('pass'), an operation identifier ('evm_preflight:evm_tx_type_classify'), a schema version string, and an evidence block including the SHA-256 hash of the input, a flag confirming no data was retained, and the count of external calls made (always 0 — purely in-memory computation).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "transaction_type": {
   "type": "integer",
   "description": "Transaction Type supplied to EVM Tx Type Classify; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "classification": "dynamic_fee",
   "transaction_type": 2
  },
  "schema": "delx/util-evm-tx-type-classify/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "8d7860bf2ad3e866ffa9821fc838a4e0b9a80325d1457ae15d94fe9bf16abe66",
   "external_calls": 0
  },
  "operation": "evm_preflight:evm_tx_type_classify"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-evm-transaction-type-classifier-a849033f/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)