# Migration Impact

> Migration Impact is a paid API for AI agents from api.zfinia.com, paid per call via x402, $0.22/call, status unknown (last checked 2026-10-11).

Analyzes a JSON schema change and real payload samples to determine compatibility verdict and how many payloads would be rejected by the new schema, ranked by failing constraints.

## Facts

- Endpoint: POST https://api.zfinia.com/x402/v1/json-schema-migration-impact?utm_source=zero.xyz
- Price: $0.22/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/migration-impact-d5d28500
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cemAJIs5Ij9Wkre18UZJx

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 migration-impact-d5d28500 -d '<json body>'
```

Example prompt: I'm about to ship a JSON schema change — here's the before and after schema, plus 200 sample payloads from production traffic. Tell me if it's a breaking change for consumers and how many of those payloads would get rejected, ranked by which new constraint is causing the most failures.

## When to prefer this

Use this endpoint when you need evidence-based confidence before shipping a schema change — specifically when you have real payload samples and want to know both the compatibility verdict and the quantified impact on actual traffic. It goes beyond static schema diffing by running your real documents against the new schema, so it distinguishes a breaking change that affects zero current payloads from one that would reject 10% of your traffic. Prefer it over generic JSON Schema validators when migration risk quantification matters.

## Known failure modes

- documents array empty or missing — requires at least 1 sample payload
- before or after schema malformed — invalid JSON Schema object causes error
- documents array exceeds 500 item limit — request rejected
- role enum value not one of producers, consumers, both — validation error
- schema objects reference external $refs that cannot be resolved — constraint analysis incomplete

## How this service works

Decide whether a schema change is safe to ship, with evidence. Returns the compatibility verdict for your clients and, separately, how many of the real payloads you supply would newly be rejected, with the failing constraints ranked by how many payloads each costs. A breaking change nothing relies on is a different decision from one that rejects a tenth of your traffic.

## Output

Returns a compatibility verdict indicating whether the schema change is breaking for producers, consumers, or both, along with a count of how many supplied sample payloads would be rejected under the new schema, and a ranked list of the specific failing constraints ordered by how many payloads each constraint rejects.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "role": {
   "enum": [
    "producers",
    "consumers",
    "both"
   ],
   "type": "string"
  },
  "after": {
   "type": "object"
  },
  "before": {
   "type": "object"
  },
  "documents": {
   "type": "array",
   "items": {},
   "maxItems": 500,
   "minItems": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/migration-impact-d5d28500/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.zfinia.com](https://www.zero.xyz/host/api.zfinia.com/llms.txt)