# Publication Records - Provenance Edge Audit

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

Binds declared graph edges to both pinned endpoints and owner/subject records, auditing provenance relationships in publication data

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/publication-records/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045332/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/publication-records-provenance-edge-audit-9757d068
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dkFIGeUnVO0188qbOaiPG

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 publication-records-provenance-edge-audit-9757d068 -d '<json body>'
```

Example prompt: Audit the provenance edges in this publication record dataset — I have 5 edges and 4 nodes, the data class is public, and I need you to confirm the edges are properly bound to their pinned endpoints and owner/subject records.

## When to prefer this

Choose this endpoint when you need to verify that declared provenance edges in publication records are correctly anchored to both pinned endpoints and owner/subject records. It is specifically suited for publication graph integrity checks on public or synthetic datasets with nonpersonal metadata, not for independent certification or live data certification workflows.

## Known failure modes

- Invalid or missing edges array causes validation error
- Nodes array empty or exceeds 32-item limit returns schema rejection
- dataClass not set to 'public' or 'synthetic' causes enum validation failure
- nonpersonalMetadata not set to true (const) causes request rejection
- Edge references nodes not present in the nodes array causing binding failure
- Malformed edge or node structures causing parse errors

## 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 report indicating whether each declared edge is successfully bound to both its pinned endpoints and the corresponding owner/subject records in the publication dataset, along with any mismatches or unresolved bindings found during analysis.

## 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/publication-records-provenance-edge-audit-9757d068/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)