documentation

Cuanto documentation

Integrate the Cuanto commerce layer — product discovery, the AI shopping assistant, and revenue attribution — into your app, agent, or site.

Anyone can browse this reference. To get live credentials — a Partner token and Partner UUID — apply for partner access, or sign in if you already have an account.

Request partner access Partner sign in

introduction

What you get

One integration to monetize purchase intent across 1B+ products and 21,000+ brands.

Cuanto is the commerce layer for AI. Surface relevant products, let shoppers buy through affiliate links, and earn commission on every attributed purchase — through whichever surface fits your app:

API — REST endpoints for catalogue search, redirects, reports, and webhooks.
MCP server — a read-only tool surface so AI agents can search your catalogue.
CASH — the embeddable AI shopping-assistant chat (hosted brain + streaming API).
Widget — drop-in <script> that mounts CASH on any page.
CALM Studio — generate campaign images and videos for the products you promote.

authentication

Credentials

Find both on the API Setup page.

Partner tokensecret: Private bearer credential for all authenticated API + MCP calls. Sent as Authorization: Partner <token>. Never expose it in client-side code except the widget, where it is the widget key.
Partner UUIDpublic: Your public attribution id. Safe to embed in redirect links (?partner_uuid=…). It identifies you for attribution but does not authenticate protected APIs.

Base URLs

API https://api.getcuanto.ai · Redirects https://getcuanto.ai/redirect · MCP https://api.getcuanto.ai/api/v1/partners/mcp

Never expose or share your Partner token

Your Partner token authenticates every protected API, MCP, and widget call — treat it like a password. Never commit it, log it, or share it outside your own systems, and never call protected endpoints directly from a browser you don’t control. The one deliberate exception is the Widget embed (see the Widget tab for what that means and how to reduce risk). If a token ever leaks, rotate it from the API Setup page immediately.

5 minutes

Quickstart

Authenticated catalogue search → redirect.

1 · Search the catalogue

bash

curl https://api.getcuanto.ai/api/v1/partners/catalogue/offers?search=running+shoes \
  -H "Authorization: Partner $CUANTO_PARTNER_TOKEN"

2 · Every row carries a ready-to-use redirect_url

json

{
  "status": "SUCCESS",
  "total_results": 1,
  "data": [
    {
      "merchant_uuid": "8f3c…",
      "seller_name": "Acme Running",
      "commission": 7.5,
      "commission_type": "PERCENTAGE",
      "currency": "USD",
      "redirect_url": "https://getcuanto.ai/redirect?target_type=offer&merchant_uuid=8f3c…&partner_uuid=YOUR_UUID"
    }
  ]
}

3 · Send the shopper through it (optionally stamping your own click id)

text

https://getcuanto.ai/redirect?target_type=offer&merchant_uuid=8f3c…&partner_uuid=YOUR_UUID&partner_tracking_id=order_42

The click is recorded, the shopper lands on the merchant, and when the purchase confirms you’re paid and notified via webhook. Full flow under Attribution.

conventions

Response envelope

Every JSON endpoint returns the same envelope:

json

{ "status": "SUCCESS", "data": { /* object or array */ }, "total_results": 1 }

Errors use standard HTTP codes: 401 bad/missing token, 403 a feature isn’t enabled on your account, 400 invalid params.