# Delx Commerce X402 Delivery Latency Check

> Delx Commerce X402 Delivery Latency 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).

Checks whether a given API response latency falls within a specified maximum SLA threshold and returns a verifiable pass/fail result

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/x402-delivery-latency-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-x402-delivery-latency-check-0bdfc6ec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UetOZ9MEZdiMvvYW5V-mv

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-x402-delivery-latency-check-0bdfc6ec -d '<json body>'
```

Example prompt: Check whether a measured latency of 120ms is within my SLA maximum of 1000ms — I need a verifiable pass/fail result with a SHA-256 hash of the inputs.

## When to prefer this

Use this endpoint when you need a cryptographically verifiable, pay-per-result SLA check with no signup and a tamper-evident SHA-256 input hash — ideal for autonomous agents operating under x402 payment protocols that need auditable proof of latency compliance without storing sensitive data.

## Known failure modes

- Missing required fields (latency_ms or maximum_ms) returns a validation error
- Non-integer values for latency_ms or maximum_ms cause schema rejection
- Payment failure via x402 protocol blocks request processing
- Negative latency values may produce undefined behavior

## 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 the original latency_ms and maximum_ms values, a boolean within_sla field, an overall status string ('pass' or 'fail'), an evidence block containing a SHA-256 hash of the inputs, confirmation that no data was retained, and the count of external calls made (always 0), enabling verifiable, auditable SLA checks.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "latency_ms": {
   "type": "integer",
   "description": "Latency Ms supplied to X402 Delivery Latency Check; used only for this bounded calculation and processed in memory without retention."
  },
  "maximum_ms": {
   "type": "integer",
   "description": "Maximum Ms supplied to X402 Delivery Latency Check; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "latency_ms": 120,
   "maximum_ms": 1000,
   "within_sla": true
  },
  "schema": "delx/util-x402-delivery-latency-check/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "03c9c90cd7fb858eb54622ab93888c5358b1c9a17f5cf97704f3515687d97231",
   "external_calls": 0
  },
  "operation": "delivery_contract:x402_delivery_latency_check"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-x402-delivery-latency-check-0bdfc6ec/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)