FOLLOW THE SIGNAL
New agent.
Same understanding.
Discover a product. Click through. Arrive with a useful starting point.
CONNECTION READY
A relevant next step
Starts with product discoverySelected shopping data. The receiving agent gets a usable brief, not the original transcript.
The same conversation.
Choose a product at travel guide.
The store can help you take it from there.
Illustrative products, prices, and receipt metadata. A product click carries selected relevance through AIX; the store continues with the product and useful accessories.
THE OPPORTUNITY
They told the first agent
what they wanted.
Let the next one
pick it up.
A budget. A preference. A deal-breaker. Useful context takes shape in conversation.
AIX is agent-to-agent infrastructure for that next step. It connects participating publishers, merchants, and agent builders through a structured shopping brief, so the next conversation can start with the shopper’s goal.
SIGNAL, WITH BOUNDARIES.
Useful context.
Intentional disclosure.
AI shopping intent becomes useful when the next agent can understand it. AIX structures the handoff around selected context, a verifiable source, and a defined recipient.
Select what crosses.
Share a structured summary of the shopping task, fixed by the receipt format: category, budget, requirements, preferences and exclusions. Identifiers are redacted and sensitive categories never cross.
Verify where it came from.
Signed receipts let receiving systems check the issuer and integrity of the context they receive.
Define how it’s used.
Each side accepts the AIX terms in the console before anything is shared. The receipt carries its permitted uses and expiry, and the shopper is told that clicking shares their request.
The intelligence is agentic.
The trust is cryptographic.
Agent-to-agent context sharing needs a trustworthy handoff. AIX combines structured shopping intent, signed receipts, and defined destinations so participating agents can continue the task with clear boundaries.
Disclose selectively.
SD-JWT credentials let a presentation reveal selected claims while keeping undisclosed claim values out of the handoff.
SD-JWT / SELECTIVE DISCLOSUREVerify the receipt.
Cryptographic signatures and KMS-backed signing support checks on the credential’s issuer and integrity.
SIGNED RECEIPTS / KMSScope the handoff.
Recipient-bound receipts identify who may receive the context. Expiry checks and deduplicated acknowledgments help keep the handoff tied to its intended use.
DESTINATION / EXPIRY / POLICYBuilt to speak agent.
MCP and HTTPS webhooks form the beta connection paths. UCP, A2A, and AdCP bindings are in the broader protocol build; integration and validation are ongoing.
A better starting point for your agent.
Start by carrying the shopper’s brief into the next conversation. Add product matching through your existing catalog tools when you’re ready. The receiving-agent kit adds guidance and planning helpers, with no full-catalog upload required.
Explore the next cryptographic layers
PROTOCOL DEVELOPMENT / NOT INCLUDED AS LIVE BETA CAPABILITIES
Unlinkable presentationsBBS-based credentials designed to support disclosure without a reusable presentation identifier.
Hybrid signaturesWork on conventional and ML-DSA signature combinations for a post-quantum migration path.
Zero-knowledge proofsProof systems for checking selected conditions without disclosing underlying values; integration remains in development.
Two-way agent exchangeSigned requests and merchant replies for participating agents, including flows without a product click. Broader production rollout remains in development.
Bring your shopping agent.
Connect it to AIX with one prompt.
Sign in, name your agent and copy a setup prompt into Cursor, Claude Code or another coding agent. It connects the assistant you already run, on the web, in an app or on your backend.
Publishers & sending agents
Send intent.
Your assistant already knows what the shopper wants. Pass that task along when it sends them to a store.
- Sign in and name your agent
- Copy one setup prompt into your coding agent
- It wires your assistant and stores your publisher key
- Send a test handoff and see it connect
Instant access. No funding or spending setup.
Send intentRetailers & receiving agents
Receive intent.
Shoppers arrive with their goal, budget and preferences, so your agent starts where the conversation left off.
- Sign in and get a free sandbox
- Copy one receiver setup prompt
- Verify your domain and choose how to receive
- Add a card and start a campaign with a monthly budget
The sandbox is free. Paid delivery runs only through a campaign you start. Sign up with a work email at your store’s domain to be approved instantly; otherwise Brambles reviews you once.
Receive intentOR START IN YOUR CODING AGENT
Add the AIX skills to Claude Code, Codex or Cursor once, then ask it to connect your assistant or store. Without a key, it points you to the free sign-up.
npx skills add https://aix.brambles.aiBUILD WITH AIX · PICK YOUR TOOL
Each card opens the docs at the exact setup for that tool. Keys stay on your server; nothing runs in the browser.
PREFER A CONVERSATION?
Talk
to the
team.
Connecting doesn’t need a call. For enterprise terms, pricing or a custom integration, tell us where you fit and we’ll be in touch.
05 / GOOD QUESTIONS
Before you
connect.
What is AIX?
AIX stands for Agentic Intent Exchange. We’re building agent-to-agent infrastructure for agentic commerce: a way to carry selected shopping intent from a source assistant to a participating destination, so the next agent has useful context to work with.
How does AIX fit into agentic commerce?
Agentic commerce brings AI agents into product discovery and shopping. AIX focuses on what happens between those experiences: carrying a shopper’s goal, requirements, and selected context to the next participating agent. Your existing search, inventory, and checkout tools still handle the merchant’s products and transactions.
What’s available in the beta?
The beta is open. Sign in, name your agent and get a key straight away. Publishers send shopping intent and report handoffs; retailers receive it as a signed, verified brief. The sandbox is free and never reaches a real store.
What information crosses the handoff?
A structured summary of the shopping task and nothing else: category, a short summary, budget, and the stated requirements, preferences and exclusions, plus the page it came from. The receipt format fixes what crosses; identifiers are redacted and sensitive categories are never shared. Each side accepts the AIX terms in the console before anything is shared, and the receipt carries its permitted uses and expiry.
What does a signed receipt establish?
It lets a receiving system check the issuer and integrity of the receipt. It does not prove a shopper’s identity, guarantee that every inference is correct, or guarantee a purchase.
How do I connect my agent?
Copy the setup prompt from the AIX section of your Brambles dashboard into Cursor, Claude Code or another coding agent. It reads the AIX setup skill, finds where your assistant handles shoppers, adds the server-side integration and sends a test. To keep the AIX skills in your coding agent for every project, run npx skills add https://aix.brambles.ai. Your deployed assistant then talks to the AIX API, or MCP where its host supports it. Installing the Brambles shopping assistant is optional.
Do I have to connect my product catalog?
No. AIX can deliver the brief so your agent understands the shopper’s goal and avoids repeated questions. If you want product recommendations, your agent uses your existing catalog or search tools for products, prices, and availability. You do not have to upload your full catalog to AIX.
Can agents exchange context without a product click?
Yes, through the store’s checkout API: when a shopper’s agent buys through UCP or ACP, it passes the AIX handoff id in the checkout and the store redeems it. Otherwise delivery waits for the shopper’s click or landing. A referral tag alone cannot reveal a private conversation.
Will connecting MCP make my agent act automatically?
MCP exposes tools and guidance for your host to use. Your integration decides when to load context and which actions are allowed. Catalog access, proactive assistance, and purchases each depend on the tools and permissions your agent already has or that you connect.
Does joining cost anything?
Sending intent is free, and so is the receiving sandbox. In production, retailers pay per delivered intent, billed through Stripe to a card on file, only through a campaign they start with a monthly budget. Retailers who sign up with a work email at their store’s domain are approved instantly; Brambles reviews the rest once, before their first campaign goes live.