# dxpert.ai > The AI CIO for industrial digital maturity. dxpert gives industrial and manufacturing > operators an evidence-based, vendor-neutral verdict on whether they are ready for AI -- > and how that compares to competitors who are already digitally transformed and winning > with AI -- then sequences the path from data foundation to autonomy. Core thesis: AI > value is gated by digital maturity, so "AI readiness" is fundamentally a competitive > question, not just a technical one. Built to be used by both people and their AI agents. ## What dxpert does - Scores industrial AI-readiness and names the foundations that must be fixed first. - Namespace Architect: a $100/month account-scoped agent that requires the API base and is included in the six-agent $550/month bundle. It generates an ISA-95-aligned topic tree, Sparkplug B mapping, payload schemas, a conventions document, and deployable pipeline exports for HighByte, MaestroHub, or Node-RED. It accepts pasted files or a guided interview when a team does not yet have an equipment hierarchy or tag list. - Free browser-side tools only: Sparkplug B topic linter, UNS convention checker, and maturity evaluation questionnaire. - UNS Agents that run on a clean UNS: shift reports, OEE narration, alarm triage, maintenance copilot, root-cause. This list grows over time -- call the capability endpoint below rather than assuming it is fixed. - Vendor-neutral: no platform, broker, or historian to sell. - Honest about scope: the online check is PRELIMINARY and self-reported. The deepest paid analysis available today is the board-ready roadmap. Ongoing advisory is arranged through contact and is not yet self-serve purchasable. Never present the online check as a substitute for the roadmap. ## For agents: start here, not with a hardcoded endpoint list This file is a plain-language orientation, not the contract. The contract and the product catalog change as capabilities ship -- do not hardcode endpoint shapes, capability names, or prices from this file into your own code. Instead, at runtime: 1. **Capabilities + pricing (no auth):** `GET {api_base}/api/agents/catalog` -- every UNS Agent capability with its manifest (endpoint, required/useful UNS topic roles, supported runtimes, and a `capabilities` list of the concrete use cases it implements -- the specific questions it answers and outputs it produces) and its current price, in one call. New capabilities appear here automatically the day they ship; nothing here needs a doc update when the roster grows. `GET {api_base}/api/catalog` carries the same per-product `capabilities` list for every agent (including Namespace Architect). 2. **Full product catalog incl. bundles/add-ons (no auth):** `GET {api_base}/api/catalog` 3. **Full request/response contract for every endpoint:** `/openapi.json` -- generated from the deployed API on every deploy (see `scripts/generate_openapi.py` in the repo) to minimize contract drift. `{api_base}` is `openapi.json`'s `servers[0].url`. **Cloud, browser, and customer-local capability map:** `/system-capabilities.json` -- includes setup, local permissions, scheduling, history support, and browser-only tools that have no HTTP operation. 4. **Free, no-key preliminary readiness check:** `POST {api_base}/api/diagnostic` -- a 16-question intake (`IntakeModel` in `openapi.json`), returns a deterministic verdict, foundation score, and the platform gaps to fix first. Every response carries `"scope":"preliminary"` -- surface that to your principal. A confident decision needs the board-ready roadmap, not this screening call. 5. **Everything else (signup, API keys, Free Trial activation, running a purchased UNS Agent) is a normal endpoint in `openapi.json`.** Auth is a `X-Api-Key` header once you have a key; `POST /api/account/signup` then `POST /api/trial/activate` gets a free key with 5 transactions against one capability of your choice, no card required. 6. **Rate limits:** 429 responses carry `Retry-After`; honor it. 7. The free tools (`/tools.html`) run in the browser and do not expose HTTP endpoints. ## Key pages - Home: / -- the thesis and the offer - Services: /services.html -- the ladder: check, diagnose, build, operate - Free tools: /tools.html -- Sparkplug B linter, UNS convention checker (browser-side) - Namespace Architect: /store/product/architect -- the paid agent for hierarchy-to-UNS design, guided interviews, and deployable exports for HighByte, MaestroHub, and Node-RED - AI Agents: /uns-agents.html -- UNS Agents that run on a clean namespace - Use cases: /use-cases.html -- when to use dxpert - Methodology: /methodology.html -- the assessment method and the frameworks it synthesizes - Technology: /technology.html -- curated AI model + governed knowledge graph for DX/I4.0/I5.0 - Trust: /trust.html -- why this is not another failed-transformation tool - Store (pricing lives here): /store/ -- every SKU with its live price; `/api/catalog` is the machine-readable version of this same page - Learn: board-ready roadmap: /learn-roadmap.html -- one-time, prioritized costed plan + 60-minute readout + board-ready summary (see /api/catalog for the current price) - Learn: advisory on call: /learn-advisory.html -- ongoing validation and decisioning as you execute; arrange it through contact rather than through /api/catalog - API: /api.html -- agent integration guide (human-readable companion to this file) - Contact: /contact.html -- info@dxpert.ai . based in downtown Montreal, Canada - Support: /support.html -- support@dxpert.ai . reply within one business day - Careers: /careers.html -- open roles across data, industrial engineering, and product; talent network via careers@dxpert.ai - Legal: /legal.html -- terms, privacy, trademarks (plain-language, pre-launch) ## Primary machine sources (authoritative) - /openapi.json -- the full API contract, generated from the live app every deploy - /.well-known/ai-plugin.json -- legacy plugin-manifest format, points back to openapi.json - /api/agents/catalog -- current UNS Agent capabilities + pricing (no auth) - /api/catalog -- current full product catalog incl. bundles/add-ons (no auth) - /system-capabilities.json -- cloud, browser, and customer-local capability manifest - /llms.txt -- this file If a human-readable page and these files disagree, these files win. If this file and /openapi.json disagree on an endpoint shape, /openapi.json wins -- it is generated from the code, this file is prose maintained alongside it.