# Delx Commerce EVM Slippage Bounds Check

> Delx Commerce EVM Slippage Bounds 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 whether the actual slippage on an EVM token swap falls within an acceptable policy threshold before execution

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/evm-slippage-bounds-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-slippage-bounds-check-4a22d83b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pnzw9RrddhQ_TZqKfZU9x

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-slippage-bounds-check-4a22d83b -d '<json body>'
```

Example prompt: Before I execute this swap, check if the slippage is within my 100 bps maximum — expected output is 1000000000 and minimum output is 990000000.

## When to prefer this

Use this endpoint when an AI agent needs a lightweight, verifiable, privacy-preserving preflight check on EVM swap slippage before submitting a transaction on-chain. Ideal when you want cryptographic evidence (input hash) that the check was performed without data retention, and when paying per-call without signup overhead via x402/USDC is preferred over integrating a full on-chain oracle or DEX SDK.

## Known failure modes

- Missing required fields (minimum_output_raw, expected_output_raw, or maximum_slippage_bps) cause validation errors
- Non-numeric string values for output amounts may cause parsing failures
- Payment not received or insufficient USDC causes 402 rejection
- Slippage exceeds policy threshold returns within_policy: false but is not itself an error — the agent must handle this as a soft failure

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

Returns the computed slippage in basis points (slippage_bps), a boolean indicating whether the trade is within policy (within_policy), a pass/fail status string, and an evidence object containing a SHA-256 hash of the inputs and confirmation that no data was retained and no external calls were made.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "minimum_output_raw": {
   "type": "string",
   "maxLength": 8192,
   "description": "Minimum Output Raw supplied to EVM Slippage Bounds Check; used only for this bounded calculation and processed in memory without retention."
  },
  "expected_output_raw": {
   "type": "string",
   "maxLength": 8192,
   "description": "Expected Output Raw supplied to EVM Slippage Bounds Check; used only for this bounded calculation and processed in memory without retention."
  },
  "maximum_slippage_bps": {
   "type": "integer",
   "description": "Maximum Slippage Bps supplied to EVM Slippage Bounds Check; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "slippage_bps": 100,
   "within_policy": true
  },
  "schema": "delx/util-evm-slippage-bounds-check/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "5dc5df2b52d98e3702891cadc557bb1b15650ccede841dc6c0a42606eb549a31",
   "external_calls": 0
  },
  "operation": "evm_preflight:evm_slippage_bounds_check"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-evm-slippage-bounds-check-4a22d83b/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)