# Orbital Records - Provenance Edge Audit

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

Validates declared graph edges by binding them to pinned endpoint nodes and owner/subject records, auditing provenance linkage in orbital/celestial record declarations.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/orbital-records/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045328/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/orbital-records-provenance-edge-audit-53bc0c30
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QhtRZuGsivmcZlWkaAqqC

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 orbital-records-provenance-edge-audit-53bc0c30 -d '<json body>'
```

Example prompt: Can you audit the provenance edges in my orbital records graph — I have up to 10 edges and 10 nodes, all public data with non-personal metadata — and check that each edge is properly bound to both its endpoint nodes and the correct owner and subject records?

## When to prefer this

Choose this endpoint when you need to audit provenance linkage between declared graph edges and their pinned endpoint nodes or owner/subject records in celestial/orbital record schemas. It is specifically suited for graph-structured celestial data with bounded edge/node counts (up to 32 each) and restricted to public or synthetic, non-personal metadata. Not appropriate for raw data certification, CSV parsing, or general-purpose graph analysis outside the orbital records domain.

## Known failure modes

- Edges or nodes arrays exceed 32 items — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not explicitly set to true — request rejected
- Malformed edge or node declarations — parsing failure or incomplete audit
- Empty edges or nodes array (below minItems:1) — schema validation 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 report indicating which declared edges are successfully bound to their pinned endpoint nodes and owner/subject records, flagging any edges with missing, mismatched, or incomplete provenance linkage. Does not perform independent certification — results reflect supplied-record analysis only.

## 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/orbital-records-provenance-edge-audit-53bc0c30/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)