# Package Manifests - Provenance Edge Audit

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

Validates declared provenance edges in package manifests by binding each edge to pinned source and target endpoints and verifying owner/subject records in supplied metadata.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/package-manifests/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045309/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-provenance-edge-audit-0ac7555e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BaZymTmMiNd08PwOnlUCo

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-provenance-edge-audit-0ac7555e -d '<json body>'
```

Example prompt: Audit the provenance edges in our package manifest — I've got 5 edges and 6 nodes, all synthetic data, with nonpersonal metadata only — can you check that each edge correctly binds to its pinned endpoints and that the owner/subject records are accounted for?

## When to prefer this

Use this endpoint when you need to verify that declared provenance edges in a package manifest correctly link to pinned artifact endpoints and carry valid owner/subject records, specifically for public or synthetic (non-personal) data. Prefer it over general schema validators when the focus is on supply chain graph integrity and provenance binding rather than syntactic field checks alone.

## Known failure modes

- edges array empty or exceeds 32-item limit — validation error
- nodes array empty or exceeds 32-item limit — validation error
- dataClass not one of 'public' or 'synthetic' — rejected
- nonpersonalMetadata not explicitly true — rejected
- malformed edge or node objects — processing error
- edges reference nodes not present in nodes array — audit flags broken bindings

## How this service works

Bind a declared edge to both pinned endpoints and the exact owner/subject Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an analysis of each declared provenance edge, indicating whether it is correctly bound to both its pinned source and target node endpoints, whether owner and subject records are present and consistent, and any detected anomalies such as missing IDs, broken bindings, or unresolvable references. Does not perform independent certification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "edges": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "nodes": {
   "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-provenance-edge-audit-0ac7555e/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)