For 3PLs · agencies · platforms

The agent infrastructure
commerce runs on

Pipe17 built the first e-commerce agent on this infrastructure — and became the first member of onX, the open standard for agent-driven commerce. Now you can use the same rails to launch agents for every brand you serve.

onX — Order Network eXchange

An open standard built on the Model Context Protocol for AI agents to talk to order management systems — stewarded by the vendor-neutral Commerce Operations Foundation. Agents built on this infrastructure speak onX natively, to every system and every partner in the network.

What you build on

Everything an agent needs.
Nothing you have to rebuild.

An isolated agent per brand

Every brand you serve gets its own agent instance — its own memory, credentials, and knowledge. Brands never see each other. You see everything.

The integration layer, solved

A connector catalog hardened by 300 integrations' worth of how systems actually behave — with credential vaulting, rate limits, and read-only scopes by default.

The trust ladder, built in

Autonomy is gated rung by rung: answer, plan, configure, communicate, operate. Reversible actions run; irreversible ones wait for a human. Policy, not prompt engineering.

Every channel out of the box

Slack, email, and web chat route into one conversation layer. Your agent shows up where each brand's team already works.

Metering made for rebilling

Every model call is metered per brand and rolls up to your account — so per-brand cost, margin, and rebilling are visible from day one.

An operating graph that compounds

Each agent accumulates operational knowledge about its brand — and the infrastructure gets smarter with every brand on the network.

The partner motion

An agent on every brand you serve

01

One account, every brand

Your account holds an organization per brand you serve. Your team moves across all of them; each brand's team sees only their own. Isolation is the tenancy model, not a setting.

02

Launch your agent

Build on the same infrastructure that runs Pippen — connectors, channels, memory, and autonomy gating included. Your agent, your brand, in front of your customers.

03

Expand brand by brand

Usage is metered per brand, priced per brand served. Start with one book of brands, prove the labor returned, and roll it out across the rest.

Build the next agent on the network

Pipe17 was the first. Join the infrastructure — and the open standard — that agents for commerce operations are being built on.