# BigQuery Table Schema Change Auditor

> BigQuery Table Schema Change Auditor 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-24).

Audits JSON changes between before/after BigQuery table schema documents, validating both against a pinned SchemaStore definition and reporting added, removed, or changed JSON paths along with introduced or resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-bigquery-table-46801318-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bigquery-table-schema-change-auditor-7a9b7f81
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6VVpRb7XsdNPZuDrHOctu

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 bigquery-table-schema-change-auditor-7a9b7f81 -d '<json body>'
```

Example prompt: Can you audit my BigQuery table schema change — here's the before JSON and the after JSON — and tell me what fields were added, removed, or changed, and whether any new validation errors were introduced?

## When to prefer this

Choose this endpoint when you need to specifically audit and diff BigQuery table schema JSON documents using a pinned SchemaStore reference, especially to catch introduced errors before applying a change. It is more targeted than a generic JSON diff tool because it applies BigQuery-specific schema rules and reports violations, not just structural differences.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted (non-parseable) — parse error returned
- Malformed request body missing before or after fields — validation error
- Network or payment authorization failure — request not processed

## How this service works

Change audit: bigquery-table: Audit JSON changes and validate before/after for bigquery-table. 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 audit report including JSON pointers for all added, removed, and changed paths between the before and after documents, a list of rule violations found in each, and a summary of errors introduced or resolved by the change — all based on the pinned SchemaStore definition for bigquery-table.

## 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/bigquery-table-schema-change-auditor-7a9b7f81/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)