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.

​
AAP Overview

The Agent Attribution Protocol gives agent-driven recommendations a verifiable commercial trail. Rako operates the AAP infrastructure: it indexes merchant-approved offers, issues signed AAP Codes, records recommendation events, carries attribution metadata into checkout, reconciles conversions, and settles commission. An AAP flow is: 
search → recommend → checkout → convert → settle
AAP is infrastructure for attribution and settlement. It is not a token, wallet, blockchain, or consumer tracking layer. The protocol answers one operational question: did this conversion flow through a recorded agent recommendation that Rako can verify?

​
Core objects

ObjectPurpose
OfferA merchant product, service, or payable action available for agent recommendation.
SessionA bounded user intent window created when an agent searches offers.
RecommendationThe attribution event: an agent presents a specific offer in a session.
AAP CodeA signed offer code generated by Rako and embedded into checkout metadata.
CheckoutA payment link, merchant checkout handoff, or vertical-specific application flow.
ConversionThe ledger record connecting the recommendation to a merchant outcome.
SettlementThe validation and payout process after refund, dispute, and milestone windows.
The canonical protocol specification remains in rakohq/aap-spec. These docs explain how to use it with Rako APIs and SDKs.