# Delx Commerce — EVM Transfer Recipient Check

> Delx Commerce — EVM Transfer Recipient 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 that an encoded EVM transfer recipient address matches the intended recipient before executing an on-chain transfer.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/evm-transfer-recipient-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-transfer-recipient-check-52c4c946
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aTvhAs3LiAuPGEdAuh3eo

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-transfer-recipient-check-52c4c946 -d '<json body>'
```

Example prompt: Before sending this EVM transfer, check that the encoded recipient 0x1111111111111111111111111111111111111111 actually matches the intended recipient 0x1111111111111111111111111111111111111111 — I want to make sure no address substitution happened.

## When to prefer this

Use this endpoint when an AI agent or automated payment pipeline needs to verify EVM recipient address integrity before executing an on-chain transfer — especially in contexts where address substitution, clipboard hijacking, or encoding errors are a risk. Prefer this over manual inspection when operating at scale or in automated workflows requiring auditable, verifiable preflight checks with no data retention.

## Known failure modes

- Malformed or non-EVM address format may cause a validation error
- Missing required fields (encoded_recipient or intended_recipient) returns an error
- Addresses that exceed maxLength of 8192 characters are rejected
- Network or service unavailability returns a non-200 response

## 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 indicating whether the encoded recipient matches the intended recipient (matched: true/false), the two address values, a pass/fail status, and an evidence block including a SHA256 hash of the input, confirmation that no data was retained, and the number of external calls made (zero).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "encoded_recipient": {
   "type": "string",
   "maxLength": 8192,
   "description": "Encoded Recipient supplied to EVM Transfer Recipient Check; used only for this bounded calculation and processed in memory without retention."
  },
  "intended_recipient": {
   "type": "string",
   "maxLength": 8192,
   "description": "Intended Recipient supplied to EVM Transfer Recipient Check; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "matched": true,
   "encoded_recipient": "0x1111111111111111111111111111111111111111",
   "intended_recipient": "0x1111111111111111111111111111111111111111"
  },
  "schema": "delx/util-evm-transfer-recipient-check/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "418a07bef00b96e0281dc9f7ee7e9b9a0ad8ec353bc9a709181f9bdae7289050",
   "external_calls": 0
  },
  "operation": "evm_preflight:evm_transfer_recipient_check"
 }
}
```

## More

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