AAP Overview

The Agent Attribution Protocol gives agent-driven recommendations a verifiable commercial trail. Rako operates AAP infrastructure for offer indexing, signed AAP Codes, recommendation events, attribution metadata, conversion reconciliation, and settlement workflows. 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

Object	Purpose
Offer	A merchant product, service, or payable action available for agent recommendation.
Session	A bounded user intent window created when an agent searches offers.
Recommendation	The attribution event: an agent presents a specific offer in a session.
AAP Code	A signed offer code generated by Rako and embedded into checkout metadata.
Checkout	A payment link, merchant checkout handoff, or vertical-specific application flow.
Conversion	The ledger record connecting the recommendation to a merchant outcome.
Settlement	The 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.