# Package Manifests Source Coverage Map

> Package Manifests Source Coverage Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035123/call, status unknown (last checked 2026-10-16).

Binds package release records to an owner/subject/revision/content/source frame and maps source coverage across supplied rows and sources, returning hash-shaped declarations (not independently verified source bytes).

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/package-manifests/source-coverage-map?utm_source=zero.xyz
- Price: $0.035123/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/package-manifests-source-coverage-map-376c9ad3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PRQ_Ogr2y-WWQziN1xMIn

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 package-manifests-source-coverage-map-376c9ad3 -d '<json body>'
```

Example prompt: Can you run a source coverage map on these 5 package manifest rows against 3 source references, treating the data as public and confirming it's non-personal metadata, so I can see which sources cover which records?

## When to prefer this

Use this endpoint when you need to declaratively bind package release manifest rows to a structured owner/subject/revision/content/source frame and produce a coverage map across up to 32 rows and 32 sources. Prefer this over general package analysis tools when the goal is source-frame binding and hash-shaped declarations for file inventory records rather than independent verification or certification of source bytes.

## Known failure modes

- Rows or sources arrays outside 1–32 item bounds return validation errors
- dataClass value outside 'public' or 'synthetic' enum causes rejection
- nonpersonalMetadata not set to true (const) causes request failure
- Malformed or incomplete row/source objects may yield partial or empty coverage map
- Network or payment failure (x402) prevents execution

## How this service works

Bind record references to an exact owner/subject/revision/content/source frame; hash-shaped strings are declarations, not independently verified source bytes for caller-supplied package release and file-inventory Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a source coverage map that binds each supplied package manifest row to an owner/subject/revision/content/source frame, with hash-shaped declaration strings indicating coverage. Results represent supplied-record analysis and declared associations, not independently verified source bytes or certification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "sources": {
   "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/package-manifests-source-coverage-map-376c9ad3/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)