Agentic eSIM: your AI agent buys the plan, you scan the QR
An AI agent connected to SimFuse can compare live eSIM plans for 207 destinations, price a whole trip, and either hand the traveller a checkout link or open a session at frozen prices and pay with authorized funds. One keyless MCP endpoint, no SDK, no account to read the catalog. The one human step is scanning the QR.
Plain HTTP, no SDK to install, no sandbox to apply for. Add the MCP server to your client, or start with the discovery document and follow the links.
plans in the feed, no credential required to read it
destinations, delivered as an eSIM in seconds
registration steps to compare plans and get a checkout link
Connect in a few steps
One endpoint, no key. Point your client at the storefront MCP server and the tools below appear in the next chat. Browsing and checkout links need nothing else; a purchase the agent settles itself asks for a credential inside the session.
Endpoint: https://api.simfuse.app/agentic/mcp
The same server also answers at https://simfuse.app/agentic/mcp, so a client that knows only simfuse.app needs no second hostname.
In a terminal. Pass --scope user to keep it across projects.
claude mcp add --transport http simfuse https://api.simfuse.app/agentic/mcpSettings, Connectors, Add custom connector.
- Open Settings and choose Connectors.
- Choose Add custom connector and give it a name.
- Paste https://api.simfuse.app/agentic/mcp as the remote MCP server URL. No credential is asked for.
- Enable it in a chat and ask for a plan.
Developer mode, then a new connector with the server URL.
- Open Settings, then Security and login, and turn on Developer mode.
- Add a connector with the plus button and name it.
- Enter https://api.simfuse.app/agentic/mcp as the MCP server URL and create it.
- In a new chat, pick it from the More menu and ask for a plan.
.cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project.
{
"mcpServers": {
"simfuse": {
"url": "https://api.simfuse.app/agentic/mcp"
}
}
}.vscode/mcp.json in the workspace.
{
"servers": {
"simfuse": {
"type": "http",
"url": "https://api.simfuse.app/agentic/mcp"
}
}
}~/.gemini/settings.json, or the equivalent gemini mcp add command.
{
"mcpServers": {
"simfuse": {
"httpUrl": "https://api.simfuse.app/agentic/mcp"
}
}
}One endpoint, 15 tools
What the server lists today, in the order an agent uses them: find the right plan, buy it or hand over a link, then look after the eSIM once it is paid for.
Find the right plan
plan-tripread Answer "which eSIM should I buy for this trip?". Give it the stops, a country code and the days spent in each, and it compares one plan covering the whole route against one plan per country against a mix of the two, on live prices, then flags the cheapest option that covers everything and explains the choice in a sentence you can quote. It also estimates the data each stop needs, names any country SimFuse cannot cover, and returns package ids that go straight into create-checkout-session. Use it whenever a trip has two or more countries, and for a single country when the traveller wants a recommendation rather than a list. Read-only: nothing is reserved and nothing is charged, and the totals are today's catalog prices, not a quote held for later.list-destinationsread Find the countries SimFuse sells eSIMs for, with the cheapest plan price ("from" price) for each in the currency you ask for. Start here when someone names a place: it turns "Portugal" into the two-letter country code the other tools take, and shows what that destination starts at. For one destination, follow it with list-plans; for a trip covering two or more countries, use plan-trip instead. Read-only, and it answers from the SimFuse catalog alone.list-regionsread Discover available eSIM regions, including worldwide scopes, with their canonical slugs, display names, member countries and starting prices. Only published regions with active displayed regional plans are listed. Pass a returned region slug to list-plans as region, not destination. Country membership describes the region, not a promise that every plan covers every member: check get-plan-coverage for a specific plan. Read-only; no account or key is needed.get-destination-inforead Details for one destination: its name and codes, region, how many eSIM plans are sold there, the cheapest and most expensive, the smallest and largest data bundles, and its storefront page. Takes a country name ("Japan") or two-letter code ("JP"). Use this to describe a destination before pulling its full plan ladder with list-plans. Whether a plan can be topped up varies by plan and is reported by list-plans, not here.list-plansread Show the eSIM plans on sale for one country or region, or search the whole catalog, narrowing by data allowance, validity and price. Use destination with a country code from list-destinations, or region with a slug from list-regions; never both. Use it when the traveller wants to compare what is available or find a plan inside a budget. Prices are live retail prices in the currency you ask for. For a trip covering two or more countries, use plan-trip first: it compares one plan for the whole route against one plan per country and picks the cheapest complete answer. Pass a plan id from here to get-plan, get-plan-coverage or create-checkout-session. Read-only, and it answers from the SimFuse catalog alone.get-planread Read everything about one eSIM plan by its id: data allowance, how long it stays valid, what happens after a fair-use cap, whether hotspot and top-ups are supported, the network it runs on, and the retail price in the currency you ask for. Use it to answer a specific question about a plan already found with list-plans or plan-trip, and before buying, to confirm the plan really matches what the traveller asked for. Ask get-plan-coverage instead when the question is which countries it works in. Read-only: it reserves nothing and charges nothing.build-planread Build an eSIM plan to the traveller's liking for one destination: how much data, for how many days, optionally which network it runs on and whether calls and texts are bundled. Returns the one real plan that matches, with its id and live price, never a made-up combination: a shape nobody sells is snapped to the nearest one that is, one axis at a time, and every change is spelled out in `adjustments` so you can read it back. Use it when the traveller knows what they want ("10 GB on Docomo for two weeks"); use plan-trip when they want a recommendation or the trip has several countries. To buy, pass `plan.id` to get-checkout-link when a person is paying, or to create-checkout-session when you are. Read-only: it reserves nothing and charges nothing.get-plan-coverageread List every country one eSIM plan works in, plus any country of its own region that it leaves out. Use it to answer "does this plan also cover Austria?" for a regional or worldwide plan, where the plan name says a region and the traveller needs the actual list. For a single-country plan the answer is that one country. Ask get-plan instead for the data allowance, validity or price. Read-only.check-coverageread Answer "does this eSIM plan work in X?" for one destination, as a yes or no rather than a country list. Takes a plan id and a destination (a country name or two-letter code). Reports whether the destination is covered, and separately whether it is explicitly excluded from an otherwise regional plan. Use get-plan-coverage when you need the full list of countries instead.
Buy, or hand the traveller a link
get-checkout-linkread Get the page where a person buys one specific eSIM plan, for an assistant to hand them a link. The page sells exactly this plan with Apple Pay, Google Pay and card, takes the email at payment, and sends the eSIM there. Nothing is charged or reserved by this call and the buyer needs no account. Use this whenever a PERSON is going to pay. Use create-checkout-session instead when the agent is settling the purchase itself, or for more than one plan or unit.create-checkout-sessionbuys Open a checkout session for one or more eSIM plans at frozen prices, using the plan ids that plan-trip, list-plans or get-plan returned. Use it once the traveller has chosen what to buy. It CHARGES NOTHING and reserves no stock: it prices the basket, freezes those prices until the session's price_locked_until, and hands back the session plus a bearer agent key. Payment, completion and cancellation happen afterwards over the SimFuse agentic HTTP API with that key, as the session's `note` explains, and the eSIM is delivered by email once payment settles. Each call opens a NEW session and mints a NEW key, so call it once per basket rather than retrying it to re-read one.
After the purchase
get-order-statusread Check an eSIM order after payment: whether it completed and whether its eSIMs have been provisioned yet. Identified by the order id together with the email that bought it, both of which are on the buyer's confirmation email. Provisioning usually finishes within a minute of payment, so an order that is paid but lists no eSIMs yet is normal: check again shortly. Once an eSIM is listed, use get-esim-activation to fetch its QR code and install details.get-esim-activationread Fetch the installable eSIM(s) for a paid order: the QR code image, the LPA activation string, the SM-DP+ address and activation code for manual entry, one-tap install links for iPhone and Android, and a hosted install page to send the buyer. Identified by the order id together with the email that bought it. Returns an empty esims list while provisioning is still in flight, which normally clears within a minute of payment.check-esim-usageread How much data an eSIM has used and how much is left, for one eSIM on a paid order. Identified by the order id and the email that bought it, plus the ICCID from get-order-status or get-esim-activation. Allowances are in megabytes. Readings are served from a cache refreshed every couple of minutes: checked_at says when the reading was taken. An unlimited plan reports its full-speed allowance for the current period rather than a total.list-topup-optionsread Data top-ups that can be added to an eSIM the buyer already has, narrowed to what its network will actually accept. Identified by the order id and the email that bought it, plus the ICCID. Read-only: a top-up is bought in the SimFuse app, not through this server, and the response carries the link that opens this eSIM there. Do not pass these package ids to create-checkout-session, which would buy a separate new eSIM rather than add data to this one.
A real order, start to finish
Six calls from "I fly to Istanbul on Friday" to a QR code on the traveller's screen. Prices are frozen when the session opens, and nothing is charged until payment settles.
- Plan the trip. plan-trip takes the stops and the days in each and returns the plans that cover them, with live prices and per-GB rates. list-plans and get-plan narrow it down.
- Decide who pays. For a person paying by card or wallet, get-checkout-link returns the exact plan page and the agent is done. For a purchase the agent settles itself, create-checkout-session opens a session at frozen prices.
- Settle. A self-serve credential settles in cryptocurrency: the session returns a deposit address and an exact amount. x402 buys one plan in one request, in USDC on Base, synchronously. Vetted platforms can settle by card.
- Watch the order. get-order-status reports when payment completed and when the eSIM was provisioned, identified by the order id and the buyer's email.
- Fetch the eSIM. get-esim-activation returns the QR code image, the LPA string, the SM-DP+ address and the one-tap install links. This is the step a human has to finish: an agent cannot install a SIM on a phone.
- Look after it. check-esim-usage reports data used and left with the time it was checked; list-topup-options says which top-ups the eSIM's network will accept.
What answers today
Several ways in, one checkout engine behind all of them. There is no second catalog, no separate price list and no agent-only inventory: an agent buys the same plan at the same live price a traveller does.
- Agentic Commerce Protocol. The full seller API: create a checkout session, update it, complete it. We implement ACP directly rather than through a payment platform's suite, which is what lets us declare our own settlement handler. /.well-known/acp.json
- Universal Commerce Protocol. A shopping service at the same checkout engine, for clients that speak UCP instead. We declare only the checkout capability, because checkout is all we route. /.well-known/ucp
- Product feed. Every plan we sell, priced, with data allowance, validity and destination as structured attributes. Keyless on purpose: a catalog that needs a key to read is a catalog nobody crawls. /agentic/feeds/products
- Trip quote. One keyless GET prices a whole trip: pass the countries and the days in each, and the answer compares one plan covering the route against one per country against a mix, on live prices, with a stated reason and package ids that drop straight into a checkout session. The same trip opens in the planner for a human to see and edit. /agentic/trips/quote
- MCP server. A keyless Model Context Protocol server over Streamable HTTP. Compare plans and coverage, price a trip, and get a link for the traveller to pay on this site. Separate tools open agent checkout sessions and retrieve order status, installation details, usage and top-up options. Private order tools require the buyer's order details. /agentic/mcp
- OpenAPI and Machine Payment Protocol. The machine-readable description of the API, with pricing attached to the operations you can pay for. This is the document to hand a client that discovers services rather than being pointed at them. /openapi.json
- x402 on-chain purchase. One request buys one plan. Ask for a plan, get a 402 quoting the amount in USDC, sign the authorization, retry. Settlement is synchronous, so there is no pending window and nothing to poll. /agentic/x402/purchase/{id}
- Agent registration. How to get a credential, written for a reader that is not a person. Post your agent's name, receive a key, start buying. It is also reachable by following the WWW-Authenticate header on any 401 from us. /auth.md
Who is completing the purchase?
For a traveller paying by card or wallet, get-checkout-link returns the exact plan page without registration or a charge. The API sequence below is for an agent paying with authorized funds. Creating a session does not pay for it.
- Discover. Read the discovery document at our primary domain. It names the API base, the protocol version, the payment handlers we accept and where to register.
- Read the catalog. Page the product feed, or fetch a single plan's price. Ids in the feed are the ids checkout expects, so nothing has to be resolved in between.
- Register yourself. Post a name and get a key back. No form, no review, no waiting. The key lasts a year and is shown exactly once, so store it before you close the response.
- Open a checkout session. Create a session with the chosen plans, then follow its payment and completion instructions. Prices are frozen until price_locked_until. The eSIM is issued after payment settles; creating the session alone buys nothing.
# 1. Find us. Everything else is linked from here.
curl https://simfuse.app/.well-known/acp.json
# 2. Read the catalog. No credential needed.
curl "https://api.simfuse.app/agentic/feeds/products?per_page=5"
# 3. Register a credential for authorized agent purchases.
curl -X POST https://api.simfuse.app/agentic/keys \
-H "Content-Type: application/json" \
-d '{"agent_name":"my-assistant","contact_email":"[email protected]"}'
# 4. Open a session. Payment and completion are separate steps.
curl -X POST https://api.simfuse.app/agentic/checkout_sessions \
-H "Authorization: Bearer $SIMFUSE_AGENT_KEY" \
-H "Content-Type: application/json" \
-d '{"items":[{"id":"<package id from the feed>","quantity":1}],"currency":"EUR"}'Completing the session returns payment instructions for the handler you chose. The full request and response shapes are in the OpenAPI description. https://simfuse.app/openapi.json
Why this works here and stalls elsewhere
Most catalogs are technically reachable by an agent and practically unbuyable. Four things are usually in the way, and none of them is in the way here.
- The product is digital. There is no address to collect, no shipping to quote and no delivery window to promise. An eSIM is provisioned the moment payment settles, which removes most of what makes an agent purchase risky for a seller.
- The credential is self-serve. Registration is an endpoint, not an email thread. That is only safe because the self-serve scope settles prepaid, so there is nothing to charge back and no reason to vet anyone before letting them buy.
- The price is frozen, not guessed. Retail is live and multi-currency, so a quote that drifts between reading and paying is a real failure. Every session locks its prices, and the total is rebuilt from our catalog at settlement rather than read from what the client sent.
- The catalog is open. The feed needs no key, publishes structured attributes rather than prose, and every page on this site is also available as Markdown. An agent comparing options does not have to scrape a storefront to do it.
What your user actually receives
After payment and installation details are ready, get-esim-activation returns the QR code and install links. get-order-status checks progress; check-esim-usage reports usage with a checked_at timestamp. These tools require the order ID and buyer email. Usage and top-up lookups also need the eSIM's ICCID. list-topup-options shows available top-ups; buying one happens in the SimFuse app.
What we are building next
Stated plainly, because a roadmap that reads like a feature list is how you end up trusting a page that was describing an intention. None of the following has shipped.
- A SimFuse app in ChatGPT. Our MCP server is live, but eligibility for a listed ChatGPT integration is unresolved. OpenAI's current commerce rules restrict listings to physical goods and prohibit digital-product or service sales. An eSIM shopping integration needs eligibility clarification before we can promise a listing.
- A Claude connector. A directory listing would make our MCP server easier to find and connect. The listing has not shipped; connection and tool use remain subject to the assistant's supported features and permissions.
Here for a phone, not an API
Then none of the above matters. Pick a destination, pay, and the eSIM installs before you have finished packing. Browse plans by country
