EDI (X12, EDIFACT, AS2)
Connect AI agents and workflows to EDI: read and build X12 and EDIFACT documents such as 850, 856 and 810, send and receive over AS2 or SFTP.
Book a demoEDI (X12, EDIFACT, AS2) for AI agents and workflows.
engini lets your AI agents and workflows work with EDI, the way retailers, distributors and manufacturers exchange orders and invoices: turn incoming X12 or EDIFACT documents into structured data, build outgoing ones from your ERP, validate them, send and receive over AS2 or SFTP, and answer with functional acknowledgments. A purchase order from a retailer becomes a sales order in your ERP, and the ship notice and invoice go back on time. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What your agent can do with EDI. Every tool is one you allow or leave out.
The EDI tools in engini, grouped by what they change. Reading a document is safe to hand out widely. Sending to a trading partner goes only to the workflows and agents that need it.
Read
Turn an X12 or EDIFACT document into structured data, such as an 850 purchase order into header and lines.
Check a document against its standard and the partner's rules, and list what is wrong.
Read documents received from a trading partner, by type and date.
Write
Build an X12 or EDIFACT document from data: an 855 acknowledgment, an 856 ship notice, an 810 invoice and more.
Send a document to a partner over AS2, signed and encrypted, and record the receipt (MDN).
Drop a document in a partner's or VAN's SFTP folder.
Send a 997 or 999, or an EDIFACT CONTRL, for a document received.
Triggers
A trading partner sent a document to your AS2 address.
An EDI file arrived in an SFTP folder.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to EDI (X12, EDIFACT, AS2). Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your EDI (X12, EDIFACT, AS2) connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of EDI (X12, EDIFACT, AS2) tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects EDI (X12, EDIFACT, AS2) and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every EDI (X12, EDIFACT, AS2) tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to EDI (X12, EDIFACT, AS2) through engini
{
"mcpServers": {
"engini-edi": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your EDI (X12, EDIFACT, AS2) connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the EDI (X12, EDIFACT, AS2) tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on EDI (X12, EDIFACT, AS2). Agents and workflows, across systems.
Retail orders straight into the ERP
An 850 from a retailer becomes a sales order in NetSuite, SAP or JD Edwards, the 855 acknowledgment goes back, and exceptions go to the account rep in Teams.
Ship notices on time
When an order ships, the 856 ship notice is built from the fulfillment and sent before the truck arrives, so there are no chargebacks.
Invoices partners accept
Invoices are built as 810s from the ERP, validated against each partner's rules and sent, and remittances (820) are applied to open invoices.
Questions about partner traffic
An agent in Slack answers what came in, what was rejected and who has not acknowledged. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between EDI (X12, EDIFACT, AS2) and another system engini connects is available.
You decide what each agent may do in EDI (X12, EDIFACT, AS2). engini enforces it on every call.
Only the tools you allow
A toolset lists the EDI (X12, EDIFACT, AS2) tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own EDI (X12, EDIFACT, AS2) account and engini acts as that person, with their EDI (X12, EDIFACT, AS2) permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect EDI (X12, EDIFACT, AS2) in three steps. Then decide what each agent may do.
Sign in to EDI (X12, EDIFACT, AS2)
Add each trading partner with its AS2 ID, URL and certificates, or its SFTP folder, and the documents you exchange. engini keeps your AS2 certificate and signs and encrypts for you.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in EDI (X12, EDIFACT, AS2) from Claude, ChatGPT, Cursor or your own code.
EDI (X12, EDIFACT, AS2) and engini. Straight answers.
Can an AI agent write to EDI (X12, EDIFACT, AS2), or only read?
Both. engini has tools to build EDI documents, send them over AS2 or SFTP, and send acknowledgments. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Do we still need a VAN?
Not for partners who support AS2 or SFTP. engini connects to them directly. For partners who require a VAN, send to and collect from the VAN's mailbox.
Which documents does it handle?
Any X12 or EDIFACT document. The common ones are 850, 855, 856, 810, 820, 846, 940 and 945 in X12, and ORDERS, DESADV and INVOIC in EDIFACT.
Can it follow each retailer's rules?
Yes. Validate EDI checks a document against the partner's own rules as well as the standard, before it is sent.
Does the agent act as me in EDI (X12, EDIFACT, AS2)?
It sends as your company, with your AS2 ID and certificate or your SFTP account. Every run is recorded under the person who started it.
Can a change in EDI (X12, EDIFACT, AS2) start work?
Yes. A document received over AS2 starts a workflow as it arrives, and a scheduled trigger checks SFTP folders for new files. A workflow can include an AI agent step.