# Planetary Measurements - Provenance Edge Audit

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

Audits declared provenance edges by binding each edge to its pinned endpoint nodes and verifying owner/subject record alignment against supplied metadata.

## Facts

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

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 planetary-measurements-provenance-edge-audit-fd3dd074 -d '<json body>'
```

Example prompt: Audit these 5 provenance edges and their 5 pinned endpoint nodes in my synthetic planetary measurements dataset — make sure each edge is correctly bound to both endpoints and that the owner/subject records align; nonpersonalMetadata is true.

## When to prefer this

Choose this endpoint when you need to verify that declared provenance edges in a celestial or planetary measurement graph are correctly bound to their pinned endpoint nodes and that owner/subject record associations are consistent. It is specifically designed for supplied-record analysis (not independent certification) of non-personal, public or synthetic metadata graphs with up to 32 edges and 32 nodes.

## Known failure modes

- Edge or node array exceeds 32-item limit, returning a validation error
- Missing required nonpersonalMetadata:true flag causes request rejection
- Invalid or unsupported dataClass value returns an enum validation error
- Mismatched edge-to-node references result in binding failure details per edge
- Empty edges or nodes arrays (below minItems:1) rejected immediately

## 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 a report indicating whether each declared provenance edge is correctly bound to both its pinned endpoint nodes, along with owner/subject record alignment status for each edge. No independent certification is issued — 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/planetary-measurements-provenance-edge-audit-fd3dd074/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)