# Tool Schemas Revision Delta Map

> Tool Schemas Revision Delta Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.021304/call, status unknown (last checked 2026-10-28).

Compares two revisions of tool-schema declarations and returns a delta of changes to input/output pins, targets, and scope labels as contract metadata.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tool-schemas/revision-delta-map?utm_source=zero.xyz
- Price: $0.021304/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-schemas-revision-delta-map-60edfb4b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VzCjrDBh_qQJ1jerHo_jb

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-revision-delta-map-60edfb4b -d '<json body>'
```

Example prompt: Can you compare these two versions of our tool schema and show me what changed in the input/output pins, targets, and scope labels? The data is non-personal and synthetic — here's the 'before' object and the 'after' object.

## When to prefer this

Use this endpoint when you need a lightweight, offline diff of tool-schema contract metadata between two specific revisions — particularly when you only care about pin declarations, targets, and scope label changes rather than full semantic compatibility analysis. Best suited for CI pipelines, pre-release audits, or schema drift monitoring where only non-personal synthetic or public metadata is involved.

## Known failure modes

- Missing or malformed 'before'/'after' objects result in a validation error
- nonpersonalMetadata must be explicitly set to true or the request is rejected
- dataClass must be 'public' or 'synthetic'; other values cause an enum validation failure
- Supplying personal data may cause the request to be rejected based on declared data-class policy
- Large or deeply nested schema objects may hit size limits or increase latency

## How this service works

Compare revision-pinned tool-schema declaration target, input/output pins and scope labels. These are contract metadata deltas, not full compatibility analysis or a causal explanation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured delta report highlighting changes between the 'before' and 'after' tool-schema declarations, including differences in input/output pins, revision-pinned targets, and scope labels. This is contract metadata diff output only — not a full compatibility analysis or causal explanation. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "object"
  },
  "before": {
   "type": "object"
  },
  "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-revision-delta-map-60edfb4b/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)