Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the eSIM Zones API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fesim.digitalshop.app%2Fesim-digitalshop" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fesim.digitalshop.app%2Fesim-digitalshop" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with eSIM Zones API.
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
Patterns agents use eSIM Zones API for, with concrete tasks.
★ 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.
GET STARTED
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.
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.
Call the login endpoint to obtain an API token and confirm it authorizes a providers lookup
3 endpoints — the esim zones api returns the operators available in an esim location zone and the price range per gigabyte for that zone.
METHOD
PATH
DESCRIPTION
/api/login
Login and obtain an API token
/api/esim/zones/providers
Get providers by location zone
/api/esim/zones/priceRange
Get price range per gigabyte for a zone
/api/login
Login and obtain an API token
/api/esim/zones/providers
Get providers by location zone
/api/esim/zones/priceRange
Get price range per gigabyte for a zone
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using eSIM Zones API through Jentic.
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.
Know of an official OpenAPI document? Contribute it →
For 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.
Use for: I need to find eSIM providers for a location zone, Get the price range per GB in a zone, Obtain an API token to query eSIM zones, Check which operators cover a destination
Not supported: Does not handle eSIM purchase, activation, or data top-ups. Use for querying eSIM zone providers and price ranges only.
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.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>