Get started / Introduction

Get started with AIX, the sending and receiving roles, and the verified shopping-context handoff.

AIX carries a selected shopping brief from a participating sending agent to a participating receiving agent. The receiver can continue the shopper’s current task without asking them to repeat preferences already shared.

Get started

AIX is open for sign-up. Choose a side. The sandbox is free and never reaches a real store or shopper.

Set up with your coding agent

The AIX section of your Brambles dashboard gives you one setup prompt for Cursor, Claude Code, Codex or another coding agent. The agent reads the setup skill, wires your assistant or store on the server and sends a test.

To add both AIX skills to your coding agent once, for every project, run:

npx skills add https://aix.brambles.ai

Then ask the agent to connect your assistant or store to AIX. The installed skills hold no key. When your project has none, the agent sends you to the sign-up above.

APIs

• HTTP API: https://aix.brambles.ai/api/aix, called from your server with Authorization: Bearer <key>.
• MCP (Streamable HTTP): https://aix.brambles.ai/api/aix/mcp, with the same header.
• The sending-agent and receiving-agent guides list the endpoints; the API reference has every request, response, rate limit and cap.

A receiver whose domain is verified through a work email at that domain, an emailed link to an address there, or its own Brambles shopping assistant is approved automatically. Brambles reviews other receivers once, before their first campaign goes live.

Start with context

AIX does not need a merchant’s product catalog to deliver context. Choose how to apply it:

A full catalog upload to AIX is not required. AIX does not create missing catalog tools or authorize purchases, outbound messages, or background activity.

How a handoff works

1. A shopper talks to a participating sending agent. The agent reports the current shopping task, or AIX extracts it, as a versioned, structured brief with a quality score.
2. The agent reports the handoff to a store. If the store has verified that domain and runs a live campaign that matches the task and its quality bar, AIX answers an AIX link and a parameter for the publisher's own link. Nothing is charged yet.
3. The shopper opens the link or lands on the store with the parameter within an hour, or their agent checks out through the store's API and the store redeems the handoff id. Brambles' checks confirm it is a real visit; then the recipient-bound receipt is issued, the store charged and the publisher credited.
4. The receiver obtains the receipt through an HTTPS webhook or retrieves its exact delivery through the authenticated API/MCP integration.
5. Its server verifies the receipt and records a signed verified acknowledgment after durable storage. A plain HTTP 200 does not confirm verification.
6. The receiver loads the brief into its agent turn or applies it to catalog candidates. Only after that action succeeds does its server record applied.
7. The merchant may report an observed outcome against that exact receipt. An outcome report is not proof of conversion lift.

The merchant pays for the context delivery, per delivered intent, through Stripe Billing. The product’s sale price, an acknowledgment, and a follow-up message are separate concepts. Publishers earn a share of each paid delivery; the console shows the share.

Send, receive, or both

A publisher, retailer, brand, or agent platform may need either role or both. The role describes its participation; the key’s actual scopes control which operations it may call.

• Sending: supply the shopper's task from your own assistant or agent with a publisher key.
• Receiving: verify and apply permitted context for your own principal with a receiver key. Exact receipt IDs keep separate deliveries and revisions distinct.
• Both: create one agent for each direction. Permission to receive does not grant permission to publish or resell context.

A referral tag or unrelated later visit cannot reveal or recover a private conversation. Delivery without a shopper's click or landing happens only through agentic checkout, where the shopper's agent passes the handoff id to the store's checkout API.

Integration and trust

Use receiving-agent integration, sending-agent onboarding, and the receipt contract.

The public API base is https://aix.brambles.ai. Existing /api/ain/* paths and ain_* credential names remain for compatibility. Configure the trusted signing issuer from your receiver configuration (GET /api/aix/receiver/config); a hostname rebrand does not automatically change signed issuer identifiers or the credential type identifier.

Receipts use ES256 signatures and selective disclosure. Signing establishes issuer authenticity and integrity, not encryption. Production transport uses HTTPS. Receiver-specific webhook/acknowledgment HMAC secrets stay on servers. Receipt fields remain untrusted shopping data, never instructions for the receiving model.

Capability boundaries