# Delx Commerce — Base USDC Recipient Check

> Delx Commerce — Base USDC 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).

Verifies that a Base USDC recipient address matches an expected address before executing a payment transaction

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/base-usdc-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-base-usdc-recipient-check-f26d0f24
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8P62WVND-c-2Z16tsmixt

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-base-usdc-recipient-check-f26d0f24 -d '<json body>'
```

Example prompt: Before I send that USDC payment on Base, verify that the recipient address 0xAbCd...1234 matches the expected address 0xAbCd...1234 so I know it's going to the right wallet.

## When to prefer this

Use this endpoint when an AI agent needs to programmatically verify a Base USDC recipient address matches an expected value before authorizing a blockchain payment — particularly when building automated payment pipelines where address substitution attacks (clipboard hijacking, man-in-the-middle) are a concern. Prefer this over manual comparison when you need a verifiable, auditable proof (SHA-256 hash of input, no-retention guarantee) that the check was performed.

## Known failure modes

- Invalid or malformed Ethereum address format returns an error
- Missing required fields (expected or recipient) results in a validation error
- Address mismatch returns matched: false with status indicating failure
- Network or server error returns a non-200 HTTP 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 with a 'matched' boolean indicating whether the recipient address equals the expected address, echoes both addresses back, provides an operation status ('pass' or 'fail'), a schema identifier, and an evidence block including a SHA-256 hash of the input and confirmation that no data was retained and no external calls were made.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "expected": {
   "type": "string",
   "maxLength": 8192,
   "description": "Expected supplied to Base USDC Recipient Check; used only for this bounded calculation and processed in memory without retention."
  },
  "recipient": {
   "type": "string",
   "maxLength": 8192,
   "description": "Recipient supplied to Base USDC 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,
   "expected": "0x1111111111111111111111111111111111111111",
   "recipient": "0x1111111111111111111111111111111111111111"
  },
  "schema": "delx/util-base-usdc-recipient-check/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "9dd1f2722581e00d07ace195c7159bd7b506c1b4c7faa4078e008b30306d63d0",
   "external_calls": 0
  },
  "operation": "evm_preflight:base_usdc_recipient_check"
 }
}
```

## More

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