Three integration paths
Direct database, your ERP's REST API or standard MCP protocol.
Today we run in production with AS2 by Asinfo. With any other ERP we connect via database (SQL Server, PostgreSQL, MySQL), REST API or MCP protocol: we build the connector with you during the pilot.
No migration · your DB remains the source of truth.
Today your ERP stores years of data: customers, invoices, products, receivables. The problem is that this data lives isolated from the new AI, WhatsApp and natural-language reporting layers. Pacunex AI agents for ERP solve that exact gap: connecting your current system to an agent layer without touching the database.
Migrating ERP is costly, risky and sometimes unnecessary.
Poorly documented proprietary APIs that frustrate integrators.
Reports only the ERP owner knows how to run — AI stays excluded.
We identify your access type: direct database, published REST API or vendor MCP protocol.
Without impacting your production DB. Controlled reads, explicit writes, sandbox first.
Collections, sales, reports, support — you pick the first agent to run.
The agent runs on a real slice of your ERP and we measure KPI vs. your previous baseline.
An AI agent for ERP is a digital teammate that reads and writes in your management system to execute commercial tasks through an external channel — typically WhatsApp. It does not replace the ERP: it extends it with AI.
Direct database, your ERP's REST API or standard MCP protocol.
Your ERP remains the source of truth. The AI agent queries, it does not copy.
AS2 by Asinfo runs with Pacunex today via database. It is our reference integration.
Each connector is tested against a sandbox before touching production DB.
Every read and write by the agent is logged and auditable.
The exact connector to your ERP is built jointly during the pilot, at no extra cost.
Today we have a single integration in production: AS2 by Asinfo. With any other ERP the path is its database, its REST API or MCP — the connector is built and tested with you during the pilot.
Honest projections — Pacunex is in open beta.
Agent reads overdue receivables and operates via WhatsApp, logging promises back to the ERP.
Your manager asks in plain Spanish what used to need IT — the AI queries the ERP and answers.
Before each visit, the rep gets customer context pulled from the ERP.
Guided implementation, special beta conditions and a direct voice in the roadmap.
No. Pacunex AI agents for ERP connect to the system you already use, with no migration. Your ERP stays the source of truth.
Today the only integration we have in production is AS2 by Asinfo. That said, if your ERP exposes a database (SQL Server, PostgreSQL or MySQL), a REST API or MCP, we can connect it: we build the specific connector with you during the pilot, at no extra cost.
Yes, within the limits you define. By default writes are explicit and traceable — every operation is logged and auditable.
No. The AI agent queries what it needs each turn via database, REST API or MCP and does not copy your database. Chat sessions and operational logs are stored encrypted in our infrastructure, isolated per company.
About a week for connector sandbox, two weeks for pilot with real data and a month to measure agent KPI.
In both cases. With an on-premise ERP the usual path is reading its database with a read-only user; with a cloud ERP, its REST API. The method is defined in the initial audit.
Let's chat on WhatsApp, identify the integration path and build the first connector with you.