# Api Contracts — Source Coverage Map

> Api Contracts — Source Coverage Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035087/call, status unknown (last checked 2026-10-23).

Maps HTTP contract schema-pair declarations to their exact owner, revision, input, and output source manifests to verify source coverage alignment.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/source-coverage-map?utm_source=zero.xyz
- Price: $0.035087/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-contracts-source-coverage-map-af050271
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vYb-wIREAWz69Idp6iXLI

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 api-contracts-source-coverage-map-af050271 -d '<json body>'
```

Example prompt: Take these 5 HTTP contract schema pairs — all public, non-personal metadata — and map them to their corresponding source manifests so I can see which owner, revision, input, and output sources each one is bound to.

## When to prefer this

Use this endpoint when you need to formally bind HTTP contract schema-pair declarations to their source manifests and verify owner/revision coverage. It is specifically suited for offline, typed, non-personal metadata audits of API contract declarations — not for runtime conformance testing, implementation validation, or live API monitoring. Prefer this over general schema linters or contract diff tools when you need a structured source manifest linkage report with receipt-level auditability.

## Known failure modes

- Missing or malformed contract array entries return validation errors
- Manifests array out of range (0 or >32 items) rejected
- nonpersonalMetadata must be explicitly set to true or request is rejected
- dataClass must be 'public' or 'synthetic'; other values rejected
- Mismatched contract-to-manifest counts may result in partial or empty coverage map
- Result unavailable after 24-hour retention window

## How this service works

Bind HTTP contract schema-pair declarations to an exact owner/revision/input/output source manifest. Digest agreement is not source truth, implementation conformity or runtime testing. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A source coverage map linking each supplied HTTP contract schema-pair declaration to its exact owner, revision, input, and output source manifest entry. The result does not assert implementation conformity, runtime correctness, or digest agreement — only whether a binding exists between the contract declaration and the source manifest. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-contracts-source-coverage-map-af050271/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)