# GENESIS Agent Tools — JSON Schema Drift Detector

> GENESIS Agent Tools — JSON Schema Drift Detector is a paid API for AI agents from genesis-agent-tools.genesisagenttools.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-01).

Compares two JSON schemas to detect breaking changes and API compatibility drift between versions

## Facts

- Endpoint: POST https://genesis-agent-tools.genesisagenttools.workers.dev/api/tools/json-schema-drift?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/genesis-agent-tools-json-schema-drift-detector-123d41ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_s8U-DyIdaZIP7YsQL1uRn

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 genesis-agent-tools-json-schema-drift-detector-123d41ed -d '<json body>'
```

Example prompt: Can you check whether my updated API schema still passes backward compatibility — the current schema has removed the 'userId' field and changed 'amount' from string to number, compared to the previous version that had both?

## When to prefer this

Choose this endpoint when you need a fast, pay-per-call API compatibility check without standing up your own schema diffing infrastructure. Ideal for AI agents that autonomously gate deployments, audit third-party API changes, or enforce compatibility policies in CI/CD pipelines. The x402 micropayment model makes it suitable for low-frequency, on-demand checks.

## Known failure modes

- Missing 'current' or 'previous' fields in request body returns validation error
- Malformed or non-object schemas may cause parsing errors
- Payment failure via x402 protocol blocks request execution
- Ambiguous schema structures may produce conservative (higher) breaking change counts

## How this service works

Pay-per-call x402 APIs for autonomous agents on Base USDC: API compatibility analysis, bounded HTTP/JSON workflows, URL evidence analysis, crypto price consensus, and agent/MCP readiness checks.

## Output

Returns a JSON object with a boolean 'pass' field indicating whether the schema update is backward compatible, and a 'breaking_change_count' number indicating how many breaking changes were detected between the current and previous schemas.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "current",
  "previous"
 ],
 "properties": {
  "current": {
   "type": "object"
  },
  "previous": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "pass": {
   "type": "boolean"
  },
  "breaking_change_count": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/genesis-agent-tools-json-schema-drift-detector-123d41ed/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from genesis-agent-tools.genesisagenttools.workers.dev](https://www.zero.xyz/host/genesis-agent-tools.genesisagenttools.workers.dev/llms.txt)