# Meeting Records - Provenance Edge Audit

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

Validates decision-to-segment edges for meeting, revision, and digest bindings by checking declared offset containment and structural provenance integrity, using only offline typed nonpersonal metadata.

## Facts

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

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 meeting-records-provenance-edge-audit-eac2278d -d '<json body>'
```

Example prompt: Audit the provenance edges for these meeting records — I need to check that the decision-to-segment bindings and declared offset containment are valid across up to 8 edges and their corresponding segments, using public data class and nonpersonal metadata only.

## When to prefer this

Use this endpoint when you need to structurally validate decision-to-segment provenance edges in meeting records, revisions, or digests without involving any transcript content, personal data, or consent checking. It is specifically suited for offline metadata-only audits of declared offset containment and binding integrity. Prefer this over general document validation tools when your data is nonpersonal, typed, and structured as decision/segment/edge triples.

## Known failure modes

- Invalid or mismatched edge/segment counts (minItems 1, maxItems 32 violated)
- dataClass not set to 'public' or 'synthetic'
- nonpersonalMetadata not set to true (const constraint)
- Malformed edge or segment objects failing schema validation
- Edges referencing decisions not present in the decisions array
- Result expiry after 24 hours makes re-retrieval impossible

## How this service works

Check decision-to-segment edges for meeting/revision/digest bindings and declared offset containment. No transcript, consent check or claim that the segment supports an agreement. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns an audit result indicating whether each decision-to-segment edge correctly declares offset containment and binding integrity for meeting, revision, or digest records. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. No transcript or consent information is included.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "edges": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "segments": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "decisions": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/meeting-records-provenance-edge-audit-eac2278d/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)