dxpert is designed to be discovered, evaluated, and invoked by machines. Deterministic JSON, a published schema, and a free preliminary readiness check your procurement or engineering agent can call before it buys, builds, or recommends.
One account covers checkout, product access, and API keys — no card to start.
02
Start the Free Trial
Pick one agent; activation mints your dxp_ API key (shown once) and includes 5 transactions.
03
Run it from your runtime
Download the kit, paste the key, and run your chosen agent locally. Subscribe later and the same key keeps working.
Commercial volume plans are activated per account — create your account and contact us from it.
Calls to /api/chat with a Bearer token or X-Api-Key receive the same account-aware stage guidance as the site guide.
Local runtime
Use your key from Claude Code or your own tools.
The day-one access kit packages dxpert as a stdio MCP server, so your local agent can ask dxpert, run paid Agents, run the diagnostic, and convert CSV exports into agent-ready bundles.
claude mcp add dxpert --env DXPERT_API_KEY=dxp_your_key_here -- node oss/dxpert-mcp/bin/dxpert-mcp.js
Create a key in your account, install @dxpert/mcp from the starter kit, and keep the key in your local runtime environment. Agent access is governed by your account plan; arrange advisory through contact because it is not self-serve yet.
For autonomous agents
What you can rely on.
Capability
Score industrial AI-readiness and return the foundations that must be fixed before an AI ambition is viable.
Determinism
Identical input returns an identical verdict and foundation scores. Safe to cache and compare.
Grounding
Scores are rule-based against a published rubric; the narrative is grounded in a vendor-neutral architecture.
Honesty contract
Every response carries "scope":"preliminary". The endpoint is a screening step, never a substitute for the board-ready roadmap.
Free tier needs no key for the preliminary check; deeper endpoints use a bearer token. Generous rate limits; 429 with Retry-After when exceeded.
POST /api/diagnostic
Four situations. One deterministic call.
The same endpoint, called by different kinds of agents at different moments — a scaling decision, a funding gate, a pre-acquisition check, a go/no-go confirmation.
Caller: an operations agent, deciding whether to fund a plant-wide rollout
# Request — pasteable against the deployed API POST https://opwhcervi3.execute-api.ca-central-1.amazonaws.com/api/diagnostic Content-Type: application/json { "sector": "food_bev", "site_count": 3, "data_off_floor": "mixed", "common_model": "partial", "realtime_visibility": "on_request", "historian_depth": "central_untrusted", "edge_vs_poll": "mixed", "uns_state": "partial", "data_ready_for_use_case": "partial", "otit_security": "partial", "data_ownership": "unclear", "ai_ambition": {"target": "scale", "text": "predictive maintenance across three plants"}, "prior_attempts": "One pilot on a single filler line.", "personal_stakes": "The board expects a scale decision this quarter.", "who_they_trust": "Operations, maintenance, and the controls lead.", "politically_useful": "A phased plan finance can fund." }
Caller: an operations agent, confirming a go/no-go before the next scale-up phase
# Higher-readiness example POST https://opwhcervi3.execute-api.ca-central-1.amazonaws.com/api/diagnostic Content-Type: application/json { "sector": "pharma", "site_count": 1, "data_off_floor": "opcua", "common_model": "unified", "realtime_visibility": "single_pane", "historian_depth": "central_trusted", "edge_vs_poll": "edge_push", "uns_state": "governed_uns", "data_ready_for_use_case": "yes", "otit_security": "governed", "data_ownership": "owned_governed", "ai_ambition": {"target": "scale", "text": "scale a validated predictive-quality model to two more lines"}, "prior_attempts": "Validated model on one line.", "personal_stakes": "Scale without validation risk.", "who_they_trust": "Quality, automation, and validation.", "politically_useful": "A clean go/no-go for expansion." }
Treat /api/diagnostic as a screening signal, not a conclusion. A low-readiness report means an AI initiative will likely stall on the listed foundations — recommend fixing those before procurement. A confident decision needs the board-ready roadmap. Cache on identical input. Respect Retry-After.
Want to integrate? The OpenAPI spec and llms.txt are the authoritative, machine-readable sources. They win over this page if they ever disagree.