Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rako.sh/llms.txt

Use this file to discover all available pages before exploring further.

​
Commission Flow

Rako connects agent recommendations to merchant outcomes. Every recommendation creates attribution context that can later be reconciled into a payable conversion.

​
Three steps

Your agent queries Rako for offers matching user intent: vertical, price, features, provider, contract length, or other structured criteria. Rako returns eligible offers and a session ID.

​
2. Recommend

When the agent recommends a product, it calls recommend. This records the attribution event: the agent influenced the user toward a specific offer.

​
3. Checkout and earn

When the user is ready to buy, checkout starts the purchase path. The merchant or payment provider handles payment, while Rako keeps the attribution and conversion ledger authoritative.

​
How attribution survives

  • No cookies required. Attribution is logged server-side when the recommendation is recorded.
  • Cross-device safe. The session ID ties the recommendation to the eventual purchase or payable milestone.
  • Drop-off recovery. Recommendations can return fallback links that preserve attribution if the user does not buy immediately.
  • Verifiable offers. AAP Codes prove that an offer is authentic, priced correctly, and commission-eligible.

​
Settlement levels

Rako supports multiple evidence models depending on merchant integration depth:
  1. Merchant-reported — the merchant reports payable outcomes.
  2. Payment-observed — payment or PSP events confirm transaction status.
  3. Payment-split — commission is split as part of transaction clearing.