Get started / Quickstart

Quickstart

Connect a shopping assistant or a store to the Agentic Intent Exchange with one prompt, an MCP client or plain HTTPS. The sandbox is free and never reaches a real store or shopper.

Set up with an AI agent

Paste this into Cursor, Claude Code, Codex or any coding agent. It installs the AIX skills, finds where your server handles shoppers, adds the integration and sends a sandbox test.

Prompt for coding agents

I want to connect my shopping assistant to the Agentic Intent Exchange. Run npx skills add https://aix.brambles.ai, then follow the aix-send-intent skill. My sandbox key is in AIX_PUBLISHER_KEY.

Keys come from the AIX console and are shown once. Create a free sending agent, store the key as AIX_PUBLISHER_KEY on your server, and never put it in browser code, a mobile app or a chat. Create a free sending agent ↗

Pick how you connect

Every path ends at the same two server calls. Choose the one that matches where your agent lives.

Coding agents · one prompt

The agent installs the skills, finds where your server handles shoppers, adds the calls and sends a sandbox test.

Agent frameworks · AIX as tools in your agent

Agents built on these frameworks get the two AIX operations as tools, through the MCP server or defined in code, with the prompt rules that tell the model when to use them.

MCP clients · the exchange as tools

Any host that speaks Streamable HTTP and can send a bearer header. The tools are scoped to the key.

From your server · HTTPS

Two calls with a three-second timeout. AIX must never slow down or break the shopper's experience.

What happens next

POST/intentsYour server reports the shopper's task after each turn that changes it. Names, contact details and the transcript never leave you.
POST/handoffsWhen the assistant links the shopper to a store, report it and add the returned aix_param to the store URL inside your own link.
AIXGates, then a receiptConsent (EEA, UK, CH), sensitive-topic suppression, receiver verification and campaign budget. Then a receipt bound to that one store.
GET/activityAccepted, delivered, earned. The console flips to Connected after your first sandbox handoff.

What your server exchanges

Two calls. The first describes the task; the second says where the shopper is going.

POST /intents
{
"session_id": "conv_123",
"task": {
"category": "Running shoes",
"summary": "Wide running shoes for daily training, cushioning preferred, up to $150.",
"budget": { "currency": "USD", "max_cents": 15000 },
"facts": [
{ "attribute": "width", "value": "wide", "strength": "required" },
{ "attribute": "use_case", "value": "running", "strength": "required" },
{ "attribute": "feature", "value": "cushioning", "strength": "preferred" }
]
},
"page_url": "https://publisher.example/reviews/best-running-shoes",
"locale": "en-US",
"country": "US",
"privacy": { "gpc": false }
}

Endpoints

Base URL https://aix.brambles.ai/api/aix. Every request carries Authorization: Bearer <key>. Sandbox keys start with aix_test_, production keys with aix_live_.

Protocol bindings

MCP and plain HTTPS are live today. Bindings for the Universal Commerce Protocol (UCP), Agent2Agent (A2A) and the Ad Context Protocol (AdCP) are in development. The Agentic Commerce Protocol (ACP) and the Agent Payments Protocol (AP2) move the order and the payment; AIX moves the intent.

Was this helpful?