# Delx SLO Compliance

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

Calculates whether a service meets its SLO target by comparing good events to total events and returning a compliance verdict in machine-readable JSON.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/slo-compliance
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-slo-compliance-a9823557
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ezxr-iyw8UaN6ghFcWVVk

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-slo-compliance-a9823557 -d '<json body>'
```

Example prompt: We had 99,850 successful requests out of 100,000 total this week — can you check whether that meets our 99.9% SLO target?

## When to prefer this

Choose this endpoint when you need a deterministic, stateless, local computation of SLO compliance from raw event counts — especially in agentic workflows that require a bounded preflight check before acting on untrusted input, calling an upstream API, or approving a deployment. It is ideal when you do not want to rely on an external observability platform and simply need a cheap, fast, machine-readable verdict from first-party math.

## Known failure modes

- Validation failure if good_events exceeds total_events — not billed
- Missing required fields (good_events or total_events) return structured validation error — not billed
- Non-integer values for event counts rejected with validation error
- target_percent out of range (0-100) causes validation failure
- Network errors or payment issues may prevent call completion

## How this service works

Measure achieved reliability against an SLO target from good and total events. Use it before an autonomous workflow acts on untrusted input, changes an API, retries a request, or evaluates production reliability. Returns bounded machine-readable JSON for $0.002 USDC via x402 on Base. Execution is deterministic, first-party, local-only, stateless, and does not call an upstream provider; structured validation failures are not billed.

## Output

Returns a bounded machine-readable JSON object indicating whether the computed reliability (good_events / total_events as a percentage) meets the specified target_percent, along with the achieved reliability value and a compliance boolean or verdict field.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "good_events": {
   "type": "integer",
   "minimum": 0
  },
  "total_events": {
   "type": "integer",
   "minimum": 0
  },
  "target_percent": {
   "type": "number",
   "default": 99.9,
   "maximum": 100,
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/slo-compliance/v1",
  "compliant": true,
  "bad_events": 20,
  "good_events": 99980,
  "total_events": 100000,
  "actual_percent": 99.98,
  "target_percent": 99.9,
  "gap_percentage_points": 0.08
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-slo-compliance-a9823557/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)