# Tool Schemas — Source Coverage Map

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

Maps tool-schema declarations (owner, revision, input/output) to a source manifest, identifying which declared schemas lack source coverage.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tool-schemas/source-coverage-map?utm_source=zero.xyz
- Price: $0.035093/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-27
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-schemas-source-coverage-map-097fffe9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PwUU6rrDBf1o1ZOpFRgsK

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 tool-schemas-source-coverage-map-097fffe9 -d '<json body>'
```

Example prompt: Check which of my public tool schema declarations are missing from the source manifest — I have up to 10 contracts and 5 manifests I want to cross-reference for coverage gaps.

## When to prefer this

Use this endpoint when you need to audit whether declared tool schemas (by owner, revision, input, and output) are represented in a known source manifest, particularly for governance, compliance, or pre-release verification workflows using only public or synthetic nonpersonal metadata. Prefer this over general schema validation tools when the specific concern is source manifest coverage rather than schema correctness or runtime behavior.

## Known failure modes

- Contracts or manifests arrays empty or exceeding 32-item limit returns validation error
- nonpersonalMetadata not set to true causes rejection
- Mismatched or malformed contract/manifest formats result in incomplete coverage map
- dataClass value outside 'public' or 'synthetic' enum causes schema validation failure
- Digest agreement in the manifest does not imply source truth — gaps may still exist despite matching digests

## How this service works

Bind tool-schema declaration 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 coverage map binding each tool-schema declaration (identified by owner, revision, input schema, and output schema) to its corresponding source manifest entry, with clear identification of any declarations absent from the supplied manifest. Results are available for 24 hours; minimal receipt metadata is retained for 90 days. No implementation conformity or runtime testing is performed.

## 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/tool-schemas-source-coverage-map-097fffe9/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)