Search offers, recommend products, earn commission. Use Rako's MCP server for
zero-code integration, or the JavaScript and Python SDKs for full control.
MCP Server
The fastest way to connect an agent to Rako. Add the MCP server to Claude Desktop,
Cursor, or any MCP-compatible client — your agent gets three tools: search_offers, recommend, and checkout.
Record a recommendation and log the attribution event. This is how commission is earned.
Parameter
Type
Required
Description
session_id
string
Yes
Session ID from search_offers
offer_id
string
Yes
ID of the offer to recommend
context
string
No
Why this offer was recommended
checkout
Initiate checkout for a recommended offer.
Parameter
Type
Required
Description
session_id
string
Yes
Session ID from search_offers
recommendation_id
string
Yes
Recommendation ID from recommend
Example Conversation
MCP conversation flow
User: I need a new SIM deal. Cheap, at least 10GB, no contract.
Agent: [calls search_offers(vertical="sim", min_data_gb=10, contract_months=0)]
I found 4 options:
1. SMARTY 30GB — £10/mo (Three network, no credit check)
2. giffgaff 10GB — £10/mo (O2, 5G included)
3. giffgaff 25GB — £12/mo (O2, 5G included)
4. Lebara 5GB — £5/mo (Vodafone)
I'd recommend SMARTY 30GB — 3x the data at the same price.
[calls recommend(session_id, offer_id, context="Best value")]
User: Sounds good, let's go with SMARTY.
Agent: [calls checkout(session_id, recommendation_id)]
Done! Here's your checkout link: https://aap.link/r/...
JavaScript / TypeScript SDK
Full control from Node.js, Deno, or Bun. Type-safe, zero dependencies.
Three steps from search to earning commission. Every recommendation creates a
cryptographically signed attribution record.
1
Search
Your agent queries Rako for offers matching user intent — vertical, price,
features. Returns structured data with a session ID that tracks the journey.
2
Recommend
When your agent recommends a product, it calls recommend().
This is the attribution event — Rako records that your agent influenced the decision.
3
Checkout & Earn
When the user is ready to buy, checkout() initiates
the purchase. The merchant's PSP handles payment — Rako settles commission
as a post-transaction receivable.
How attribution survives
No cookies needed. Attribution is logged
server-side when recommend() is called,
not when a link is clicked.
Cross-device safe. The session ID ties
the recommendation to the eventual purchase, even if the user switches devices.
Drop-off recovery. Every recommendation
returns a fallbackUrl —
if the user doesn't buy immediately, the link preserves attribution for later.
Verifiable. Each offer carries a cryptographic
signature (AAP Code) that proves it's real, priced correctly, and commission-eligible.
Supported Verticals
Rako supports multiple verticals. Pass any of these to the vertical parameter when searching.
sim
SIM Deals
Pay-monthly and pay-as-you-go SIM-only plans
broadband
Broadband
Home broadband and fibre packages
energy
Energy
Gas and electricity tariffs
flights
Flights
Flight offers and deals
hotels
Hotels
Hotel accommodation and packages
insurance
Insurance
Insurance products and policies
Ready to connect your agent?
Get an API key and start earning commission on agent-driven sales. Free until 2028 for early adopters.