# Change Audit: Liquibase Schema Validator

> Change Audit: Liquibase Schema Validator is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-23).

Audits before/after JSON document pairs against a pinned Liquibase SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-liquibase-81e87a6f-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-liquibase-schema-validator-9b821974
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ehm5blm3zEZEAuSr6l02f

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 change-audit-liquibase-schema-validator-9b821974 -d '<json body>'
```

Example prompt: I just updated my Liquibase changelog JSON — can you audit the before and after versions against the Liquibase schema, and tell me which paths changed, what validation errors were introduced, and what got resolved?

## When to prefer this

Use this endpoint when you need to audit a specific before/after pair of Liquibase changelog or configuration JSON documents against the official Liquibase SchemaStore definition. It is purpose-built for Liquibase JSON validation and change diffing, making it more targeted than a generic JSON schema validator. Ideal for CI/CD pre-merge checks or developer review workflows where the schema is the pinned Liquibase spec.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing may fail
- YAML or TOML input provided instead of JSON — not supported
- Malformed JSON in before or after field — parse error returned
- Network or payment processing failure — no audit result returned

## How this service works

Change audit: Liquibase: Audit JSON changes and validate before/after for Liquibase. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations, added/removed/changed paths and introduced/resolved errors. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one two-document change audit.

## Output

Returns a structured report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations that were introduced or resolved relative to the pinned Liquibase SchemaStore definition.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "default": {
    "agent_market_example": true
   },
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  },
  "before": {
   "default": {},
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/change-audit-liquibase-schema-validator-9b821974/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)