Reference / Changelog

Dated changes to the Agentic Intent Exchange API, console, terms and setup skills, newest first.

Dated, newest first. Changes that can break an integration are marked Breaking. The API is versioned by schema identifiers (aix.shopping-context.v1, aix.delivery.v1, aix.delivery-ack.v1); a new major schema version ships beside the old one, never in place of it.

2026-10-24

• Breaking: one status for every store-side refusal. POST /handoffs now answers not_delivered whenever no store will pay for the handoff right now (the store is not receiving, has no matching live campaign, the intent is below its quality bar, or it has no billing or budget), without saying which, so a sending agent cannot map a store's commercial state. delivery_failed is documented. The activity report's handoffs.not_delivered object now has the keys not_delivered, consent_required and delivery_failed. Every recorded handoff carries environment, earnings_cents and quality_score.
• Webhook schema fixed. The published delivery.v1.schema.json and the OpenAPI DeliveryEnvelope now list all six fields of the body that is actually sent: schema_version, reference, receipt, ain_member_id, delivered_at and acknowledgment_url (the last two are required). The earlier four-field schema rejected every real webhook.
• Acknowledgment response documented. POST /deliveries/ack answers { ok, event_id, receipt_id, event, application, duplicate }, not { "status": "recorded" }. GET /deliveries, GET /deliveries/{receipt_id}, GET /activity and POST /privacy/delete are typed in the OpenAPI document, and IntentAccepted carries quality and the sandbox warning.
• Principal ids. Examples no longer show a :live suffix, which never existed: production principals are the bare agent id, sandbox principals end in :test.
• 401 and 403. A missing, revoked or unknown key answers 401 unauthorized; a key without the scope an operation needs answers 403 insufficient_scope with required. Three receiver endpoints answer 401 in both cases; the reference says which.
• Limits disclosed. Per-key rate limits (120 a minute for intents, handoffs, redemptions, deletions, acknowledgments and MCP; 30 for message-only intents; 60 for activity and delivery polling; 10 for test deliveries; 30 per IP for landings), the new-publisher cap of 100 paid deliveries a day for 30 days and the 1,000-a-day default after it, the one-hour click window, the different-address rule for repeat opens, and the automated-open rule. Destinations must be https.
• Sandbox AIX links show a test page naming the destination instead of redirecting.
• Test deliveries. The console button, POST /test-deliveries and a sandbox redeem_handoff or POST /handoffs/{handoff_id}/redeem with any well-formed id are the three ways to get one; the docs no longer describe a test-delivery MCP tool, which never existed. The MCP submit_intent tool takes { "intent": { … } }; the framework guides send it that way.
• Receiving docs trimmed to what is deployed. Tools and endpoints that were never released (receiver guidance, next-step planning, candidate ranking, a skill download) and the product-context object are gone from the docs. Any sending agent with a production key can supply intent for a verified, campaign-backed store.
• Payments. Receivers pay through Stripe Billing, metered per delivered intent and invoiced in USD when usage reaches $25 and at month end; nobody pays in advance. Publisher earnings are paid monthly, on the 10th, for charges the store has already paid; balances under $25 carry forward.
• Terms, version 2026-10-24 (both sides). The receipt is issued and the delivery charged when the shopper's click, landing or the store's redemption is confirmed, never when a handoff is merely reported; the quality bar, daily caps, the one-hour window and USD are stated; receiver fees are invoiced through Stripe Billing with refunds, credits and disputes handled there, and a reversed charge reverses the matching publisher earning; domain verification by email link and by the organization's Brambles shopping assistant are listed; the minimum payout is stated. "App" is now "Sending Agent" or "Receiving Agent". The console asks each organization to accept the new version.
• Site. The Agentic Intent Exchange is linked from the products menu and the footer. Console copy says "agent" for sending and receiving agents and shows delivery and verification states in words.

2026-10-23

• Reporting in the dashboards. Each AIX agent has a report for the last 7, 30 or 90 days, for sandbox and production:

  • totals and a chart by day;
  • for sending agents, the stores they sent shoppers to;
  • for receiving agents, what shoppers asked for, where they came from (chat, search results, recommendations), how many sending agents sent them, and their recent deliveries;
  • the sales stores reported.

  The daily figures and every handoff or delivery download as CSV. What a shopper asked for is kept 30 days, as the terms require. Publishers see sales only as totals, and stores never see which publisher sent a shopper.

• Report a sale over HTTPS. POST /deliveries/{receipt_id}/outcome with {"converted": true, "order_value_cents": …} is the REST version of the MCP report_outcome tool, for a receipt you verified. The receive-intent skill now tells stores to report sales from their checkout.

• AIX in your other dashboard pages.

  • Publishers' earnings appear on the revenue overview and the payouts card as their own type, AIX shopping intent, instead of inside click ads.
  • Stores that receive intent get an AIX card on their retail analytics page.

2026-10-22

• Keep your own links. A handoff a store would pay for now also answers aix_param (aix=<handoff_id>) and landing_url. Publishers add the parameter to the store URL inside the link they already use, affiliate, ad or plain, and the request is delivered when the shopper lands on the store with it. The AIX link stays available for publishers without their own links. Handoff ids now start with aixho_.
• Capture the shopper's arrival. Stores pick up ?aix= with the AIX tag (https://aix.brambles.ai/aix-tag.js, one script on every page, which calls POST /landing), their Brambles shopping assistant, or their own server with POST /handoffs/{handoff_id}/redeem and {"via": "landing"}. A landing through the tag or the Brambles assistant passes the same checks as a click, and browser extensions can hand the id to the page with postMessage.
• MCP redeem_handoff. Receiving agents connected over MCP can redeem a handoff id from a landing or a checkout.
• One-click sending for Brambles publishers. A publisher whose shopping assistant Brambles runs turns on Share shopping intent from your Brambles assistant in the dashboard. No agent, key or code; existing product and affiliate links keep working, and the request rides inside them to stores that would pay.
• Click-confirmed delivery. A handoff a store would pay for returns an AIX link (https://aix.brambles.ai/h/…, status delivers_on_click). The intent is delivered, the store charged and the publisher credited only when a shopper's browser opens it. Bots, link previews, the publisher's own server, instant clicks and click floods never count. Open handoff_url in the shopper's browser and never prefetch it.
• Intent quality. Every accepted intent carries quality: a score from 0 to 100 and the signals behind it. Campaigns pay only for intents at or above their quality bar (min_quality, default 40); a handoff below it is not delivered (since 2026-10-24 it answers not_delivered).
• Agentic checkout (UCP, ACP). When a shopper's agent buys through the store's checkout API, it passes the handoff id in the checkout (UCP attribution.aix_handoff, ACP affiliate_attribution), and the store redeems it with POST /handoffs/{handoff_id}/redeem: the same delivery and charge as a click, once per handoff.
• One-click receiving for Brambles stores. A store running the Brambles shopping assistant greets shoppers who arrive through AIX with their request, with no integration code. Stores can turn it off in the console.
• Verify a domain by email link or your Brambles assistant. The console can email a one-time link to any company address at the domain, and a store whose homepage already runs its own Brambles shopping assistant is verified as soon as it adds the domain. Both approve the receiver. The tag and DNS instructions now say where to add them on common store platforms and DNS hosts.
• Publisher earnings from collected payments. Earnings join the payout run once the store's invoice covering them is paid.
• Card on file for receivers. Production delivery is billed through Stripe Billing on a metered price per delivered intent; nobody pays in advance. The console stores only the subscription id and status.
• One-click domain verification. A work email at the domain verifies the domain instantly and approves the receiver automatically. The aix-verification meta tag, a DNS record or a file remain as fallbacks, reviewed once by Brambles.
• Receiver terms, version 2026-10-22. Accepted per organisation at opt-in; the console asks again when a version changes.
• Setup skills for coding agents. npx skills add https://aix.brambles.ai installs the aix-send-intent and aix-receive-intent skills into Claude Code, Codex, Cursor and other coding agents, from /.well-known/agent-skills/index.json (discovery schema 0.2.0, each skill digest-pinned).
• Console. MCP tool lists are scoped to the key: a publisher key is never offered receiver tools. Clearer verification and payout copy after the first live end-to-end run.

2026-10-21

• Self-serve open beta. Sign in, name an agent, get a sandbox key at once. Sending and receiving agents, sandbox and production keys, opt-in per side with versioned terms, receiver campaigns with a monthly budget, publisher earnings paid through Stripe Connect on the 10th.
• Privacy enforced in code. Sensitive-topic classifier, consent at the store-link click for shoppers in the EEA, the UK and Switzerland, country required in production, one pseudonym per task and destination, and POST /privacy/delete for shopper deletion requests.
• Fix. Agent creation failed for some new accounts during the first live sign-up test; resolved the same day.

2026-10-15

• Public page. brambles.ai/agentic-intent-exchange published at its permanent URL, with the share card and the beta request form.

2026-10-10

• Closed beta. Product-click handoff with recipient-bound signed receipts, identifier redaction and sensitive-category filtering, webhook delivery signed with a per-member secret, verified and applied acknowledgments, and outcome reporting against the exact receipt.