# Delx Commerce Latency SLA Check

> Delx Commerce Latency SLA Check is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-02).

Checks whether an observed latency measurement falls within a specified SLA threshold, returning overage details and a pass/fail result.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/latency-sla-check?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-latency-sla-check-50a8fd44
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZgJNMrBrJ1dKue0PiDz4T

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-latency-sla-check-50a8fd44 -d '<json body>'
```

Example prompt: Check if an observed latency of 420ms is within a 500ms SLA — tell me whether it passed and if not, by how much it exceeded the threshold.

## When to prefer this

Use this endpoint when you need a lightweight, stateless, pay-per-call SLA compliance check without setting up monitoring infrastructure. Ideal for agents running ad-hoc latency assertions in pipelines, deployment gates, or alerting workflows where the result needs to be verifiable and the cost is known upfront. Prefer this over building custom comparison logic when you want a standardized schema output that downstream agents or dashboards can consume consistently.

## Known failure modes

- Missing required fields (sla_ms or observed_ms) returns a 400 error
- Non-numeric inputs for latency fields may cause validation rejection
- Payment failure via x402 if USDC balance is insufficient blocks the request
- Extreme or negative latency values may produce unexpected overage calculations

## How this service works

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

## Output

A JSON object containing the original SLA threshold (sla_ms), the observed latency (observed_ms), whether the measurement is within SLA (within_sla boolean), and the overage in milliseconds (overage_ms, 0 if within SLA). Schema version is tagged as delx/util-latency-sla-check/v1.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "sla_ms": {
   "type": "number",
   "description": "SLA latency threshold in milliseconds."
  },
  "observed_ms": {
   "type": "number",
   "description": "Observed latency sample in milliseconds."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/util-latency-sla-check/v1",
  "sla_ms": 500,
  "overage_ms": 0,
  "within_sla": true,
  "observed_ms": 420
 }
}
```

## More

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