# Ecology Observations Control Coverage Validator

> Ecology Observations Control Coverage Validator is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035162/call, status unknown (last checked 2026-10-20).

Validates that each required control in an ecology observation run/method/revision has exactly one satisfied control declaration, flagging missing, unknown, duplicate, or wrong-frame controls

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/ecology-observations/condition-coverage-map?utm_source=zero.xyz
- Price: $0.035162/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ecology-observations-control-coverage-validator-35b677c3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lAZKdg016Umo9sini8sAD

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 ecology-observations-control-coverage-validator-35b677c3 -d '<json body>'
```

Example prompt: Can you check whether run 'ECO-2024-0451' with method digest 'sha256:abc123' and revision 'v3' has all its required controls satisfied — I need a condition coverage map for a public data class export with required controls ['blank','positive','negative']?

## When to prefer this

Use this endpoint when you need to verify that ecology observation run data has complete, non-redundant control coverage before export or regulatory submission. Prefer this over generic data validators when working specifically with ecology observation runs that require exact control declaration matching against a known method/revision. It is a supplied-record analysis tool, not an independent certification service.

## Known failure modes

- Missing required controls result in a non-passing coverage map
- Duplicate control declarations cause validation failure for affected controls
- Wrong-frame controls are flagged and prevent passing status
- Unknown control identifiers are reported as unresolvable
- Invalid or missing runRef/methodDigest/revision returns an error
- Exceeding 32 controls or specifying 0 required controls may cause schema rejection
- nonpersonalMetadata must be set to true or request is rejected

## How this service works

Require exactly one satisfied control declaration for each required control in an exact run/method/revision; missing, unknown, duplicate or wrong-frame controls cannot pass for ecology observation export Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a condition coverage map indicating whether each required control has exactly one satisfied declaration in the specified run/method/revision, with per-control status flags (satisfied, missing, unknown, duplicate, wrong-frame) and an overall pass/fail result for the ecology observation export.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "runRef": {
   "type": "string"
  },
  "controls": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "revision": {
   "type": "string"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "methodDigest": {
   "type": "string"
  },
  "requiredControls": {
   "type": "array",
   "maxItems": 16,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ecology-observations-control-coverage-validator-35b677c3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.mahastrategies.com](https://www.zero.xyz/host/www.mahastrategies.com/llms.txt)