# Delx SLA Breach Count

> Delx SLA Breach Count is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-13).

Counts the number of latency samples that exceed a given SLA threshold in milliseconds, returning a deterministic breach count.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/sla-breach-count
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-sla-breach-count-f83c8a4d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pHNw52WFReUdeqsbfK9aI

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

Example prompt: Count how many of these latency samples breach my 200ms SLA: [145, 210, 98, 305, 189, 420, 175, 310] — I need the exact breach count.

## When to prefer this

Choose this endpoint when you need a fast, stateless, zero-cost-upstream computation to count how many latency samples exceed a defined SLA threshold — particularly in SRE pipelines, error budget calculations, or health scoring workflows where deterministic, machine-readable output is required without relying on external data sources or paid upstream services.

## Known failure modes

- Missing sla_ms field returns validation error
- Empty samples_ms array returns breach count of zero
- Non-numeric values in samples_ms array cause parsing errors
- Negative latency values may be accepted but produce unexpected results
- Network timeout results in no response from endpoint

## How this service works

Count SLA breaches in a latency sample against a millisecond threshold — call when counting latency samples above an SLA. Use for SRE/ops math agents buy from broad utility catalogs: SLA, error budget, success rate, and health scores with zero upstream cost. Returns deterministic machine-readable JSON for $0.003 USDC via x402 on Base. Execution is first-party, local-only, stateless, and memory-only with no paid upstream, no input retention, and no claim of live chain tip, web search, or media g…

## Output

Returns a deterministic JSON object containing the count of latency samples that exceed the specified SLA threshold, along with details such as which samples breached and optionally the breach rate, enabling downstream SRE calculations like error budget consumption.

## 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-sla-breach-count-f83c8a4d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)