Questions
The questions people ask before they connect.
What you need, what is free, how the connection works, and how to review the results.
How does the free trial work?
Try Starter, Team, Company or Company Plus free for 14 days. No credit card required. The trial starts when you complete signup and accept the terms. One self-service trial is available per organization. Free has no expiry. Enterprise is contact-led.
Will I be charged when the trial ends?
Starting a no-card trial does not authorize a charge. To continue paid access, explicitly subscribe or arrange approved invoice billing. Otherwise, your organization returns to Free when the trial ends. Saved configuration remains, but Free limits and pack access apply. Open Subscription in the console to review the price and first charge date before confirming payment. Choosing a plan does not restart the trial.
Which billing options are available?
Starter and Team use card billing. Company and Company Plus support card billing or an approved invoice arrangement. Enterprise requires contacting us. A pending invoice request does not activate paid access. AI-provider charges and custom development are separate.
What do we need to get started?
An Epicor administrator, access to the required Epicor REST APIs, the Cutova solution package, and a compatible AI assistant. Your administrator registers the instance and publishes tools or installs a pack with its prerequisites. Each user then connects and authorizes access.
What is free?
Free includes one Epicor user, one instance and seven enabled tools. Executive Insights is free with every tier. Install the pack and its Epicor prerequisites before asking questions. Kinetic Uplift, BAQ Builder and Epicor Functions are included with any paid plan.
Do we have to switch assistants?
Your team can keep using a compatible assistant. An administrator uses the Cutova console for setup and tool selection. Each person authorizes the connection in their assistant.
Does Cutova get our Epicor passwords?
Cutova does not receive end-user Epicor passwords during sign-in. It stores the administrator-configured service account username, password and API key encrypted with AES-256-GCM. Epicor tool calls use that connection with the signed-in user's identity through impersonation.
Who receives our Epicor data?
Tool results return through Cutova to your chosen AI client and provider. Their handling is governed by your agreement and settings. An administrator can enable the optional AI schema-description helper after reviewing the provider and data terms. It sends schema metadata to that provider. Request values and credentials are excluded from diagnostic logging, and error details are redacted. See the security page for data handling.
Can it write to Epicor, or only read?
Both. Administrators choose tools, including any tools supplied by installed packs. Writes use the configured Epicor APIs and their applicable server-side controls. Configure approval prompts in your AI client for the workflow you want to allow. Choose the approval settings for your workflow and review generated changes in a sandbox before using them in production.
Can the assistant still get an answer wrong?
Yes. Live Epicor data gives the assistant evidence to work from, but its interpretation can still be wrong. Check the query, calculations and conclusions before acting.
Which AI assistants work with it?
We publish setup guides for Claude, ChatGPT, VS Code, Microsoft Copilot Studio and LibreChat. Other MCP clients may connect through remote Streamable HTTP. Authentication, Skills, file handling and interactive MCP Apps vary by client and settings. Check the connection guide for your client.
Which Epicor releases and interfaces can we use?
Cutova connects through Epicor REST APIs, rather than the screen interface. Availability depends on your release, authentication setup, and the APIs and Functions a tool needs. Classic authentication and Kinetic UX have different setup paths. Tell us your release and use case so we can check the prerequisites.
What about an instance behind a firewall?
The optional on-premise gateway opens an outbound connection to Cutova. It does not require an inbound firewall port for the gateway connection. Your administrator configures which Epicor host it can reach.
Do we need developers?
Publishing an existing BAQ is configuration. Packs provide tools and guidance for a specific job. An administrator still needs to install the prerequisites, and new business logic or a custom workflow may need development.
What is a tool?
One capability the assistant can call, such as an Epicor BAQ, Business Object or Function. Your published tools and installed packs determine the available work.
Am I limited to the available Skill Packs?
No. Packs give you tools and guidance for a starting point. You can publish your own BAQs, Business Objects and Epicor Functions as tools, then combine tools and instructions into your own workflows or packs. Add the capabilities your work needs. Your plan determines how many tools you can enable, and new business logic may need development.
What is MCP?
MCP, or Model Context Protocol, is the standard AI assistants use to call external tools. Cutova is the MCP server that connects those requests to Epicor.