# Incident Notes - Export Semantic Parity

> Incident Notes - Export Semantic Parity is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.039297/call, status unknown (last checked 2026-11-04).

Compares two sets of closed incident note metadata by ID, revision, service, state, severity, and event digest to detect structural differences, ignoring narrative content and export ordering.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/incident-notes/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039297/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/incident-notes-export-semantic-parity-7904c21a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0gSvG7YyrIkSOhgNsir4m

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 incident-notes-export-semantic-parity-7904c21a -d '<json body>'
```

Example prompt: Compare these two batches of closed incident note metadata — the 'before' set has up to 32 entries and the 'after' set has up to 32 entries — using only public, nonpersonal metadata, and tell me which incidents changed in ID, revision, service, state, severity, or event digest.

## When to prefer this

Use this endpoint when you need a deterministic, content-agnostic structural comparison of two snapshots of closed incident metadata — particularly when you want to detect changes in IDs, revisions, states, severities, or digests without parsing or interpreting narrative text. Ideal for compliance audits, post-deployment checks, or cross-team reconciliation where only nonpersonal, public or synthetic metadata is involved.

## Known failure modes

- Exceeds 32-item limit on before or after arrays — returns validation error
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — schema validation failure
- Malformed incident entries in array — may return partial or error response
- Result data expired after 24-hour retention window — no retrieval possible

## How this service works

Compare closed incident projections by ID, revision, service, state, severity and event digest. Ignores export order; no interpretation of incident narratives or verified resolution. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured parity report showing which incident records differ between the before and after sets, broken down by fields such as ID, revision, service, state, severity, and event digest. Export ordering is disregarded. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "before": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/incident-notes-export-semantic-parity-7904c21a/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)