Shopping · head-to-head
BuyWhere vs Rappi
BuyWhere runs a live product-search API backed by a real, large product catalog spanning merchants across seven Southeast Asian and North American markets, purpose-built for AI shopping agents. Access is gated by a Bearer API key with a published free/Starter/Pro/Enterprise pricing ladder rather than an open, unauthenticated feed. Its CORS policy only serves an Access-Control-Allow-Origin header to allow-listed origins, so arbitrary browser-side callers get no such header even though the API answers preflight requests.
Rappi's public API lets approved merchant partners manage store menus and orders across its Latin American on-demand delivery platform. Access requires a formal partnership and uses OAuth2 — Authorization Code with PKCE for partner-facing flows, plus Auth0-issued bearer tokens for machine-to-machine calls — confirmed live against its login/token gateway. Each country Rappi operates in runs its own regional API host.
| BuyWhere | Rappi | |
|---|---|---|
| Authentication | API Key | OAuth |
| Pricing | freemium | free |
| Formats | JSON | JSON |
| CORS | no | yes |
| HTTPS | Yes | Yes |
Rappi supports CORS, while BuyWhere doesn't — pick Rappi for direct browser calls.