One set of connected data
Perform.AI runs every part of your e-commerce operations on one set of connected data, so a decision in one stage is made with the context from every other. In practice that means one shipment record, produced once and read by everything: the Tracking Page a shopper opens, the notification that goes out, the view your customer service team works in, the delivery date shown at checkout and the reporting your operations team reads. Because they all read the same record, a question has one answer rather than four depending on which system is asked. The problem this solves is the gap between a brand’s tools. Every tool works, but decisions get made without the facts that sit in the next system along: a delivery date promised without knowing what the carrier charges, one “where is my order” answered by opening three systems, numbers assembled by hand before anyone can act on them. Platform closes that gap at the data level. Carrier data is collected by whichever method each carrier supports, mapped to one event vocabulary, and joined to the order, warehouse and returns data that arrives from your own systems.What Platform covers
Data Integration
How shipment and order data enters Perform.AI through the API, file upload, SFTP, webhooks and store integrations, and how it comes back out.
Carrier Integration
How Perform.AI connects to carriers for tracking, booking and labels, and how carrier configurations and standard events work.
AI Navigator
The assistant in the Perform.AI portal that answers questions about features, your account setup and your shipments, with links to act.
Security & Compliance
How Perform.AI authenticates portal users, API clients and MCP sessions, and which roles control access to your account.
Two ways to ask Perform.AI a question
Platform includes two assistants that do different jobs. AI Navigator works inside the portal and knows everything in Perform.AI and nothing beyond it. The Perform.AI MCP server connects the AI assistant your team already uses to your Perform.AI account through the Model Context Protocol, so a question about a shipment can be answered against your mail, your documents and the rest of your work at the same time. Most teams use both. See AI Navigator and the MCP overview.Portal languages
The portal is available in English, German, Spanish and French, selected in the user’s profile. AI Navigator answers in the language you write in.For developers
- Authentication: request API credentials and generate a Bearer token.
- Create Shipment, Update Shipment, List Shipments and Retrieve Shipment: the shipment endpoints behind every integration.
- Webhooks: receive a Shipment update on every update cycle.
- Carrier configurations: the
carrier_referencevalues your shipments and bookings use. - Shopify integration: connect a store without writing code.
- MCP installation and MCP tools: connect your own assistant to your account data.