In June there was exactly one way to buy an eSIM by talking to an AI assistant. By September, around ten providers claim some flavour of “agent-ready”, and a Claude or ChatGPT user asking to buy connectivity will be routed to whichever server the model happens to know. We went through every provider’s live documentation on 7 September 2026 and compared what an agent actually gets. Where a claim below is about someone else’s product, it links to their own page — and we re-check these figures on a schedule, because a comparison that rots is worse than none.
The four questions that separate the field
Marketing aside, eSIM MCP servers differ on four axes, and they decide whether your agent completes a purchase in one conversation or stalls on a signup form:
1. What does browsing cost? Can the agent see the catalog anonymously, or does the very first tool call need a key?
2. What does buying cost? An API key from a dashboard, an OAuth dance, a partner contract — or nothing but a funded balance?
3. What shape is the pricing? Fixed packages with validity windows force the agent to predict usage; metered billing lets it pay for what the task consumed.
4. Which rails, and whose name? Cards need a cardholder. Stablecoins don’t. KYC requirements decide whether an autonomous agent can be the customer at all.
At a glance
| Server | Browse | Buy | Pricing shape | Rails |
|---|---|---|---|---|
Roamzy (roamzy.io/mcp) | Anonymous | Anonymous — account is minted on the first tool call, no key, no signup | Metered per MB, no packages, no expiry | USDT / USDC, min top-up $20 |
PikaSim (pikasim.com/mcp) | Anonymous (6 public tools) | Wallet code via OAuth or Bearer key | 2,300+ fixed packages | BTC, Lightning, Monero, USDT; min $10 |
eSIMAccess (mcp.esimaccess.com) | Partner credentials required | OAuth 2.1 + PKCE over a partner account | B2B packages (prices not public) | Not disclosed on the MCP surface |
| esim.dog | API key (REST; MCP claimed, endpoint not documented) | API key | Fixed plans (GB × days) | Stripe + crypto |
| VoidMob | “MCP for AI Agents” advertised; no public endpoint or tool docs found | Fixed, from $2.99 | BTC, ETH, SOL + more | |
Everything in this table was read from each provider’s live pages on 7 September 2026 and is tagged to its source; if a provider changes their docs, tell us and we’ll update the row.
Roamzy — anonymous-first, metered, no expiry
Our server is built around one bet: the agent should never leave the conversation. https://roamzy.io/mcp answers without authentication — an anonymous account is created on the first tool call, and buying needs nothing beyond a funded balance. No API key, no OAuth screen, no email. The catalog covers 193 countries at metered per-MB rates: the floor is $0.61 per GB ($0.0006/MB), the catalog median is $3.69 per GB, and nothing expires — no validity windows, no packages to size. The agent pays for the megabytes the task used, which is the pricing shape a machine can actually reason about: see eSIM for AI agents for the full flow and the MCP server page for setup.
Honest limits: rails are USDT/USDC only — no cards, by design — and the minimum top-up is $20, higher than PikaSim’s $10. Spending limits (daily / monthly / per-transaction) are set by the agent on its own token, and there’s a 20% recurring referral if your product brings users.
PikaSim — the credible alternative
PikaSim ships the most complete competitor implementation: 15 tools split across a public browse endpoint and a wallet-authenticated purchase endpoint. Their rails are the widest of the field — Bitcoin, Lightning, Monero and USDT, with a $10 wallet minimum — and there’s a reseller program with its own key type. The trade-off is the pricing shape: 2,300+ fixed packages means the agent must predict how much data the trip needs and when it stops needing it. If your agent values Lightning or Monero over metered billing, this is the one to test against ours.
eSIMAccess — B2B, not a consumer agent’s first purchase
eSIMAccess documents 17 tools behind a properly-built OAuth 2.1 + PKCE flow, with scoped permissions down to destructive operations. But the flow rides on a partner account with API credentials — AccessCode and SecretKey — so it’s an integration surface for businesses reselling eSIMs, not something an end user’s agent can walk up to. No prices or payment methods are published on the MCP surface. If you’re building an eSIM product on top of a wholesale platform, it belongs on your shortlist; if you’re an agent buying one eSIM for one trip, it isn’t addressed to you.
esim.dog and VoidMob — claimed, not yet documented
esim.dog advertises MCP spec compliance, but what’s actually documented is a REST API behind a Bearer API key — with the notable distinction of accepting Stripe + crypto, the only cards-capable option in this comparison, and a “no KYC” policy that carries a per-country asterisk. VoidMob announces “MCP for AI Agents” with eSIMs from $2.99 paid in BTC/ETH/SOL, but at check time there was no public endpoint or tool documentation to evaluate. Both may ship real servers tomorrow — this section will be updated when they do.
Try it in one paste
Point any MCP client at the streamable-HTTP endpoint and ask it to price a trip — no account first:
{
"mcpServers": {
"roamzy": { "url": "https://roamzy.io/mcp" }
}
}The first tool call creates an anonymous account with tight default limits; funding it is a stablecoin invoice away. The full agent flow — limits, confirmation thresholds, claim links — lives on /ai-agents, live rates on /prices, and the deeper background in Best eSIM for AI agents and how agents pay with x402 & stablecoins.
Verdict
If your agent needs one eSIM bought inside one conversation with zero setup, anonymous-first metered billing is the only shape that fits — that’s us. If your priority is Lightning or Monero rails and you’re comfortable sizing packages, PikaSim is the credible alternative. If you’re a business building a reseller product, eSIMAccess is the B2B route. And if a provider’s agent story is a landing-page badge with no endpoint behind it — that’s worth exactly what your agent can fetch: nothing, yet.