Connect your AI
Your fleet data, inside the AI you already use.
Claude, ChatGPT, Mistral Le Chat, Lovable, Cursor, your own agents: anything that speaks MCP can read your daXos data directly. One address, one access key, no integration project. Included in The Hub, never sold separately.
https://mcp.daxosdigit.com/mcp
Issued by daXos to each person who connects, sent privately, shown once. It starts with dxk_. Ask us at info@daXosdigit.com.
How to connect
Two minutes, in the app you choose.
Every app adds a "custom connector" or "MCP server" in its settings. Paste the server URL. A daXos sign-in page opens: paste your access key and press Connect. The app never sees the key again; it gets a short-lived token instead.
claude.ai and Claude desktop
Settings → Connectors → Add custom connector. Paste the URL, leave the OAuth fields empty, then sign in with your key on the daXos page.
ChatGPT
Add a custom MCP connector where your ChatGPT plan offers one, with the URL. ChatGPT runs the sign-in itself; paste your key on the daXos page.
Le Chat
Connectors → add a custom MCP connector → the URL. Choose OAuth and sign in with your key, or choose API key / Bearer and paste the key itself.
Lovable
Connectors → custom MCP server → the URL. OAuth with your key, or a Bearer token equal to the key.
Cursor, VS Code, Claude Code
Add the URL as a remote MCP server. They run the sign-in flow on their own and open the daXos page for your key.
Your own code
Streamable HTTP on the same URL, with the header Authorization: Bearer <your key>. Works with any MCP SDK or agent framework.
What your AI can read
Five tools. Your devices only. Read-only.
Your AI sees what daXos measured, as received and as validated, so it can show its working. It cannot change anything: no settings, no device, no vehicle.
Your fleet
Every device on your account, your own labels, whether it is connected, when it last reported, the sensors it carries and which records it has.
Right now
The last known position and speed of a device, and the latest reading of each of its sensors: temperature, humidity, tilt.
As measured
The raw record before any validation: GPS fixes with 3-axis acceleration, every sensor packet, every vehicle-bus reading, each with the flag our pipeline gave it.
As validated
What survived daXos validation: fixes with longitudinal and lateral acceleration in the vehicle's own frame, the cleaned sensor series, and only the vehicle readings that passed every check.
The working
For one trip, how the data was validated: how the sensor axes were matched to the vehicle, vibration levels, how many readings were rejected and why.
Try these
"Which units have not reported since this morning?" · "What temperature is the load in van 12 at now?" · "Find the hardest braking on yesterday's trips for unit 4." · "How many fixes were rejected on that trip, and why?"
Or call the API
The same data, as plain URLs.
For software rather than conversation: a TMS, a dashboard, a nightly report, an automation tool (Zapier, Make, n8n, Power Automate), or an assistant that works from an OpenAPI description. The same five reads, the same access key, the same rules. Read-only.
https://mcp.daxosdigit.com/v1
Reference: mcp.daxosdigit.com/v1/docs · OpenAPI 3.1: /v1/openapi.json
curl -H "Authorization: Bearer dxk_…" https://mcp.daxosdigit.com/v1/devices
Add ?format=csv to any list endpoint for a file Excel opens. Windows take unix seconds or ISO 8601; pages follow next_cursor.
Your fleet
The devices your key may read, with their labels, pods and what each one records.
Right now
Last position and the latest reading of every sensor and vehicle-bus parameter.
As measured · as validated
kind=fixes|
Security and your data
- Your data and no one else's. A key belongs to one person on one account and reaches that account's devices only. Any other device answers "not found".
- Standard sign-in. OAuth 2.1 as the MCP specification defines it, with PKCE. Apps that sign in this way receive tokens that expire within the hour, never your key.
- Keys we cannot read back. We store a fingerprint of each key, not the key. Lose it and we issue a new one.
- Revoke in one step. Revoking a key ends it, and every app connected with it, on the next request.
- Every call logged. Which key, which tool, when and how much data, so you can ask us who read what.
- Encrypted in transit. HTTPS only, on our own host in the United States.
One thing to be clear about: what your AI reads from daXos then passes to the company behind that AI, under your agreement with them. Choose the assistant and plan whose data terms suit you. On our side nothing changes: retention, deletion and the AI-training line are those of our Privacy page and the DPA, where your MCP endpoint is already covered.
Questions
Does it cost extra? No. API and MCP access are part of The Hub's base rate, as on the pricing page.
Which AI can I use? Any app or agent that can connect to a remote MCP server with OAuth or a Bearer token. The ones above are the ones we have documented; others work the same way.
MCP or API? MCP when a person talks to an AI about the fleet: the AI discovers the tools itself. The API when software asks on a schedule, or a tool wants an OpenAPI description. Same key, same data, same log; use both if you like.
Several people on my team? Each person gets their own key, so each can be revoked alone and the log shows who read what.
Can I try it before buying? Yes. Write to info@daXosdigit.com for demo access on a daXos unit in service, or start the free trial and connect your AI to your own routes.
Get your access key
info@daXosdigit.com
Tell us who will connect and from which app. The key reaches that person privately.