# Reading Plans - Provenance Edge Audit

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

Binds declared graph edges to their pinned endpoint nodes and owner/subject records for provenance analysis of reading plan data structures.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/reading-plans/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.04534/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reading-plans-provenance-edge-audit-0cebafc9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8-2QABEZoPwYakBjvmxWR

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

Example prompt: Audit the provenance edges in my reading plan graph — I have up to 10 edges and 8 nodes, the data class is public, and all metadata is non-personal. Bind each declared edge to its pinned endpoints and check owner/subject record associations.

## When to prefer this

Use this endpoint when you need to audit and validate provenance bindings between declared graph edges and their pinned endpoint nodes and owner/subject records in the context of reading plan library data. Prefer this over generic graph validation tools when the analysis is limited to public or synthetic (non-personal) data and you need a caller-supplied record analysis rather than independent certification.

## Known failure modes

- Edge or node arrays outside allowed range (1-32 items) return validation error
- dataClass value outside allowed enum ('public' or 'synthetic') causes rejection
- nonpersonalMetadata not set to true (const) causes request failure
- Malformed edge or node objects cause processing errors
- Edges referencing nodes not present in the nodes array may produce unresolved binding warnings

## 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 provenance binding results showing how each declared edge maps to its pinned endpoint nodes and corresponding owner/subject records, flagging mismatches or unbound edges based on the supplied graph structure.

## 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/reading-plans-provenance-edge-audit-0cebafc9/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)