# Bounty Engineer Schema Drift Guard

> Bounty Engineer Schema Drift Guard is a paid API for AI agents from bounty-engineer-x402-prod.onrender.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-13).

Compares two API schema versions (before and after) and detects breaking changes, returning a verdict on whether the schema drift is safe or breaking.

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/schema-drift-guard?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bounty-engineer-schema-drift-guard-b4598ba4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sezhc5WMVPC6wltZ_79rU

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 bounty-engineer-schema-drift-guard-b4598ba4 -d '<json body>'
```

Example prompt: Check if the schema change I'm about to deploy is a breaking change — here's the before schema: {"type":"object","properties":{"userId":{"type":"string"}}} and after schema: {"type":"object","properties":{"userId":{"type":"integer"}}}.

## When to prefer this

Choose this endpoint when you need automated, programmatic detection of breaking API schema changes as part of a CI/CD pipeline or pre-deployment check. It is particularly suited for autonomous agent workflows where schema compatibility must be verified without human review, and where you want a structured JSON verdict with a list of specific breaking changes rather than a human-readable diff.

## Known failure modes

- Malformed or missing 'before'/'after' schema objects result in validation errors
- Schemas too complex or deeply nested may produce incomplete analysis
- Payment failure (HTTP 402) if USDC balance is insufficient
- Non-JSON schema formats may not be recognized correctly
- Edge cases in schema evolution (e.g. conditional schemas, oneOf/anyOf) may not be fully analyzed

## How this service works

Machine-buyable infrastructure for autonomous agents: API cost routing, margin optimization, funding-rate data, webpage extraction, result verification, spend controls, retry planning, state, tender search and GitHub bounty intelligence.

## Output

Returns a JSON object with an 'ok' boolean, a 'mode' string set to 'schema_drift_guard', a 'verdict' string (e.g. 'no_breaking_change_detected'), and a 'breaking' array listing any detected breaking changes. If no breaking changes are found, the array is empty.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "object"
  },
  "before": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "mode": "schema_drift_guard",
  "verdict": "no_breaking_change_detected",
  "breaking": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-engineer-schema-drift-guard-b4598ba4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bounty-engineer-x402-prod.onrender.com](https://www.zero.xyz/host/bounty-engineer-x402-prod.onrender.com/llms.txt)