# Tool Context — Source Coverage Map

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

Binds call-context contract declarations to a retained tool-contract manifest and produces a coverage map showing which tools are covered by which call contexts, without verifying actual schemas or implementations.

## Facts

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

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-context-source-coverage-map-cc4cacdc -d '<json body>'
```

Example prompt: Check the source coverage map for my tool-contract manifest — I have 5 call-context declarations and 8 tools, all synthetic public data, and I want to see which contexts are bound to which tools and where there are gaps.

## When to prefer this

Choose this endpoint when you need a lightweight, offline coverage analysis binding call-context declarations to a tool-contract manifest without triggering any schema validation, implementation checks, or live evidence verification. It is best suited for auditing declarative metadata only, especially when all data is public or synthetic and nonpersonal. Prefer alternatives if you need actual tool schema verification, live contract enforcement, or persistent result storage beyond 24 hours.

## Known failure modes

- Empty or malformed calls/tools arrays return a validation error
- Exceeding 32 items in calls or tools array triggers a max-items error
- Passing nonpersonalMetadata as false (or omitting the required const:true) causes rejection
- Invalid dataClass value outside 'public' or 'synthetic' enum results in schema error
- Mismatched or unresolvable contract declaration references may produce empty or partial coverage maps
- Service unavailability after 24-hour result window means results must be regenerated

## How this service works

Bind call-context contract declarations to the supplied retained tool-contract manifest. Digest coverage does not verify an actual tool schema, implementation or evidence contents. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured coverage map associating each supplied call-context declaration with the tools it covers from the manifest, highlighting uncovered or partially covered tools. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days. No actual tool schema or implementation is verified — only declared metadata bindings are analyzed.

## Request schema (JSON Schema)

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

## More

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