# License Records — Condition Coverage Map

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

Compares declared license-condition checklists against supplied fulfilled/unfulfilled/unknown evidence labels to produce a structured coverage map, without legal interpretation or compliance certification.

## Facts

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

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 license-records-condition-coverage-map-01703cc7 -d '<json body>'
```

Example prompt: Can you map my MIT license condition checklist — attribution, copyright-notice, and no-sublicense — against these evidence labels (attribution: fulfilled, copyright-notice: fulfilled, no-sublicense: unknown) using public data class, and tell me which conditions have gaps?

## When to prefer this

Choose this endpoint when you need a structured, offline comparison of declared license conditions against existing evidence labels — particularly for open source compliance workflows, software audits, or release checklists where you already have evidence labels assigned and want a gap report. It is not a legal interpreter or compliance certifier; prefer it over manual checklist review when you need a machine-readable coverage map quickly at low cost per call.

## Known failure modes

- Empty or missing evidence array returns validation error
- Evidence or requiredConditions arrays exceed 32-item limit causing rejection
- Invalid dataClass enum value (not 'public' or 'synthetic') causes schema error
- nonpersonalMetadata not set to true causes request rejection
- Mismatched or unrecognized condition labels may result in unknown coverage entries
- Result retrieval window exceeded (after 24 hours, retained result unavailable)

## How this service works

Compare declared license-condition checklists with supplied fulfilled/unfulfilled/unknown evidence labels. Does not interpret law, grant permissions or certify license compliance. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured condition coverage map showing each declared license condition matched to its supplied evidence label (fulfilled, unfulfilled, or unknown), highlighting which conditions lack evidence coverage. Does not interpret legal obligations, grant permissions, or certify compliance. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "evidence": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "requiredConditions": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

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