Install Jentic One Beta

Connect the esimoa Partner API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the esimoa Partner 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%2Fesimoa.com%2Fesimoa" | sh

Step 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%2Fesimoa.com%2Fesimoa" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with esimoa Partner API.

Search and compare travel eSIM plans by destination country, validity days, and data allowance

Filter results to unlimited-data plans, a specific provider, or multi-country plans

Retrieve the full details of one eSIM plan by its id

List the countries that currently have eSIM plans on sale

Return a purchase link carrying your partner code so purchases earn a commission

GET STARTED

Start building with esimoa Partner API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use esimoa Partner API for, with concrete tasks.

★ Travel eSIM Comparison

A travel assistant finds the right data plan for an upcoming trip. The esimoa Partner API searches plans by destination country, validity in days, and minimum data, and can narrow results to unlimited plans or a single provider, returning comparable options with prices so the traveller can choose before departure.

Search esimoa for eSIM plans with country JP and a minimum data allowance, sorted by the recommended order, and return the top options with prices

Affiliate eSIM Recommendations

A publisher embeds eSIM recommendations that earn commission. The esimoa Partner API returns a purchase link with the publisher's partner code on every plan, so an agent can surface a best-fit plan for a destination and hand back a link the reader can buy through while attributing the sale.

Fetch the details for a chosen eSIM plan by its id and return its partner purchase link for the reader

AI Agent Travel Planning via Jentic

An AI travel agent adds connectivity to a trip plan through Jentic without holding the esimoa API key itself. It searches by intent, receives the matching operation and its input schema, and queries plans with the credential injected at run time, so it can recommend a data plan alongside flights and lodging.

Search Jentic for 'compare travel eSIM plans', load the search operation schema, and query plans for the destination with Jentic-managed credentials

Key Endpoints

3 endpoints — the esimoa partner api searches and compares travel esim plans sold by esimoa, filtering by destination country, validity in days, and data allowance.

METHOD

PATH

DESCRIPTION

GET

/v1/esims

Search and compare eSIM plans

GET

/v1/esims/{id}

Get the details of one eSIM plan

GET

/v1/countries

List countries with plans on sale

GET

/v1/esims

Search and compare eSIM plans

GET

/v1/esims/{id}

Get the details of one eSIM plan

GET

/v1/countries

List countries with plans on sale

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring esimoa by hand means sending its X-API-Key header, building the query filters for country and data, and threading your partner code through every purchase link yourself. Through Jentic you install once, import esimoa from the API Directory, store the key once, and your agent calls it.

Permission scoping

This API is read-only: every operation is a GET for searching plans, reading one plan, or listing countries, so a rule can confine your agent to those reads and nothing that changes account state. You choose which of the three operations it may call.

Credential isolation

Your esimoa partner key 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 'compare travel eSIM plans' or 'list countries with eSIM plans', and Jentic returns the matching esimoa operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using esimoa Partner API through Jentic.

What authentication does the esimoa Partner API use?

The esimoa Partner API authenticates with an API key sent in the X-API-Key header per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

Can I filter eSIM plans by country and data with the esimoa Partner API?

Yes. The search operation accepts query filters for the destination country, the validity in days, a minimum or maximum data allowance, unlimited-data-only, a specific provider, and multi-country plans. An agent can combine these to return a short, comparable list of plans for a trip.

What are the rate limits for the esimoa Partner API?

The OpenAPI spec does not specify rate limits for the esimoa Partner API. Check the esimoa developer documentation for current limits, and use the search operation's limit and offset parameters to page through results efficiently.

How do I compare eSIM plans with the esimoa Partner API through Jentic?

Search Jentic for 'compare travel eSIM plans' and it returns the esimoa search operation with its input schema. Load the schema, pass the destination and data filters, and the key is injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the esimoa Partner API?

Yes. Every operation in this API is a read-only GET, so a rule can confine your agent to searching plans, fetching plan details, and listing countries, and nothing that changes state. You choose which of the three reads it may call, and every request runs through your own instance where it is logged.

Is there an esimoa Partner API MCP server?

You don't need an MCP server to give your agent the esimoa Partner API. Jentic connects it directly from the API Directory: import it, store your partner key once, and your agent calls the search and countries operations it needs without a separate server to install.

esimoa Partner API

AI ReadinessAI-Aware (B-)60/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceStorefrontapiKey3 EndpointsREST

For Agents

Search and compare travel eSIM plans by country, duration, and data, fetch a single plan by id, and list destinations with plans on sale. Each result carries a partner purchase link. Authenticated with an X-API-Key header.

Use for: Search for eSIM plans for a trip to Japan, Find unlimited-data eSIM plans for France, Italy, and Spain, Compare eSIM plans by price and data allowance, Get the details and purchase link for a specific eSIM plan

Not supported: Does not handle eSIM activation, provisioning, or payment processing. Use for searching and comparing travel eSIM plans only.

The esimoa Partner API searches and compares travel eSIM plans sold by esimoa, filtering by destination country, validity in days, and data allowance. Each result includes a purchase link carrying your partner code, so purchases made through it earn a commission. A countries operation lists the destinations that currently have plans on sale, and plan details can be fetched by id.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

42%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

33%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

43%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the esimoa Partner API to your agent

Capabilities

Start building with esimoa Partner API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

esimoa Partner API

Jentic AI Readiness Score

esimoa Partner API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness