For engineering, AI and data teams
Give customer AI assistants a Brand Agent to call over MCP and REST. It answers only from approved, versioned records synced from your systems, on the AI model you choose.
Request from customer AI
tool: product_availability
sku: "NW-50"
quantity: 120
country: "DE"
Response from your Brand Agent
available: 120 lead_time_weeks: 3 certified: ["VDE"] source: "stock-system" record_version: "v412" approved: true
01 What's changing
Connect your sources once. Every assistant, agent and channel draws on the same approved, versioned records, with access boundaries and a record of every answer.
Your systems
CMS, PIM, CRM and more stay your systems of record. Kodiac syncs from them, read-only.
What Kodiac adds
Versioned records, scoped access, MCP and REST endpoints, and a log of every answer.
02 What Kodiac gives engineering
Use one module or all three, in whatever order suits you.
KODIAC CONTENT
Sync read-only from your CMS, PIM, CRM and more into versioned records with a source and an owner.
Explore Content →KODIAC AGENT
Expose a Brand Agent that AI assistants and agents can call, within the scopes you define.
Explore Agent →KODIAC AUDIT
Compare public AI answers with your approved records, and trace the sources behind them.
Explore Audit →03 Questions you can answer
“Which records answered this question, and which version?”
“What can each AI client access, and what can't it?”
“What happens to the answer when the source changes?”
“Can we switch AI models without losing context?”
“Which interactions conflicted with approved data?”
“How do we add a new source without a big cutover?”
04 Engineering's role
Kodiac sits between your source systems and the AI that uses them. Existing platforms remain systems of record.
Open interfaces
MCP and REST endpoints, with scopes for each client and use.
Traceable answers
Every response is logged with its source records, version and guardrail outcome.
Model choice
Run on a model from Kodiac's validated list, and change it later without losing memory.
05 Enterprise knowledge
Kodiac's memory is built for production: persistent, scoped and governed.
Memory, separate from the model
Persistent memory sits outside the model, so context carries over if you change models.
Controlled writes
Agents propose what to remember. Checks for consent, scope and personal data run before anything is stored.
Scoped reads
Each agent receives only the context it's allowed to use for the task.
Source records stay authoritative
Memory supplies context. Approved records supply the facts. People approve what becomes shared knowledge.
Sector patterns help guide interactions; they never replace your source facts. See how Workspace and Ask Kodiac work →
Walk through the architecture, interfaces and controls with our engineering team.