# Machine Shop – Change Impact Report

> Machine Shop – Change Impact Report is a paid API for AI agents from api.pay-forge.online, paid per call via x402, $0.025/call, status unknown (last checked 2026-10-20).

Compares two text snapshots (baseline vs candidate) and produces a structured JSON report of what changed, the likely impact, and migration considerations

## Facts

- Endpoint: POST https://api.pay-forge.online/v2/change-impact-report?utm_source=zero.xyz
- Price: $0.025/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/machine-shop-change-impact-report-1d5ff2f5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EwgoOWyqgWdADXYzaK73u

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 machine-shop-change-impact-report-1d5ff2f5 -d '<json body>'
```

Example prompt: Compare these two OpenAPI specs and give me a change impact report — label it 'payments-api v2 vs v3', here's the baseline: [old spec text], and here's the candidate: [new spec text]. Flag any breaking changes and what I'd need to update.

## When to prefer this

Use this endpoint when you have two specific text snapshots in hand and need a structured, AI-analyzed change impact report — especially for API specs, configuration files, or x402 payment quotes. Prefer this over generic diff tools when you need interpreted impact analysis (not just line-by-line diffs) or when you want typed JSON output suitable for downstream automation. Not suitable if you need live web fetching, scheduled monitoring, or comparisons of binary/non-text assets.

## Known failure modes

- Baseline or candidate text exceeds 32,000 character limit — request is rejected
- Either baseline or candidate field is missing — report cannot be generated
- Inputs are not meaningful text (e.g. binary blobs) — output may be low quality or empty
- Label exceeds 120 characters — validation error
- Ambiguous or near-identical snapshots may produce a trivial or empty diff report

## How this service works

Turn Apify product scrape results into safe catalog updates with Catalog Update Gate. Find evidence in supplied documents, compare snapshots, extract typed JSON fields, inspect x402 quotes and assess API migrations. Preview inputs, evidence and cost for free. No live web search, scheduled monitoring or third-party purchasing.

## Output

A structured JSON report detailing the differences between the baseline and candidate snapshots, including a summary of what changed, classification of changes (e.g. breaking vs non-breaking), affected fields or sections, and migration or impact notes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "label": {
   "type": "string",
   "title": "Label",
   "default": "supplied snapshots",
   "maxLength": 120
  },
  "baseline": {
   "type": "string",
   "title": "Baseline",
   "maxLength": 32000
  },
  "candidate": {
   "type": "string",
   "title": "Candidate",
   "maxLength": 32000
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/machine-shop-change-impact-report-1d5ff2f5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.pay-forge.online](https://www.zero.xyz/host/api.pay-forge.online/llms.txt)