# Tabular Records Condition Coverage Map

> Tabular Records Condition Coverage Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035102/call, status unknown (last checked 2026-10-20).

Validates that each required row-validation condition has exactly one satisfied declaration in a tabular dataset, flagging unknown, contradictory, duplicate, or missing declarations.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tabular-records/condition-coverage-map?utm_source=zero.xyz
- Price: $0.035102/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tabular-records-condition-coverage-map-f856f95f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_v7CYrwiDtpy_kgnB8q6os

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 tabular-records-condition-coverage-map-f856f95f -d '<json body>'
```

Example prompt: Can you check my tabular dataset for condition coverage — I have 12 row IDs, 6 checks, and 3 required checks using synthetic public data — and make sure each required validation condition is declared exactly once with no duplicates or contradictions?

## When to prefer this

Choose this endpoint when you need to enforce that every required row-level validation condition in a tabular dataset is satisfied by exactly one declaration — especially before data ingestion pipelines where ambiguous, missing, or duplicate condition coverage would cause downstream failures. Best suited for synthetic or public (nonpersonal) tabular data with up to 16 row IDs and 32 checks.

## Known failure modes

- Missing required 'nonpersonalMetadata: true' field causes rejection
- More than 32 checks or 16 row IDs exceeds schema limits and returns validation error
- dataClass values outside 'public' or 'synthetic' enum are rejected
- Contradictory or duplicate declarations result in failed coverage status rather than error
- Fewer than 1 check or row ID returns a schema validation error
- Personal data submitted despite nonpersonal constraint may be rejected or flagged

## How this service works

Check each required row-validation condition has exactly one satisfied declaration. Unknown, contradictory, duplicate or missing declarations do not establish valid cells or successful ingestion. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a condition coverage map showing whether each required row-validation condition has exactly one satisfied declaration; flags rows or conditions with unknown, contradictory, duplicate, or missing declarations, plus a minimal receipt with metadata retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "checks": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "rowIds": {
   "type": "array",
   "maxItems": 16,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "requiredChecks": {
   "type": "array",
   "maxItems": 8,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tabular-records-condition-coverage-map-f856f95f/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)