# Policy Excerpts — Record Sequence Diff

> Policy Excerpts — Record Sequence Diff is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035032/call, status unknown (last checked 2026-10-15).

Compares the order and content digests of policy clauses between two extracts, identifying reorderings and differences in shared clause sequences.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/policy-excerpts/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035032/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/policy-excerpts-record-sequence-diff-0244b3e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DrL0qx2Th1o7o7qYA4zjR

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 policy-excerpts-record-sequence-diff-0244b3e6 -d '<json body>'
```

Example prompt: Can you compare the clause order and content digests between these two policy excerpts — the 'before' list has 5 clauses and the 'after' list has 6 clauses, using public data class — and tell me which shared clauses were reordered or changed?

## When to prefer this

Use this endpoint when you need a lightweight, offline structural comparison of policy clause sequences across two extracts — specifically when you only care about relative ordering and content digest changes of shared clauses, not semantic interpretation of policy priority. Ideal for compliance automation, audit trails, and version-tracking workflows that require non-personal, public or synthetic data only.

## Known failure modes

- Array exceeds 32-item limit — request rejected with validation error
- dataClass not set to 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true (const constraint) — request rejected
- Empty or malformed clause arrays — may return empty diff with no detected changes
- Service unavailability — 5xx error with no diff result returned

## How this service works

Compare declared policy clause order and content digests across two extracts. Only relative order of shared clauses counts as reordering; no interpretation of policy priority. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured diff record showing which shared policy clauses were reordered between the 'before' and 'after' arrays, along with content digest comparisons for each shared clause. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. No interpretation of policy priority is included.

## 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/policy-excerpts-record-sequence-diff-0244b3e6/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)