One path from ideato live eSIM.
The same engine powers your web dashboard, your API calls, and the tools your AI assistant runs. Start in one and continue in another without a rewrite.
Four steps
Build
Define an offer with countries, data size, and price. Draft offers remain inactive until you publish.
Test
Test the offer in the sandbox. The sandbox exercises the integration flow. It does not install a live eSIM.
Launch
Publish the offer and start creating eSIMs. Every eSIM is created under a stable request ID, so a retry never produces a second one.
Manage
Assign data plans, monitor usage and expiry, and handle exceptions from the Console or from your own tools.
One product, three surfaces
Console
The web dashboard for your team: offers, data plans, customers and QR codes.
API
One HTTP API for every operation. The Console and the API are the same product underneath.
AI tools (MCP)
The same operations as tools for an AI assistant such as Claude or Cursor. Not every Console action has an AI tool yet; the API reference lists what is available.
The rules that hold
Safe to retry
An eSIM is created under the ID of your request. A repeated call returns the same result instead of creating another eSIM.
An unclear result is not a failure
When a provider returns an unclear outcome, Carrier keeps the order open for manual reconciliation instead of creating the eSIM again.
Sponsored claims are capped
A sponsored claim reserves funds before an eSIM is created, and a cost ceiling per claim is set for each deployment.
Try it in the sandbox
Build a product in the sandbox and issue a test eSIM. Going live is a separate step.