← cartapi.io blog

Reloadly API vs cartapi MCP: which should your agent call?

Published 2026-11-09 · Last updated 2026-11-09 · 8 min read · agent commerce
TL;DR

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:

Feature comparison

Reloadly API (direct)cartapi MCP / REST
Who it's forBusinesses building their own storefront, rewards, or payoutsAI-agent builders and apps that want buyer-signed checkout
InterfaceREST per product, SDKs, pluginsMCP (Streamable HTTP) + REST
AuthOAuth client credentials, one token per product audienceMCP currently open; REST uses a bearer API key
Who paysYou, from a prefunded walletThe end user, on a Stripe-hosted page
Merchant of recordYoucartapi
Fraud screening on consumer paymentsYours to buildHandled (gift cards sold cross-border only)
PricingWholesaleConsumer price above wholesale
Gift-card catalog3,000+ brands advertised305+ brands across 156 countries (docs), a subset of Reloadly
Top-up coverageReloadly's full operator list136 countries (docs)
eSIMs in the same callNoYes (Airalo, Nomad)
Carrier detectionSeparate lookup call you orchestrateBuilt 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

When to call cartapi instead

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.

About the author

Roc Chow

Roc Chow builds cartapi, the commerce layer for AI agents, and runs . The integration details here come from writing and running cartapi's Reloadly top-up and gift-card adapters in production.

LinkedIn · · cartapi.io