# Provenance Manifests - Record Sequence Diff

> Provenance Manifests - Record Sequence Diff is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035116/call, status unknown (last checked 2026-10-20).

Detects which records were inserted or deleted between two provenance manifest snapshots without conflating those changes with record reordering.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/provenance-manifests/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035116/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/provenance-manifests-record-sequence-diff-1604e964
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wgKfGWn0BD11XlcosBduj

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 provenance-manifests-record-sequence-diff-1604e964 -d '<json body>'
```

Example prompt: Can you diff these two provenance manifest snapshots and tell me exactly which records were inserted or deleted — treating this as public, nonpersonal metadata? The before list has up to 32 records and I need the result to cleanly separate insertions and deletions from any reordering.

## When to prefer this

Choose this endpoint when you need to cleanly distinguish record insertions and deletions from record reordering in a provenance manifest, specifically for caller-supplied artifact or dataset metadata. It is the right choice when your manifest arrays are bounded (up to 32 items), the data is nonpersonal typed metadata classified as public or synthetic, and you need only the structural diff without source download, signature verification, or build reproduction.

## Known failure modes

- Array exceeds 32-item limit — request rejected with validation error
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- Malformed or non-array input for before/after fields — schema validation error
- Result expired after 24-hour retention window — result no longer retrievable

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for caller-supplied artifact and dataset provenance manifests. No source download, build reproduction, signature verification, proof of origin, causality or scientific validity. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured diff identifying which records appear only in the 'before' array (deletions) and which appear only in the 'after' array (insertions), explicitly separated from any reordering of records that survived in both snapshots. 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/provenance-manifests-record-sequence-diff-1604e964/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)