Trust what AI tells you about your Odoo.

It is the meaning system between an AI and Odoo. An AI plugged into Odoo can read records; the context layer explains what they mean and how to use them: which records count, which fields are misleading, how tables join, and whether an intended action is safe. The AI loads that context before it reads or writes anything.

Because reaching your records is not the same as understanding them. However you plugged the AI in, through MCP or tools, it can read and write Odoo data but cannot see which records count, which fields mislead, or whether an action is safe. It follows a technically valid field or join and answers the wrong business question. The context layer supplies exactly that missing meaning, so access becomes understanding.

No. Documentation describes what Odoo generally does; it does not know your version, your modules, or your customizations. Every entry in the context layer carries evidence, executable applicability checks, and a confidence level, so meaning is proven for your setup, never pasted from a manual.

No. Odoo remains the authority for permissions and execution. The context layer supplies interpretation and safety context on top: it can warn that an intended action looks risky, but it never bypasses or replaces access rights, record rules, or business methods.

Early access targets Odoo 19, Community and Enterprise. It releases 171 verified entries across focused coverage: Accounting, Sales and Inventory, Purchase and Purchase-to-Accounting, Sales-to-Fulfillment, CRM, Manufacturing, and Project, Timesheets and Helpdesk. Every entry is qualified through release-day and current Odoo 19 anchors, with edition and module applicability enforced, so some entries apply only to one edition (Helpdesk is Enterprise-only, for example). That is focused coverage verified against Odoo 19, not complete coverage of any module, and Odoo 19 is the only current version target. We state exactly what is proven, never "all modules supported".

Every entry carries evidence and executable checks that run against real Odoo 19. An entry is only called verified after it passes its full release policy, including live checks and human review where needed, never because a language model judged its own output. Confidence is tracked separately from verification: sounding sure is not the same as being right. Released entries are immutable and hash-verified against release locks before serving, so pinning a release means the meaning does not shift under you.

No. Our own products consume it first, and it is model-independent by design and works however your AI reaches Odoo, so external AI stacks, agents, and Odoo-native tools can consume the same contracts. One verified layer of meaning, whatever is asking.

Yes, that is exactly the case it is built for. An Odoo connection is not Odoo understanding. Whatever the model, and whether it reaches Odoo through the official MCP server, a third-party one, or your own custom workflow, it can follow a technically valid field or join and still answer the wrong business question: returning the customer on partner_id when you asked for the salesperson, counting draft quotes as purchases, or reading on-hand stock as available to sell. The context layer supplies the verified business meaning the model was never given, alongside the setup you already have. It advises on company scope and write risk; Odoo still decides which records a user may see.

Yes, a fair three-arm design: strong raw Odoo tools with schema, then the same setup plus the context layer, holding the model, permissions, and tasks constant so only the context differs. Live model runs exist, but independent blind human scoring is still pending, so we publish no accuracy figure, chart, or "gate passed" claim yet.

Yes, and it is public today. The open standard lives at github.com/Nantiai/ocl-standard under Apache-2.0: the experimental specification (v0), JSON Schemas, a validator, conformance tests, reference Python and TypeScript source clients, ten candidate example entries, and an example MCP server. You can read, validate, and produce entries without our registry. The clients are source, not published PyPI or npm packages yet, and the verified registry itself is the commercial product.

Yes. The verified runtime is live at api.context.nanti.ai. Try one verified decision with no login at api.context.nanti.ai/demo/revenue, then start a free 7-day trial at api.context.nanti.ai/request-access. It takes one email, with no verification step and no sales call, and an active seven-day key appears on the next screen. The key is universal: one Bearer token that covers both Odoo 19 editions, all released modules, every operation, and every interface (MCP, REST, Codex, Claude Code, Python). It never asks for Odoo credentials or customer data. The trial runs without a request-count meter, though burst, context-size, and anti-extraction limits still apply, the 171-entry registry is not downloadable or enumerable, and there is no production SLA during early access.

The hosted runtime does not. It asks for no Odoo credentials and never reads your database. It returns verified meaning about Odoo 19: which records count, which fields mislead, how they join, and whether an action is safe. Your own AI then reads the real records the way it already does, through MCP or tools, under your real permissions. There is an optional local metadata collector, opt-in and separate, that can read allowlisted Odoo metadata to tune context for your instance; if you use it, its Odoo credential stays on your side. Meaning is verified against Odoo 19, not against your specific instance, so custom modules, localizations, company, and currency can still change the answer.

Now. The open standard is public today: clone github.com/Nantiai/ocl-standard, run the CLI, and wire the example MCP server (get_context, resolve_noun, explain_field) over ten candidate example entries in minutes, with no key and no account. The verified 171-entry runtime is live too, in early access: try the no-login demo at api.context.nanti.ai/demo/revenue, then start a free 7-day trial with one email for a universal key, and call all five operations over REST or remote MCP beside however your AI already reaches Odoo.