Scans and mixed formats.
Files arrive as scans, spreadsheets and email attachments. An agent that cannot read the page cannot cite it.
BiltIQ structured data for AI is the data-preparation service behind Agent OS and Learning OS. BiltIQ engineers turn a buyer's documents and records into inputs the products can use: loaded files and written checklists for Agent OS, connectors over MCP, and the assigned course books for the AI Teacher. It is scoped and priced per project.
We'll walk you through it on sample data.
Files arrive as scans, spreadsheets and email attachments. An agent that cannot read the page cannot cite it.
A checklist that exists only in a senior reviewer's memory cannot be tested. We write it down with you, as agent checks.
Agents that need a status from your ERP need a connector, not a copy of the database.
Your past files loaded (30+ formats by design, scans included); your checklist and rules written as agent checks; connectors to your systems over MCP, built per deployment.
The course books your institution assigns, loaded so the AI Teacher can cite chapter and page; the student list and coordinator for the trial from Apr 2027 (targeted).
Opening balances set at go-live; inventory, production BOMs and HR attendance imported from Excel/CSV. A direct Tally or Zoho importer is on the roadmap.
On your GPU server or a BiltIQ loaner, on site. Outbound calls are blocked by default (platform gate). If you have no server, the pilot can run on our India cluster under NDA.
Not installed on your premises today. LMS course files sit in AWS cloud storage (India region). LMS quizzes use a local open model first, with a cloud fallback (Kimi) that is on by default and can be switched off. AI Teacher embeddings, vision and voice default to cloud services and can be repointed.
Database on your network on an Own-it install; files and attachments in GCS or S3 cloud storage today. On-prem file storage is on our roadmap. No Claude or OpenAI calls; the Kimi cloud-model option is off by default.
We look at a sample of your files with you and agree what the product needs.
For Agent OS, preparing your past files is part of the 4–6 week pilot.
The pilot report lists what your AI caught, what it missed and which data problems caused misses.
Under the managed service, agent tuning covers new checklists as your rules change.
There is no list price for preparing data for your AI. Larger work is quoted per scope, in writing, after the scoping call.
AI-ready data is information your AI can find, read and act on reliably: files it can load and cite, rules written down as checks it can test, and connectors to the systems it must query. For BiltIQ, that means inputs for Agent OS and the AI Teacher in Learning OS, prepared by BiltIQ engineers and tested against your own manual results.
No. For an Agent OS pilot, BiltIQ loads your past files as they are, scans included, and writes your checklist into the agents. The findings report then shows what your AI caught, what it missed and which data problems caused the misses. You fix what matters before the licence decision, not before the first call.
Agent OS pilot documents stay on your server, a BiltIQ loaner or, under NDA, BiltIQ's India cluster. Learning OS cannot be installed on-premises today: LMS files sit in AWS (India region), its quiz Kimi fallback is on by default (can be switched off), and AI Teacher embeddings, vision and voice default to cloud (can be repointed). Business OS keeps files in GCS or S3, with Kimi off by default.
MCP, the Model Context Protocol, is an open standard for letting software agents, including your AI agents, call tools and read data in other systems. In BiltIQ Agent OS, the Connect feature speaks MCP, and BiltIQ engineers build each connector per deployment, so your AI agents can query your ERP or document store without a copy of the whole database.
We'll walk you through it on sample data.