Back to Browse
Package Manifests Source Coverage Map
x402
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).
Price / call$0.035123
Success—
StatusUnknown
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.
Example use cases
Open-source release audit coverage
“I have 12 package manifest rows from our latest open-source release and 4 declared source references — can you bind them into a source coverage map and show me which rows each source covers? Data is public and non-personal.”
Synthetic test data source binding
“We generated 8 synthetic package manifest rows for QA and want to map them against 2 source references. Can you run the source coverage analysis with dataClass set to synthetic and non-personal metadata confirmed?”
File inventory source frame validation
“I have a file inventory from a package release — 20 rows and 6 source references — and I need to know which rows are bound to which source frame. Can you produce the coverage map? It's public, non-personal data.”
Technical details
Endpoint
POSThttps://www.mahastrategies.com/api/v1/verify/package-manifests/source-coverage-map?utm_source=zero.xyzWhen to prefer
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.
Side effects
- 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
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| rows | array | |
| sources | array | |
| dataClass | string | |
| nonpersonalMetadata | boolean |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"