How AI Agents Connect to Epicor Kinetic, On-Premise or Hosted by Epicor
What an AI agent needs to reach Epicor Kinetic in Epicor's cloud, on your own servers or with a hosting partner: the account, the API key, the access scope and the network change, plus how other approaches connect.
Gonzalo Nuñez
Chief Technology Officer

Connect an AI agent to Epicor Kinetic through Epicor's own REST API, with an API key on a dedicated integration account and an access scope that limits the agent to the services it calls. That is how Fluent connects, and it works the same way whether Epicor hosts your Kinetic instance or you run it on your own servers: an Epicor-hosted instance usually needs no network change at all, and an on-premise one only needs Fluent's fixed IP addresses allowed on the Epicor endpoint. Other routes fit specific cases: DMT when the data already exists as rows in a spreadsheet, middleware when two systems already exchange structured data, and screen automation only where no API exists.
Where your Kinetic runs, and what changes
The agent connects the same way in every case. What differs is who controls the network in front of the Epicor endpoint.
Hosted by Epicor
When Epicor hosts Kinetic in its cloud, the REST endpoint is already reachable over the internet, protected by the account and API key your team creates. An Epicor-hosted instance usually needs no network change at all. Your administrator still creates the integration account and API key and imports the access scope, exactly as on-premise.
On your own servers
Most on-premise Kinetic instances are not on the public internet, and the people who keep it that way are the ones who approve the connection. Fluent calls out from fixed IP addresses, so a restricted network needs those addresses allowed on the Epicor endpoint and nothing else opened. Nothing is installed inside Epicor. Self-signed certificates work, though a valid certificate is better.
Hosted by a partner or in your own cloud account
Treat it like on-premise. Whoever runs the firewall in front of the instance, your IT team or your hosting partner, allows Fluent's IP addresses on the Epicor endpoint. The account, the API key and the access scope are still created in Kinetic by your own administrator.
What your Epicor administrator does
Every item below is created and held by your team, and each one can be taken back without calling us.
- Create a dedicated integration account in User Account Maintenance, separate from any employee's login, with a password set never to expire.
- Generate an API key in API Key Maintenance and keep it wherever you keep secrets. It authenticates Kinetic's REST API, and you can revoke it at any time.
- Confirm the Epicor endpoint is reachable, and on-premise, allow Fluent's IP addresses.
- On the setup call, download the agent's access scope, import it in Security Management, assign it to the integration account and bind it to the API key.
- Test the connection together. Before Fluent accepts a connection it resolves the hostname, opens the port and reads the certificate, and a check it cannot complete is reported.
That technical setup is one 30-minute call, after which Fluent is connected. The guide to how long AP automation takes on Epicor Kinetic covers what follows it.
What the agent can reach once connected
Only what the access scope allows. Each Fluent agent generates its access scope from the tools it actually calls, so an agent that never touches receipts never asks for them. Epicor enforces the scope. If an agent's needs change, your administrators get a digest naming every permission added and removed before anything is re-imported, and revoking the key or unassigning the account stops the agent at your boundary.
Your live data, as your instance defines it. Agents read the API definitions off your own instance, so your customizations and user-defined fields come through as they are. Questions are answered from your own BAQs, run through Epicor's engine rather than a copy of your data.
Writes through Kinetic's own business logic. Fluent calls the same business objects the Kinetic screens call, so your BPMs and required fields apply exactly as they do to a person typing. Where Epicor offers it, a header and its lines commit together. Nothing is written until a person approves the draft in Fluent.
Credentials kept encrypted. Connection details are encrypted before they are stored, and nothing is kept in plaintext.
Other ways software connects to Kinetic
Screen automation (RPA)
An RPA bot drives the Kinetic screens the way a person would, clicking and typing values from a spreadsheet or a separate OCR step. It needs no API work, which makes it quick to try. It is also fragile: an upgrade that moves a field, a new layout or an unexpected dialog stops the bot or puts a value in the wrong field.
Import files and DMT
DMT, Epicor's Data Management Tool, loads records from a spreadsheet in its template layout. It is the right tool for structured rows, and most Epicor administrators know it from data migration. Reading each document and preparing those rows happens before it.
Direct database writes
Writing straight into Epicor's database tables skips the business logic the Kinetic screens run, so validation, required fields and BPMs never see the record. It is the one route we would rule out.
Middleware and integration platforms
Integration platforms with an Epicor connector move structured data between systems, such as orders from an ecommerce site or invoices from another ERP. When they call Epicor's API, Kinetic's business logic applies. They expect the document to be data already; reading a PDF is a separate step.
Epicor's own tools
Service Connect and Automation Studio orchestrate structured flows into Kinetic. Epicor ECM, with Intelligent Data Capture, captures and archives documents and runs approval workflows. Fluent works alongside ECM and can do the reading in place of the capture step, filing each document into ECM with its index values populated.
Side by side
| Approach | How it reaches Kinetic | Kinetic's business logic applies | Reads PDFs and scans | What your team maintains |
|---|---|---|---|---|
| AI agent on the REST API (Fluent) | Epicor's REST API, with an API key and an access scope | Yes | Yes, plus spreadsheets, email bodies, XML and EDI | The integration account, the API key and the scope import |
| Screen automation (RPA) | Drives the Kinetic screens like a user | Yes, through the screen | Only with a separate OCR step | Bots, repaired after upgrades and layout changes |
| DMT and import files | Loads spreadsheet rows | Yes | No | The spreadsheets, prepared by a person |
| Direct database writes | SQL into Epicor's tables | No | No | Records Kinetic never validated |
| Middleware and integration platforms | A connector calling Epicor's API | Yes, when it uses the API | Only with a separate capture step | The flows you build |
| Service Connect or Automation Studio | Epicor's own integration tools | Yes | No | The workflows you design |
| Epicor ECM with IDC | Epicor's own capture and document management | Ask Epicor | Yes | An ECM project, run by Epicor or a partner |
Why Fluent uses the REST API
- One path for every hosting option. Epicor-hosted, on-premise and partner-hosted instances connect the same way, from outside.
- Epicor stays in charge. Every write goes through the business logic the screens use, and Epicor enforces the access scope.
- Least privilege per agent. Each agent asks for the services it calls and nothing more.
- Nothing to uninstall. No customization, no BPM, no staging table and no import file. If you disconnect Fluent, nothing has to be removed from Epicor.
- Credentials your team holds. Revoke the key or unassign the account and the agent stops, without a call to us.
Connecting your own AI tools
A general chat assistant pointed at Epicor with an employee's login can do whatever that login can do. Fluent keeps the Epicor connection governed and gives your own systems a front door to it: its own REST API, CLI, MCP server and webhooks let them send documents to an agent, read the results and react when a document is approved. The guide to whether it is safe to let AI post into Epicor covers the controls in detail.
Customer results
Metalworks, a family-owned manufacturer in Michigan on Epicor since 2010, runs its AP invoices through Fluent. Fluent connected to Epicor in a day, and reviewers rarely change a field it read. Keying an invoice took seven to eight minutes; reviewing the draft now takes under a minute, and an approval that took five minutes now takes seconds, from an email. “It’s like a breath of fresh air,” says Jill Schoedel, IT Manager.
StoneAge, an employee-owned maker of waterblast tools in Durango, Colorado, runs supplier pack slips into Receipt Entry and customer purchase orders into Order Entry through Fluent. Fluent connected to its Epicor in one 40-minute call. A receiver reviews a pack slip in a median of about ten seconds and customer service reviews a sales order in about a minute, where both used to key them by hand. A person approves every document before it posts.
Where to start
Read how Fluent connects on the Epicor integration page, then pick the screen to automate first, such as AP Invoice Entry or Order Entry; all ten Kinetic screens are listed together. Paid plans start at $600/month, after a 30-day trial. To connect your own instance, book a demo.
Frequently Asked Questions
Through Epicor's own REST API, with an API key on a dedicated integration account and an access scope your administrator imports in Security Management. Fluent connects this way from outside, from fixed IP addresses, and installs nothing inside Epicor. Technical setup is one 30-minute call.
Yes. Fluent works with Epicor Kinetic on-premise or Epicor-hosted, and connects the same way to both. An Epicor-hosted instance usually needs no network change at all; your administrator still creates the integration account and API key and imports the access scope.
Only Fluent's fixed IP addresses, allowed on the Epicor endpoint. Nothing else is opened and nothing is installed inside Epicor. Self-signed certificates work, though a valid certificate is better. A partner-hosted instance works the same way, with whoever runs the firewall making the change.
With Fluent, exactly what the access scope you imported allows. Each agent generates a scope listing the services and methods its tools call, and Epicor enforces it. Every write goes through Kinetic's own business logic, and nothing is written until a person approves the draft in Fluent. Revoking the API key stops the agent.
No. Your team creates a dedicated integration account in User Account Maintenance and an API key in API Key Maintenance, and holds both. You can revoke either without calling us.
The REST API is the sturdier route. RPA drives the screens and breaks when an upgrade or layout change moves a field. DMT loads structured rows that someone has to prepare first. Writing straight to the database skips Kinetic's business logic, so validation and BPMs never see the record. Fluent uses the REST API, so Epicor validates every write.


