Ask with MCP
Give your approved AI assistant access to Auditi context. Find information, get answers and take permitted actions through natural conversation.
Explore AI & MCPAI & Integrations
Connect Auditi to the systems and AI assistants your firm already uses. Keep information in sync, act on updates and bring audit context into everyday work.
Explore the possibilitiesAn open platform
Ask a question, connect a system or respond to a change. Use each capability on its own, or combine them into a workflow that fits your firm.
Give your approved AI assistant access to Auditi context. Find information, get answers and take permitted actions through natural conversation.
Explore AI & MCPConnect Auditi to the systems your firm relies on. Share data, keep records in sync and build Auditi into your internal tools and processes.
Explore the Enterprise APILet a change in Auditi start the next step elsewhere. Notify your team, trigger a workflow or tell a connected system it is time to update.
Explore webhooksAI & MCP
Work with the assistant your firm has approved, using current context from Auditi. Requests, files, comments and evidence stay in your client workspace. Your assistant connects to the information it is allowed to use.
Connect ChatGPT, Claude or an internal model where supported, without forcing work through an Auditi-only model. Your firm keeps control of the assistant choice, data access and processing path.
Keep access limited to the right people and audit work. Role-based access, tenant scoping, logs, source evidence and human review stay part of the workflow.
Connected under your firm’s rules
Audit context
Brief your assistant as you would a colleague. See what needs attention, prepare a client response or update a request through natural conversation.
See more AI use casesYou
Which PBC requests need my attention?
Using Auditi context
These three requests are overdue in the audits you can access.
| Client / request | Overdue |
|---|---|
| Northbridge Ltd Loan schedule | 3 days |
| Westfield Group Bank confirmation support | 2 days |
| Oakwell Ltd Final trial balance | 1 day |
Sources: 3 Auditi requests
Enterprise API
The Enterprise API lets your systems exchange information with Auditi. Connect client data, move documents into your filing process or bring engagement status into firm-wide reporting.
Your IT team can build the connection around the way your firm works, reducing manual handoffs and the need to enter the same information in several systems.
Discuss a workflow with usExample API workflow
Files linked to the right client and request
Retrieve files and context through the Enterprise API
File documents according to your firm’s process
Evidence where your team needs it
Build connections between Auditi and the systems your firm relies on, from client data and documents to reporting, internal tools and everyday workflows.
Webhooks
Webhooks notify your systems when something happens in Auditi. For example, use webhooks to inform your team or combine webhooks with the Enterprise API to refresh reports.
In Auditi
Your client workspace
Northbridge Ltd · Audit 2026
Loan schedule.xlsx
Loan schedule · Financing
A client adds a file to a request.
In your systems
Choose an example to see what happens next.
Webhook notification
Send document updates to the audit team’s Slack or Teams channel, so everyone knows what has arrived.
Let me know when the loan schedule comes in.
Loan schedule.xlsx was added.
Northbridge Ltd · Audit 2026
Request: Loan schedule · Financing
Microsoft
Our Enterprise API, webhooks and MCP give your team the building blocks to connect your Microsoft tools. Keep documents, alerts and reporting in the tools your firm already uses.
Auditi also supports Microsoft Entra ID.
File completed PBC exports in the right engagement library, including documents and the audit trail your team needs.
Start a flow from a webhook, or call the Enterprise API from a flow your firm maintains.
Bring engagement and request data into your firm’s reporting through a custom data connection.
Route an Auditi event to the channel responsible for that client, so the team knows what needs attention.
Connect Copilot to Auditi through MCP. Ask questions and take permitted actions using your current audit context.
FAQ
Your firm brings its own approved assistant. Auditi provides access to audit context through MCP. The assistant runs in your chosen AI environment, with the access and processing arrangements your firm approves.
Auditi does not use customer data to train AI models without explicit opt-in and governance approval. Your firm should also review and approve the data processing and training terms of any connected AI provider.
With the right permissions, your AI assistant can take actions like creating or updating requests, assigning people, changing due dates and adding comments.
Yes. Role-based permissions and scoping to your firm’s environment govern access to Auditi data. Your setup determines what the assistant may read and which actions it is allowed to take.
You can connect any AI assistant that supports MCP, including ChatGPT, Claude and Microsoft Copilot. Your firm chooses the assistant it wants to use.
MCP access is included in Auditi’s Enterprise plan.
Connecting an AI assistant is optional. Your firm can use Auditi without MCP.
Auditi provides an Enterprise API, webhooks and MCP for connections configured around your firm. The workflows on this page are examples of what can be built, rather than a catalogue of prebuilt integrations.
Your IT team builds and maintains the connection. Auditi can discuss the available capabilities and help your team assess how they fit the workflow you have in mind.
Potential connections include audit suites, CRM and ERP systems, document management, reporting platforms, spreadsheets and workflow tools. What is possible depends on supported Auditi operations and the other system’s capabilities.
The Enterprise API is available on Auditi’s Enterprise plan, alongside webhooks and MCP. Contact us to discuss Enterprise access and the documentation your IT team needs.
Webhooks are included in Auditi’s Enterprise plan, alongside the Enterprise API and MCP.
The API lets a connected system request information or perform a supported action in Auditi. A webhook tells a connected system that something has happened. A workflow can use the webhook as its trigger, then call the API for the next step.
Events cover areas such as audits, clients, users, confirmations, responses, reviews and samples. Each documented event explains what triggers it and the information it carries. Your team can choose the events relevant to its workflow.
Your firm can configure a connection that receives an Auditi event and posts an alert to the appropriate channel. The routing and message are handled by your workflow or automation tool.
A webhook can signal that a relevant event has happened, such as a PBC list being archived. Your configured workflow can then notify the team or use the API to retrieve documents and pass them to your DMS.
Jan, Svenja and Daniel from Auditi will get back to you right away.
Requests, files and comments stay together in Auditi, so clients know where to act and your team keeps the context.
Connect filing, reporting and notifications to the systems your team already uses, with fewer manual handoffs.
Bring current Auditi information into your approved assistant, with the access and review process your firm controls.