# Edition Records - Provenance Edge Audit

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

Binds a declared graph edge to both of its pinned endpoint nodes and the exact owner/subject record, auditing provenance linkage in supplied edition record data.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/edition-records/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045341/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/edition-records-provenance-edge-audit-9af705bb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2-gDzHSBHR7xcvxr8GS_Q

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 edition-records-provenance-edge-audit-9af705bb -d '<json body>'
```

Example prompt: Audit the provenance edges in my edition record dataset — I have 5 edges and 6 nodes, the data class is 'public', and confirm only non-personal metadata is included. Tell me whether each edge is correctly bound to both its pinned endpoint nodes and the right owner/subject record.

## When to prefer this

Use this endpoint when you need to verify that declared graph edges in edition record data are correctly bound to both of their pinned endpoint nodes and the associated owner/subject record, particularly for public or synthetic (non-personal) datasets. It is appropriate for provenance auditing of library edition graphs prior to publication or ingestion, where independent certification is not required but declared-record consistency must be confirmed.

## Known failure modes

- Edge count exceeds 32-item maximum — request rejected
- Node count below minimum of 1 — request rejected
- dataClass value not in ['public','synthetic'] enum — validation error
- nonpersonalMetadata not set to true (const:true) — request rejected
- Mismatched edge-to-node references in supplied data — audit flags binding failures
- Malformed edge or node array entries — parsing error

## 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 audit result indicating whether each declared edge is correctly bound to both of its pinned endpoint nodes and the exact owner/subject record in the supplied edition record data, along with any consistency flags or mismatches detected.

## 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/edition-records-provenance-edge-audit-9af705bb/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)