Google BigQuery
Turn INFORMATION_SCHEMA from an inventory into a contract you can audit.
Quickstart · Get it working.
Your First BigQuery Drift Audit with CoreModels
*Zero to a recorded schema audit of a BigQuery dataset: one SQL query, two HTTP calls, no credentials shared.*
API · Drive it from the Integration API.
The CoreModels BigQuery Integration, Route by Route
*The complete HTTP surface for governing a BigQuery estate: every verb, every role, every payload.*
MCP · Drive it from an agent.
Governing BigQuery from an AI Agent over MCP
*The same import–audit–generate loop, driven by tool calls instead of curl - including how agents ship multi-megabyte extracts.*
Automation · Put it in CI.
A CI Drift Gate for BigQuery: Fail the PR, Not the Dashboard
*Turning the CoreModels schema audit into an automated gate - the v1 API, `errorCount` semantics, the badge, the history trail, and the two directions drift can come from.*
Deep dive · Understand what it does.
Inside the BigQuery Connector: How an Estate Becomes a Governed Graph
*What actually happens between a flat JSON extract and a queryable governed model - identities, type mappings, metadata mixins, audit rules, and the approximations we admit to.*
Why this matters
The case for Google BigQuery — the problem it fixes and what changes when it is fixed — is on coremodels.io.
Read the Google BigQuery guides →