# Tool Schemas — Record Sequence Diff

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

Compares two ordered lists of pinned tool-schema declaration projections to detect insertions, deletions, and reorderings, treating insertions as distinct from reorders.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tool-schemas/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035098/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-schemas-record-sequence-diff-d6b3d006
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N3NRUyuEt1gfbiCRQjKdd

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 tool-schemas-record-sequence-diff-d6b3d006 -d '<json body>'
```

Example prompt: Can you diff these two tool-schema declaration lists — the before list has ['schema-A','schema-B','schema-C'] and the after list has ['schema-B','schema-C','schema-D'] — and tell me what was inserted, deleted, or reordered, treating any new entries as insertions rather than reorders? The data class is synthetic and this is nonpersonal metadata only.

## When to prefer this

Use this endpoint when you need to compare ordered sequences of tool-schema declaration projections and require that insertions be correctly distinguished from reorderings — not conflated. Prefer this over generic diff utilities when the domain is specifically tool-schema metadata, when you need offline typed comparison with no transport execution or schema resolution, and when working with nonpersonal metadata classified as public or synthetic.

## Known failure modes

- Arrays exceeding 32 items will be rejected
- nonpersonalMetadata must be set to true (const) — any other value causes validation failure
- dataClass must be exactly 'public' or 'synthetic' — other values rejected
- Empty or malformed array items may produce incomplete diff results
- Expired results (older than 24 hours) are not retrievable

## How this service works

Compare pinned tool-schema declaration projections and shared-record order without treating insertion as reordering. No transport execution, schema resolution or compatibility certificate. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured diff of the two tool-schema record sequences, identifying which records were inserted, deleted, and reordered, while explicitly distinguishing insertions from reorderings. Results are retained for 24 hours; minimal receipt metadata is kept 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/tool-schemas-record-sequence-diff-d6b3d006/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)