# Telescope Calibrations Provenance Edge Audit

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

Binds a declared provenance edge to both its pinned endpoint nodes and the exact owner/subject, performing a supplied-record analysis of graph edges and nodes for audit purposes.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/telescope-calibrations/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.04533/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/telescope-calibrations-provenance-edge-audit-6b5d2844
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Bdm3JAPyTD_kNfCre61mh

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 telescope-calibrations-provenance-edge-audit-6b5d2844 -d '<json body>'
```

Example prompt: Audit these provenance edges and nodes to check they're correctly bound to their pinned endpoints and the declared owner/subject — the data is classified as public and all metadata is non-personal; give me the full binding analysis.

## When to prefer this

Choose this endpoint when you need to audit declared provenance edges against their pinned endpoint nodes and owner/subject assignments in a supplied record, specifically for public or synthetic data classified as non-personal metadata. It is a record-analysis tool, not an independent certification service, best suited for pre-review compliance checks or lineage graph consistency audits.

## Known failure modes

- Edge or node arrays exceed 32-item limit returning validation error
- dataClass value not in allowed enum ['public','synthetic'] causing rejection
- nonpersonalMetadata not set to true (const) resulting in schema error
- Malformed edge or node structures causing parse failure
- Mismatched edge-to-node references with no matching declared nodes

## 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 whether each declared edge is correctly bound to both pinned endpoint nodes and the exact owner/subject, identifying binding inconsistencies, structural issues, and a summary audit report for the supplied provenance graph records.

## 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/telescope-calibrations-provenance-edge-audit-6b5d2844/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)