canonical: https://jentic.com/apis/esim.digitalshop.app/esim-digitalshop # Esim Digitalshop App eSIM Zones API The eSIM Zones API returns the operators available in an eSIM location zone and the price range per gigabyte for that zone. A login endpoint issues the API token the data endpoints need, and every request routes through OpenCart's single entry point. It is a lookup surface for eSIM coverage and pricing by zone rather than a purchase or activation flow. ## For AI agents Query the operators available in an eSIM location zone and the price range per gigabyte, after obtaining an API token via login. Covers zone and pricing lookups, not purchase or activation. ## Scope Does not handle eSIM purchase, activation, or data top-ups. Use for querying eSIM zone providers and price ranges only. ## Capabilities - Obtain an API token through the login endpoint - List the operators and providers available in a given eSIM location zone - Retrieve the price range per gigabyte for a location zone ## Use cases ### Agent eSIM Price Comparison An AI agent connected through Jentic looks up the price range per gigabyte for the destination zone a traveller names and lists the operators that serve it, so it can present coverage and cost side by side. The agent obtains a token through the login endpoint first, then queries the zone data without touching a purchase flow. Example prompt: Obtain an API token, then look up the operators and price range per gigabyte for a destination zone ### Coverage Lookup by Zone A travel assistant checks which operators cover a given location zone before recommending an eSIM, using the providers lookup to confirm availability. The result is scoped to the zone the traveller is heading to, so the assistant answers with coverage specific to the destination. Example prompt: List the operators available in a specific eSIM location zone and report which carriers are covered ### Token-Based Access Setup An integration obtains an API token from the login endpoint and then uses it to query the zone and pricing endpoints, sending it as the token query parameter or the X-API-Token header. This one-time login gives a reusable token that the data lookups require. Example prompt: Call the login endpoint to obtain an API token and confirm it authorizes a providers lookup ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/login` | Login and obtain an API token | | GET | `/api/esim/zones/providers` | Get providers by location zone | | GET | `/api/esim/zones/priceRange` | Get price range per gigabyte for a zone | ## Key resources - **Zones** — Query providers and price ranges per gigabyte by eSIM location zone - **Authentication** — Obtain an API token via the login endpoint ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 63 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 90 / 100 - Developer Experience & Jentic Compatibility: 73 / 100 - AI-Readiness & Agent Experience: 44 / 100 - Agent Usability: 94 / 100 - Security: 42 / 100 - AI Discoverability: 83 / 100 - **View full report:** https://jentic.com/apis/esim.digitalshop.app/esim-digitalshop/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the eSIM Zones API by hand means logging in to obtain an API token, then sending it either as the token query parameter or the X-API-Token header, and routing every call through OpenCart's single index.php entry point. Through Jentic you install once, import the eSIM Zones API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The eSIM Zones API carries the location zone in the request rather than the URL path, so rules bound which operations your agent may call rather than which zone. Limit it to the provider and price-range lookups it needs, and include the login operation only when the agent must mint a fresh token. - **Credential handling:** Your eSIM Zones API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'eSIM providers for a zone' or 'eSIM price per GB', and Jentic returns the matching eSIM Zones operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **1NCE API** — Manages cellular IoT connectivity and SIMs directly, where eSIM Zones only reports operator coverage and pricing by zone. - **Telnyx API** — Provides wireless and telecom services that complement eSIM Zones' coverage and pricing data. - **Sinch API** — Adds mobile messaging on top of the connectivity an eSIM provides. ## FAQ ### What authentication does the eSIM Zones API use? The eSIM Zones API uses an API token obtained from its login endpoint, sent either as the token query parameter or the X-API-Token header, and it also accepts a bearer token per its OpenAPI spec. The login endpoint itself needs no token. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context. ### Can I get eSIM providers and prices for a zone with the eSIM Zones API? Yes. One lookup returns the operators available in a location zone and another returns the price range per gigabyte for that zone. Both run against the zone you pass, so the agent gets coverage and cost scoped to a single destination. ### Can I limit what my agent is allowed to do with the eSIM Zones API? Yes. Write a rule that allows only the providers and price-range lookups, so your agent can read eSIM coverage and pricing, and add the login operation only when the agent must mint a fresh token. Every call it makes is logged. ### What are the rate limits for the eSIM Zones API? The OpenAPI spec does not state rate limits for the eSIM Zones API. Check the eSIM Zones or Digital Shop documentation for the limits that apply to your token. ### How do I look up eSIM providers with the eSIM Zones API through Jentic? Search Jentic for 'eSIM providers for a location zone' and it returns the providers lookup with its input schema; your agent obtains a token through login, passes the zone, and reads back the operators. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there an eSIM Zones MCP server? You don't need an MCP server to give your agent the eSIM Zones API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the zone and pricing lookups with scoping and credential isolation applied.