{"uid":"cap_6VVpRb7XsdNPZuDrHOctu","slug":"bigquery-table-schema-change-auditor-7a9b7f81","name":"BigQuery Table Schema Change Auditor","description":"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.","url":"https://market.datapackvibe.com/x402/assistant-schema-bigquery-table-46801318-changes?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"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."}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.01","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.01/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_60z1fwcfItpXLPOVp5z8K","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.01","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"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.","exampleAgentPrompt":"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?","exampleUseCases":[{"title":"Pre-deployment schema change review","prompt":"I'm about to update our BigQuery table definition and want to make sure I haven't broken anything. Here's the current schema JSON and the updated one — can you compare them and flag any new rule violations or removed fields before I deploy?"},{"title":"Debugging a schema regression","prompt":"Something went wrong after we updated our BigQuery table config last week. I have the before and after JSON — can you diff them and tell me which paths changed and what errors got introduced?"},{"title":"Tracking incremental schema evolution","prompt":"I'm iterating on our BigQuery table schema across sprints and want a change log. Can you take this old version and new version of the JSON and report exactly what was added, removed, or modified, plus any errors that were resolved?"}],"resultDescription":"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.","failureModes":["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"],"whenToPreferThis":"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.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-24T00:55:05.906Z","isFirstParty":false,"canonicalSlug":"bigquery-table-schema-change-auditor-7a9b7f81"}