# GENESIS Agent Tools — GraphQL Breaking Change Detector

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

Analyzes two GraphQL schema versions to detect breaking changes, specifically removed types, and returns a pass/fail compatibility result.

## Facts

- Endpoint: POST https://genesis-agent-tools.genesisagenttools.workers.dev/api/tools/graphql-breaking-change?utm_source=zero.xyz
- Price: $0.01/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-graphql-breaking-change-detector-799a3c7a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BFt2y51F9fDyP80wpqSwa

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-graphql-breaking-change-detector-799a3c7a -d '<json body>'
```

Example prompt: Check whether my updated GraphQL schema is backwards compatible with the old one — here's the previous schema: 'type Query { user: User } type User { id: ID name: String }' and the current schema: 'type Query { user: User } type User { id: ID }'

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call check for GraphQL breaking changes focused specifically on type removal, especially in agent-driven CI/CD workflows or autonomous deployment pipelines that use x402 micropayments on Base USDC. Prefer this over heavier schema diffing tools when cost-per-call matters and you only need a pass/fail signal with removed types listed.

## Known failure modes

- Invalid or unparseable GraphQL schema strings return an error
- Missing 'current' or 'previous' fields in the request body return a validation error
- Payment failure via x402 protocol blocks access before analysis
- Empty schema strings may yield unexpected results or errors
- Schemas with syntax errors may fail to parse and return no meaningful diff

## 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 (true if no breaking changes detected, false if breaking changes exist) and a 'removed_types' array listing any GraphQL types that were removed between the previous and current schema versions.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "pass": {
   "type": "boolean"
  },
  "removed_types": {
   "type": "array"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/genesis-agent-tools-graphql-breaking-change-detector-799a3c7a/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)