Pipe17 has implemented the Order Network eXchange (onX) standard. All Pipe17 customers are now onX-enabled, with standardized access to order operations data through the Pipe17 MCP server.
As AI agents become part of how brands and 3PLs manage operations, the need for standardized, interoperable data exchange has never been greater. onX provides the common language that makes this possible.
Table of Contents
What is onX?
onX, built on the model content protocol (MCP), is an open standard for exchanging order data across commerce systems. It defines a common structure for core commerce objects: orders, inventory, line items, parties, payments, shipments, etc. It also standardizes events like order created, accepted, packed, shipped, and delivered. The specification may be found documented at https://github.com/commerce-operations-foundation/.
The onX standard is developed and governed by the Commerce Operations Foundation, which Pipe17 co-founded to give AI agents and all commerce channels a common language for interacting with post-purchase commerce systems.
What Pipe17’s onX Implementation Delivers
Pipe17’s MCP server is now aligned to the onX specification.
For customers building AI agents or AI-assisted workflows, this means standardized access to your omnichannel order operations data. If you’re using Pipe17 to manage your order operations for Shopify, Temu, UNIS, Flexport, Full Circle, NetSuite, or any of the hundreds of systems in our managed connector network, that data is now accessible through AI-native onX.
Through Pipe17’s onX implementation, you can query order status, inventory availability, fulfillment data, and more. You can also perform operations like rerouting orders or updating fulfillment instructions, all through a standardized interface that works with any AI client.
For a deeper look at how onX works under the hood, including the adapter pattern and open-source architecture, see our CTO’s technical deep dive: Building the Open Standard for Commerce Operations.
Benefits for Brands and 3PLs
Pipe17’s onX implementation is particularly valuable for operations teams and developers building internal AI agents for customer service, order inquiries, or exception handling. It’s also useful for AI-assisted workflows that need real-time access to omnichannel data like orders, inventory, and fulfillments, or teams looking to future-proof their commerce stack with open standards.
For example, a customer service AI agent can answer customer questions like “Where is my order?” or internal team questions like “What’s the current inventory for this SKU?” without a developer having to build a single API integration or write a query.
Similarly, an exception-handling AI agent could automatically reroute an order to an alternate fulfillment location when it detects an inventory shortage, using onX to update the order without manual intervention.
An Open Standard with Industry Backing
The Order Network eXchange is governed by the Commerce Operations Foundation, a vendor-neutral standards body.
By aligning with onX, Pipe17 is committing to supporting an open standard that will continue to grow and improve alongside the broader commerce ecosystem. As onX evolves, the Pipe17 implementation of onX evolves with it.
Getting Started
If you’re a Pipe17 customer interested in accessing your organization’s onX-enabled MCP server, contact your account manager or drop us a note here. Our team will provision your organization with credentials and documentation.
Not a Pipe17 customer yet? Book a demo to see how our AI-Native Order Operations Platform connects, orchestrates, automates, and now standardizes your agentic commerce operations.
