Notre overview
Notre Runtime context compiler, public notre contract, Engine and DB research tracks, MCP as an integration.
On this page
Notre is Caedral's research, development, and innovation program. Notre Runtime is the customer-facing context compiler on the chat path. Notre Engine and Notre DB are separate research tracks. MCP is a protocol those runtimes can speak — not the name of the product.
Public request contract (v1)
Add an optional notre object to POST /v1/chat/completions. The field is stripped before the upstream provider receives your request.
{ "model": "anthropic/claude-haiku-4.5", "messages": [...], "notre": { "mode": "off", "telemetry": false }}| Field | Type | Default | Description |
|---|---|---|---|
| mode | "off" | "auto" | omitted = off | Client intent to use Notre when deployment allows |
| telemetry | boolean | false | Include public notre metadata in non-streaming responses |
Projects
| Project | Status | Docs |
|---|---|---|
| Notre Runtime | Experimental | /docs/notre-runtime |
| MCP integration | Experimental | /docs/notre-mcp |
| Notre Engine | PRE-ALPHA | /docs/notre-engine |
| Notre DB | In development | /docs/notre-db |
Next steps
- Notre Runtime — what the product is, versus MCP as a transport
- Notre quickstart — enable mode and telemetry on a test request
- Modes — off vs auto and deployment behavior
- Telemetry — response fields when telemetry is true
- Product page — /notre/runtime