# Delx Control Coverage

> Delx Control Coverage 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).

Measures how well a set of implemented governance controls covers a required set, returning deterministic JSON gap analysis.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/control-coverage
- 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-control-coverage-1082840d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nZEIrK5FnLYdvBA6Xd6ir

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-control-coverage-1082840d -d '<json body>'
```

Example prompt: Check how well our implemented controls — ['access-control', 'encryption-at-rest', 'audit-logging'] — cover the required set ['access-control', 'encryption-at-rest', 'audit-logging', 'mfa', 'data-retention'] and tell me what's missing.

## When to prefer this

Use this endpoint when you need a fast, deterministic, stateless, local computation of control coverage gaps — particularly as a preflight or analysis step inside an enterprise agent workflow before committing to a policy, security, data, or compliance decision. Prefer it over manual gap analysis or heavyweight GRC tools when you need machine-readable JSON output at low cost ($0.003 USDC) with no data retention or external dependencies.

## Known failure modes

- Missing or empty 'required' array returns an error or trivially full coverage result
- Missing or empty 'implemented' array returns 0% coverage with all required controls listed as gaps
- Malformed array items (non-string or null values) may cause validation errors
- Network timeout or payment authorization failure via x402 returns a 402 or connection error
- Sending duplicate control names may affect coverage computation depending on deduplication logic

## How this service works

Measure implemented governance controls against a required set. Use it as a bounded preflight or analysis step inside an enterprise agent workflow before data, policy, integration, security, or commercial decisions reach production. Returns deterministic machine-readable JSON for $0.003 USDC via x402 on Base. Execution is first-party, local-only, stateless, memory-only, and has no paid upstream or input retention. Results are advisory; the caller remains responsible for authorization and produc…

## Output

Returns a deterministic JSON object containing coverage metrics (e.g. coverage ratio or percentage), a list of controls that are matched/covered, a list of missing controls not yet implemented, and possibly a gap count — all computed locally and statelessly with no data retention.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "array",
   "description": "Input field: required."
  },
  "implemented": {
   "type": "array",
   "description": "Input field: implemented."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/util-control-coverage/v1",
  "missing": [
   "approval"
  ],
  "required_count": 3,
  "coverage_percent": 66.6667,
  "implemented_count": 2
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-control-coverage-1082840d/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)