# Dataset Schema Evolution Plan

> Dataset Schema Evolution Plan is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010064/call, status unknown (last checked 2026-10-28).

Compares old and new field declarations to detect directional breaking changes between two dataset schema versions

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/datasets/schema-evolution?utm_source=zero.xyz
- Price: $0.010064/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dataset-schema-evolution-plan-e70c627b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_T_b2kKMxxecbUIHCgIfnl

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 dataset-schema-evolution-plan-e70c627b -d '<json body>'
```

Example prompt: Check for breaking changes between my old schema with fields [id, name, email] and the new schema with fields [id, full_name, email, created_at] — treat these as public data and reject any extra fields not in the declaration.

## When to prefer this

Use this endpoint when you need a fast, structured check for directional breaking changes between two versions of a dataset schema without needing semantic equivalence proofs or migration scripts. Ideal for CI/CD pipelines, API versioning workflows, or pre-release data governance audits where a quick field-level diff suffices.

## Known failure modes

- Invalid or empty field arrays (minItems:1 violated)
- Exceeding 64 fields in before or after arrays
- Invalid dataClass value outside 'synthetic' or 'public' enum
- Malformed JSON request body
- Payment failure via x402 protocol

## How this service works

Compare old/new field declarations for directional breaking changes. No semantic-equivalence proof or data migration.

## Output

Returns a field-by-field comparison between the before and after schema declarations, flagging directional breaking changes such as removed fields, renamed fields, or type incompatibilities. Does not provide semantic equivalence proofs or data migration guidance.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 64,
   "minItems": 1
  },
  "before": {
   "type": "array",
   "maxItems": 64,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "synthetic",
    "public"
   ],
   "type": "string"
  },
  "rejectExtraFields": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dataset-schema-evolution-plan-e70c627b/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)