What is TruDI?
TruDI (TruData Intelligence) is TruRating's AI data analyst. It lets an AI assistant you already use analyze your TruRating in-store checkout feedback, so you can ask questions in plain language instead of building a report.
At payment, customers answer one question on the card terminal: about staff, service, the store or your own topics. Each answer is linked to the transaction. TruDI can answer questions such as:
- "Which stores had the weakest staff ratings last month?"
- "How do weekend ratings compare with weekdays across our regions?"
- "Which of our questions has the biggest link to customer spend?"
TruDI only reads data. Every query is limited to the organization, or organizations, that your access allows.
The MCP server
TruDI is delivered as an MCP server. MCP (Model Context Protocol) is the open standard AI assistants use to connect to outside tools and data. You add TruDI to your assistant once, and the assistant then calls TruDI's tools on your behalf, runs the analysis and writes the answer. Charts appear inline in clients that support them.
Every request to the server needs a credential. There is no anonymous access.
Which clients can I use?
| Client | Where to find the setup |
|---|---|
| Claude (web and Desktop) and Claude Code | Claude |
| Microsoft Copilot Studio | Microsoft Copilot Studio |
| GitHub Copilot in VS Code | GitHub Copilot in VS Code |
| Gemini CLI | Gemini CLI |
| Gemini Enterprise | Gemini Enterprise |
| Your own agent or backend | Your own agent |
Other MCP clients, such as ChatGPT and Cursor, also work with TruDI but have no dedicated guide here. The same endpoint and authentication modes apply. Which clients can sign in as a person and which need an API key is set out in Authentication Modes.
Three ways to authenticate
| Mode | Use it when | Acts as |
|---|---|---|
| Sign in | People ask TruDI questions in a client that supports sign-in, such as Claude, VS Code or Gemini CLI. | The individual person, with their own TruHub access. |
| API key | A shared agent, or a tool that can't sign in, such as Microsoft Copilot Studio or Gemini Enterprise. | Your organization, shared by everyone using that key. |
| Client credentials | Your own server-side code, backend or agent framework calls TruDI. | Your organization, with no person involved. |
Sign-in is the better choice wherever a client supports it, because each person sees only what their own TruHub access allows and what they ask is attributable to them. An API key or client credentials identify your organization, not a person. The full detail, including token lifetimes, revocation and security implications, is in the secure pages.
Getting access
The setup guides and reference pages are in the secure section of this portal. Sign in to the portal and request access to the secure documentation, or ask your TruRating customer success director (CSD) or account manager.
Once you can see them, start with Authentication Modes, then Getting Access for what to ask TruRating to switch on for your organization.