# Delx Commerce SLA Breach Count

> Delx Commerce SLA Breach Count 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-01).

Counts how many latency samples exceed a given SLA threshold and returns the breach count and percentage.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/sla-breach-count?utm_source=zero.xyz
- Price: $0.003/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-sla-breach-count-f189c216
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_W4YsLLe1D7RK6vfHfaMoV

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-sla-breach-count-f189c216 -d '<json body>'
```

Example prompt: I have these latency samples in milliseconds — 120, 450, 620, 310, 870 — and my SLA threshold is 500ms. How many of those samples breach the SLA and what's the breach percentage?

## When to prefer this

Use this endpoint when you need a quick, pay-per-use computation of SLA breach counts and percentages from raw latency samples, without setting up your own monitoring infrastructure. Ideal for agents that need on-demand SLA compliance checks as part of an automated observability or alerting workflow, especially when no persistent monitoring service is warranted.

## Known failure modes

- Missing sla_ms or samples_ms fields returns a validation error
- Empty samples array may return zero counts or an error
- Non-numeric values in samples_ms array may cause a parse or computation error
- Payment failure via x402 protocol returns 402 and no result

## 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 containing the SLA threshold used, total number of samples, count of samples that breached the threshold, and breach percentage (e.g. {schema: 'delx/util-sla-breach-count/v1', sla_ms: 500, breach_count: 1, sample_count: 3, breach_percent: 33.33}).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "sla_ms": {
   "type": "number",
   "description": "SLA latency threshold in milliseconds."
  },
  "samples_ms": {
   "type": "array",
   "description": "Latency samples in milliseconds to count SLA breaches."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/util-sla-breach-count/v1",
  "sla_ms": 500,
  "breach_count": 1,
  "sample_count": 3,
  "breach_percent": 33.3333
 }
}
```

## More

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