How it works

How agent commerce works through Rako.

Rako connects merchants, AI agents, and attribution events without replacing checkout, custodying funds, or relying on browser-era affiliate tracking.

Request access See the demo
A central Rako attribution hub connecting a merchant storefront, AI agent, checkout, and verification node
Merchant checkout stays in place
No funds custody
No scraping
Attribution built in
Works with AAP

The flow in five steps

The flow in five steps

Five Rako process cards showing offer import, agent search, AI recommendation, merchant checkout, and attribution match

Who controls what

Merchant controls

  • Checkout experience
  • PSP and payment handling
  • Customer relationship
  • Product data and availability
  • Commercial terms and pricing

Rako handles

  • Structured offer layer
  • Recommendation records
  • Attribution matching
  • Reporting and analytics
  • Commission logic

Agents get

  • Cleaner, structured offer access
  • Less scraping and overhead
  • Recommendation credit
  • Better discovery infrastructure
  • Connected attribution

What moves through the system

Search event

Agent captures user intent and search context.

->

Recommendation event

Agent requests and receives offers for the intent.

->

Checkout handoff

Agent hands off the user to merchant checkout.

->

Conversion event

Merchant/PSP confirms order, amount, and customer.

->

Attribution match

Rako matches recommendation and conversion events.

->

Commission record

Commission is calculated and recorded.

Example: attribution match event

{
  "event_type": "attribution.match",
  "event_id": "evt_a1YDUt72C8hbK_GP1T3M2D4C7",
  "timestamp": "2025-05-10T14:32:09Z",
  "agent_id": "agt_Ba1Jd",
  "merchant_id": "mct_73e91c",
  "order_id": "ord_C6ee21",
  "amount": 449.00,
  "currency": "GBP",
  "commission": 22.45,
  "status": "matched"
}

Every step emits a verifiable event. Rako connects them into a clean, tamper-evident attribution record.

  • No cookies or browser dependency
  • Agent-native events and context
  • Built on AAP for interoperability

Not legacy affiliate tracking

Legacy model

  • Clicks and redirects
  • Cookies and browser sessions
  • Last-click attribution
  • Hard-to-verify influence
  • Lost in cross-device journeys
VS

Rako model

  • Recommendation events with context
  • Merchant checkout, no interference
  • Conversion matching and attribution
  • Agent-verified influence
  • Cleaner data, fairer commissions

Ready to make your offers agent-ready?

Join the infrastructure layer for agent-native commerce.

Request merchant access Read the docs