# Delx EVM Transfer Recipient Check

> Delx EVM Transfer Recipient Check is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Validates that an encoded EVM recipient address matches the intended recipient address before executing a transfer, as a preflight safety check.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/evm-transfer-recipient-check
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-evm-transfer-recipient-check-4fac9be2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VkuL4rsz6m9yReNFVWvqt

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

Example prompt: Before I send that ETH transfer, check that the encoded recipient address 0x1111111111111111111111111111111111111111 actually matches the intended recipient 0x1111111111111111111111111111111111111111 — I want to make sure nothing got swapped.

## When to prefer this

Choose this endpoint when you need a lightweight, stateless, auditable preflight check to confirm an EVM recipient address hasn't been tampered with or corrupted before executing a blockchain transfer. It is ideal for agent-driven workflows where address encoding happens programmatically and clipboard hijacking or encoding bugs are a risk. Prefer this over manual comparison when you need a SHA-256 evidence trail confirming the check was performed without data retention.

## Known failure modes

- Mismatch detected: matched=false returned when encoded_recipient differs from intended_recipient, status='fail'
- Malformed address input: if addresses are not valid hex strings, endpoint may return an error or unexpected result
- Payload too large: encoded_recipient or intended_recipient exceeding 8192 characters will be rejected
- Network/payment failure: x402 payment of $0.001 USDC not processed, resulting in 402 response

## How this service works

EVM Transfer Recipient Check: EVM Transfer Recipient Check compares an encoded recipient address with the intended recipient from bounded caller-supplied values without an external provider. Call EVM Transfer Recipient Check before signing, submitting, replacing, or accepting an EVM/Base transaction assembled from caller-owned data. Returns normalized transaction evidence, calculated budget or shape findings, and a fail-closed preflight status for EVM Transfer Recipient Check as versioned deter…

## Output

Returns a JSON object with a 'matched' boolean, the echoed encoded and intended recipient addresses, a pass/fail status, an operation label ('evm_preflight:evm_transfer_recipient_check'), an evidence block confirming no data retention and zero external calls, and the SHA-256 hash of the input for audit purposes.

## 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-evm-transfer-recipient-check-4fac9be2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)