---
title: "Home"
slug: "home"
type: page
locale: en-US
canonical: "https://www.coremodels.io/"
updatedAt: "2026-10-25T08:53:18+01:00"
---

# Home

## Connect your schemas once. Every agent builds on what your data means.

Import any schema. Map it to the others. Export it to the format each system needs. Give your agents one MCP endpoint to do the same.

[Start a 14-day free trial](https://go.coremodels.io/login?utm_source=www&utm_medium=hero&utm_campaign=site)

Why every agent build

## Agents need one governed model of your data

CoreModels is a governed schema and meaning layer for agents. One model holds types, fields, definitions, allowed values, and how sources map. Platform, data, and AI builders put it in every agent build.

Agents connect to a hosted model over MCP: search, read, validate, export by default; writes need an admin-enabled server so agents consume without owning it.

For: Platform engineers, data architects, and AI builders

1. **Align the model**: Define types, fields, and source maps
   - Without: Agents infer meaning from names and local docs
   - With CoreModels: Import schemas; align fields; AI suggests, humans accept
2. **Build the agent**: Write the agent and its contracts
   - Without: Each agent encodes its own private meaning
   - With CoreModels: Search, read, and export definitions over MCP
3. **Test**: Check payloads and contracts before go-live
   - Without: Mismatches only show up in production
   - With CoreModels: Validate payloads against the governed model
4. **Run**: Agent queries and acts on live data
   - Without: Queries and outputs drift as sources diverge
   - With CoreModels: Agent reads governed definitions before queries or replies
5. **Change**: Update schemas, sources, or allowed values
   - Without: Agents break silently on schema change
   - With CoreModels: Propose changes; find what breaks; humans approve

CoreModels is the governed layer every stage reads from; writes only when admins enable it.

- **One governed model**: Import schemas into one graph of types, fields, definitions, and source maps.
- **Catch breaks early**: See what a schema change breaks before agents hit production.
- **Search before they act**: Agents search, read, validate, and export over MCP before they act.
- **Humans keep control**: Changes are proposed; people approve; the model keeps the record.

Connects: [JSON Schema](https://www.coremodels.io/connector/jsonschema), [dbt](https://www.coremodels.io/connector/dbt), [Snowflake](https://www.coremodels.io/connector/snowflake), [BigQuery](https://www.coremodels.io/connector/bigquery), [Salesforce](https://www.coremodels.io/connector/salesforce), [OWL](https://www.coremodels.io/connector/owl); MCP with Claude, ChatGPT, Cursor, or your own agent

## What teams build on it.

- **AI building: A model agents can build on**: Align the model and Build the agent: import what exists, propose types, generate schema and docs.
- **Structured-data operations: Find breaks before production**: Test and Change: import dbt metadata, audit drift, find what breaks, validate.
- **Grounding: Answers grounded in production meaning**: Run: the agent reads governed definitions before queries or replies.