Reloadly API vs cartapi MCP: which should your agent call?
Integrate Reloadly directly if you are a business that already runs payments and fraud, wants wholesale pricing, and is building a storefront. Use cartapi (which is built on Reloadly) if you are building an AI agent and want top-ups and gift cards as MCP tools with a consumer checkout the user signs, without becoming the merchant yourself. The two are layers, not rivals.
If you are wiring airtime or gift cards into an AI agent, you will end up at Reloadly: its APIs sit under a lot of the top-up and gift-card market. The real question is whether your agent should call Reloadly directly or call a layer built on it. I run one of those layers, so here is where going direct is the right answer, and where it isn't.
What Reloadly is
Reloadly is a B2B wholesaler with separate REST APIs for airtime top-ups, gift cards, and utility payments. Its gift card API page advertises 3,000+ brands and 14,000+ gift card options, multi-currency wallets in USD, EUR, CAD, and GBP, code samples in seven languages, WordPress/Shopify/WooCommerce plugins, free signup, and no monthly minimums. You fund a wallet, call the API, and Reloadly fulfils against your balance.
That is exactly what a wholesaler should be. What it isn't is an agent product: there's no consumer checkout, no consent step, and no tool schema an LLM can call out of the box.
What cartapi adds on top
cartapi's top-up and gift-card categories are Reloadly underneath. The layer adds:
- An MCP server at
https://mcp.cartapi.io/mcpwith tools likesearch_topups,create_topup_checkout,search_gift_cards,list_gift_card_brands,get_checkout_link, andget_order_status. A REST API mirrors it (see the docs). - Consumer checkout the user signs. Checkout returns a Stripe-hosted URL; the agent hands it over and never touches card data. See Consent-first checkout.
- Merchant of record. cartapi is the MoR, so disputes and refunds land with it, not with you. Background: Merchant of record for AI-agent purchases.
- One neutral catalog. Top-ups and gift cards via Reloadly, plus travel eSIMs from Airalo and Nomad, in one search with explicit agent-controlled sort.
- Agent-safe mutations. Every mutation accepts an
Idempotency-Key, so an agent retrying on a timeout doesn't double-charge.
Feature comparison
| Reloadly API (direct) | cartapi MCP / REST | |
|---|---|---|
| Who it's for | Businesses building their own storefront, rewards, or payouts | AI-agent builders and apps that want buyer-signed checkout |
| Interface | REST per product, SDKs, plugins | MCP (Streamable HTTP) + REST |
| Auth | OAuth client credentials, one token per product audience | MCP currently open; REST uses a bearer API key |
| Who pays | You, from a prefunded wallet | The end user, on a Stripe-hosted page |
| Merchant of record | You | cartapi |
| Fraud screening on consumer payments | Yours to build | Handled (gift cards sold cross-border only) |
| Pricing | Wholesale | Consumer price above wholesale |
| Gift-card catalog | 3,000+ brands advertised | 305+ brands across 156 countries (docs), a subset of Reloadly |
| Top-up coverage | Reloadly's full operator list | 136 countries (docs) |
| eSIMs in the same call | No | Yes (Airalo, Nomad) |
| Carrier detection | Separate lookup call you orchestrate | Built into create_topup_checkout |
What integrating Reloadly directly actually involves
From building cartapi's adapters, the work you sign up for when you go direct:
1. Two products, two tokens
You authenticate with OAuth client credentials at https://auth.reloadly.com/oauth/token, passing an audience per product: https://topups.reloadly.com for airtime and https://giftcards.reloadly.com for gift cards, each with a -sandbox twin. Tokens expire (Reloadly's official Python library notes their finite lifetime), so you cache per audience and refresh. Each API also expects its own versioned Accept header, such as application/com.reloadly.topups-v1+json.
2. A catalog you sync yourself
Operators come back paginated (we page through /operators?includeBundles=true&size=200). Prices are quoted in your wallet's sender currency, so a USD-facing product needs your own FX step. cartapi re-syncs the catalog every 6 hours and refreshes FX daily from ECB rates before it converts costs; you will want something similar.
3. Operator detection and portability
Top-ups need the serving operator, and prefixes lie in markets with number portability. You call an operator lookup per number, ideally with a cache. We cache lookups for 7 days per number.
4. Payments and fraud
This is the part people underestimate. Gift cards are cash-like, and stolen cards find them fast. Our early gift-card orders taught us that a domestic buyer paying a premium over local retail is a strong fraud signal, which is why cartapi now authorizes gift-card payments with manual capture and only captures when the card is issued outside the gift card's country. Going direct, that whole layer is yours.
5. An agent interface
None of the above is an MCP tool yet. You still write tool schemas, consent rules, and the "don't call checkout without the user's go-ahead" instruction. Our server instructions say exactly that.
When to go direct to Reloadly
- You already operate payments, KYC, and fraud screening, and want the wholesale margin.
- You need brands or operators outside the subset cartapi exposes.
- You are building rewards or payouts, where your company pays rather than the end user.
- You are building a classic storefront (WooCommerce, Shopify) where Reloadly's plugins already fit.
When to call cartapi instead
- You are building an agent and want working commerce tools in one line of config.
- The user should pay, and you don't want to hold their card or become the merchant.
- You want top-ups, gift cards, and travel eSIMs behind one search, with no provider hidden for margin.
- You are prototyping and would rather ship than build an OAuth cache, sync job, FX layer, and fraud gate first.
Many teams will do both over time: start on the agent layer, then go direct for the one category where volume justifies the wholesale integration. That's a healthy outcome.
Trying the agent layer in one minute
claude mcp add --transport http cartapi https://mcp.cartapi.io/mcp
using cartapi, list the PlayStation gift card regions you have, then top-up options for Glo Nigeria
Both calls are read-only. Nothing is bought until a checkout tool runs and the user pays on Stripe. For the wider landscape of agent commerce servers, see MCP servers for e-commerce; for the gift-card API vendors aimed at HR rewards rather than agents, see cartapi vs Tremendous, Giftbit, Givex.
Frequently asked questions
Is cartapi a Reloadly competitor?
No. cartapi's top-up and gift-card categories are sourced from Reloadly. It adds MCP, consumer checkout, MoR, and a multi-provider catalog.
Does Reloadly have an MCP server?
Reloadly publishes REST APIs, SDKs, a Postman collection, and plugins. For MCP, wrap the REST API yourself or use an existing server like cartapi's.
How does Reloadly API authentication work?
OAuth client credentials against auth.reloadly.com/oauth/token, with an audience per product (topups, giftcards, and sandbox twins). Tokens expire; cache and refresh per audience.
When should I integrate Reloadly directly?
When you already run payments and fraud, want wholesale pricing, need the full catalog, or are building a non-agent storefront.
Is cartapi more expensive than Reloadly?
Yes, per unit. You trade margin for not running payments, fraud screening, FX, or catalog sync yourself.