IbiPoint eSIM Catalog

Server Details

Search prepaid travel eSIM data plans for 200+ countries with live prices and a buy link.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 41 days
Last Tested: 2026-10-23 12:33
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A4.1/5.0

Scored 2026-10-18 17:30 across 5 tools

Disambiguation4/5

Each tool has a fairly distinct role: search for destinations, recommend for trip descriptions, get_plan_details for a single product id, get_shop_facts for general info, and start_checkout for purchase. The main overlap is search_esim_plans vs recommend_plan, which both return plan facts, but the descriptions explicitly state when to use which, so an agent can reasonably choose.

Naming Consistency5/5

All names follow a clean verb_noun snake_case pattern (get_plan_details, get_shop_facts, recommend_plan, search_esim_plans, start_checkout). No mixed conventions or vague verbs.

Tool Count4/5

Five tools is a lean but sensible surface for a catalog/recommendation/checkout server, with no redundant filler. It is on the sparse side, but every tool covers a distinct step in the journey.

Completeness4/5

The set covers the full path from discovery (search, recommend) through detail (get_plan_details, get_shop_facts) to purchase (start_checkout). Order tracking is explicitly out of scope and no post-purchase or comparison/lookup-by-id gaps are severe enough to block typical workflows.

Available Tools

5 tools

get_plan_detailsGet plan detailsA

Read-onlyIdempotent

Inspect

Full facts for one IbiPoint plan by product id: coverage with networks per country, data and speed rules, activation and validity rules, top-up, tethering, price with basis (per-day plans: price_30_days and price_max), reviews and link — quoted in the customer's bucket or currency when given.

ParametersJSON Schema

Name	Required	Description
`bucket`	No	Optional language-region bucket the customer shops in, e.g. "en-gb", "de-de". Wins over language; prices and links are quoted in it.
`currency`	No	Optional ISO 4217 code. Every price in the result is quoted in it.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare "en" is quoted in en-us / USD.
`product_id`	Yes	Product id from search_esim_plans or recommend_plan.

Output Schema

ParametersJSON Schema

Name	Required	Description
`sku`	No	Catalogue SKU.
`url`	No	Product page in pricing_bucket. Use verbatim.
`data`	No	Data Pack: total data label, e.g. "5GB".
`days`	No	Validity in days (Data Pack).
`name`	No	Short plan name: destination · data · validity · type.
`type`	No	Plan type.
`price`	No	Price in currency, read WITH price_basis: the full price of the plan when "total", the price of ONE day when "per_day". Never a per-GB rate. The price shown is the price paid.
`title`	No	Full product title in the requested language.
`topup`	No	Top-up possibility for this plan.
`rating`	No	Average customer rating (1-5). Present only when reviews exist.
`data_gb`	No	Data amount in GB. Meaning given by data_period.
`summary`	No	Short description in the requested language, from the product page.
`currency`	No	ISO 4217 currency of every price in this object.
`fair_use`	No	Fair-use policy text from the supplier, when stated.
`networks`	No	Operator names across the plan (deduplicated). Per-country detail is in coverage_countries.
`validity`	No	Validity label, e.g. "30 days".
`plan_note`	No	One-sentence vendor fact to present verbatim when present; overrides the generic type description.
`price_max`	No	Only on price_basis "per_day": the price for the longest duration in days_range (365 days), discount applied. Never infer it by multiplying.
`tethering`	No	Hotspot / tethering is supported where the network and device allow it (shop rule).
`voice_sms`	No	Always "none": data only, no telephone number, no SMS.
`covers_via`	No	Present when the plan was returned for a country it covers as part of a multi-country plan: the plan's own region name.
`days_range`	No	Unlimited Flex: choosable durations in days, "1-365".
`expires_on`	No	Stock expiry date (YYYY-MM-DD) when the product itself has one.
`product_id`	No	Product id. Use it for get_plan_details and start_checkout.
`data_period`	No	"total": data_gb is the whole plan (Data Pack). "per_day": data_gb is the daily full-speed allowance (Unlimited Flex).
`ip_breakout`	No	Country whose internet connection the customer appears to use (IP breakout), ISO code(s) — matters for banking apps, streaming and mainland-China access. Vendor fact.
`price_basis`	No	What `price` means.
`last_updated`	No	Date the plan was last updated in the catalogue (YYYY-MM-DD).
`review_count`	No	Number of reviews. Present only when > 0.
`transparency`	No	A per-order Transparency link shows remaining data in near real-time.
`coverage_note`	No	Coverage caveat to present verbatim, e.g. traffic routed via Hong Kong.
`price_30_days`	No	Only on price_basis "per_day": the price for 30 days with the duration discount applied — the reference figure to quote for a stay of about a month. Never infer it by multiplying.
`always_on_rate`	No	Unlimited Flex: reduced speed after the daily allowance, e.g. "512 Kbit/s". Empty when the plan is unlimited.
`coverage_count`	No	Number of countries in coverage_countries.
`price_is_final`	No	Always true: no tax or fee is added at checkout.
`pricing_bucket`	No	language-region bucket the prices and links are quoted in, e.g. "en-us".
`daily_high_speed`	No	Unlimited Flex: daily allowance at full speed, e.g. "2GB"; "unlimited" = unlimited data every day at full speed (fair-use policy).
`unused_valid_days`	No	Days the eSIM may remain unused after purchase before it expires (supplier value).
`activation_trigger`	No	"install": validity and billing start the moment the eSIM is installed — install only when ready to use. "first_connection": the eSIM can be installed before travel; validity starts on first connection to a network at the destination.
`coverage_countries`	No	Every country the plan works in, with the network operators per country when known.
`network_generation`	No	Network technology, e.g. "4G/LTE/5G". Never an operator name.
`install_before_travel`	No	true when the eSIM can safely be installed before departure (activation_trigger first_connection).

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description still adds real behavioral context: quotes are localized to the provided bucket/currency, and pricing is returned with an explicit basis, including price_30_days and price_max for per-day plans. It does not discuss rate limits or pagination, but for a read-only lookup that is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that opens with the core action ('Full facts for one IbiPoint plan by product id') before the field list. It is dense and every clause maps to returned content, though the long comma-chain of fields makes it slightly heavy for a one-sentence description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not detail return structure, yet it still names the major returned sections, which is helpful. Combined with annotations and full schema coverage, an agent has everything needed to call it correctly; only the when-to-use relationship to siblings is unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3: bucket, currency, language and product_id are all already documented with precedence (bucket wins over language). The description only echoes the quoting behavior ('quoted in the customer's bucket or currency when given') and adds no format or edge-case detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (retrieve full facts for one plan) scoped tightly by product id, then enumerates exactly what those facts are: coverage/networks, data and speed rules, activation, validity, top-up, tethering, pricing, reviews. This clearly separates it from the sibling search_esim_plans (discovery) and recommend_plan (suggestion), since it is the single-plan lookup keyed by an id those tools produce.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by product id' and the schema note that the id comes from search_esim_plans or recommend_plan imply the follow-up-detail workflow, but the description itself never states when to call this versus those siblings, nor any precondition or exclusion. Usage is inferable rather than declared.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_shop_factsShop factsA

Read-onlyIdempotent

Inspect

How IbiPoint works, in the shop's own words: delivery and installation, device requirements, payment methods, money-back guarantee, top-up, hotspot, support and company details. Use for any "how / when / what if" question that is not about one specific plan.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered before the description is read. The description adds the useful framing that content is authoritative 'in the shop's own words' and reads as static reference data, but says nothing about freshness, caching, or scope of the returned corpus.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: the first front-loads the resource and its topic coverage, the second gives the usage condition. The topic list is long but each item is a distinct content category that helps an agent judge coverage, so it earns its space; only minor tightening is possible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not explain return values, and its enumeration of covered topics tells the agent whether this tool can answer a given question. What remains missing is any hint about the shape/granularity of the returned facts or whether the corpus is complete, but for a zero-parameter reference lookup this is close to sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly does not waste space inventing arguments, instead describing what the fixed response contains.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (IbiPoint shop facts) and enumerates exactly what it covers: delivery/installation, device requirements, payment methods, guarantee, top-up, hotspot, support, company details. It also distinguishes itself from plan-specific siblings with the phrase 'not about one specific plan,' so an agent can tell it apart from get_plan_details without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering condition — any 'how / when / what if' question — and an explicit exclusion, questions about one specific plan, which implicitly routes the agent to get_plan_details. It stops short of naming the alternative tool or describing the boundary for other siblings (recommend_plan, start_checkout), so it is strong but not fully explicit routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

recommend_planRecommend a plan for a tripA

Read-onlyIdempotent

Inspect

Turn a trip into up to three plan recommendations: countries (1-5, any language), number of days and how much data the traveller uses. Each fit carries the full plan facts, the total price for the whole trip and a one-sentence reason built only from catalogue facts. Use this first whenever the user describes a trip rather than asks for a list.

ParametersJSON Schema

Name	Required	Description
`days`	Yes	Trip length in days.
`usage`	No	light ≈ 0.5 GB/day (maps, messaging), normal ≈ 1.5 GB/day (social, some video), heavy ≈ 4 GB/day (video, hotspot). Default normal.
`bucket`	No	Optional language-region bucket the customer shops in, e.g. "en-gb", "de-de". Wins over language; prices and links are quoted in it.
`budget`	No	Optional maximum total for the trip, in the result currency.
`currency`	No	Optional ISO 4217 code. Every price in the result is quoted in it.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare "en" is quoted in en-us / USD.
`countries`	Yes	Countries or regions of the trip, any language.
`gb_per_day`	No	Overrides usage with an explicit daily need in GB.

Output Schema

ParametersJSON Schema

Name	Required	Description
`trip`	No
`message`	No
`currency`	No
`all_plans_url`	No
`pricing_bucket`	No
`recommendations`	No

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds behavior beyond that: results are capped at three fits, each carries full plan facts plus a total trip price, and the reason is constrained to catalogue facts only. It does not mention auth needs, rate limits, or fallback behavior when nothing fits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences, front-loaded with the purpose and output shape before the routing instruction. Little waste, though the middle clause is dense enough that it could be split for scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter read tool with an output schema, the description covers purpose, output shape, and routing, so return-format gaps are excused by the output schema. Missing only explicit sibling naming and edge-case behavior, which are minor given the structured coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 8 parameters in detail. The description only restates countries (1-5, any language), days, and data usage, adding no format or constraint detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Turn a trip into up to three plan recommendations') and enumerates the core inputs (countries, days, data usage). It also implicitly distinguishes itself from the list-oriented sibling by framing itself as the trip-description entry point rather than a list search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this first whenever the user describes a trip rather than asks for a list,' giving both a when-to-use and a contrasting condition that routes to a list-style sibling. It stops short of naming that sibling (search_esim_plans) or stating exclusions, so it is clear but not fully prescriptive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_esim_plansFind eSIM plansA

Read-onlyIdempotent

Inspect

Find IbiPoint eSIM plans for one destination or several (countries or regions, any language). Returns the best-value plans first with full facts, coverage lists and a direct link; multi-country plans that include the destination are returned too and marked covers_via. Use when a user wants mobile data abroad; use recommend_plan when they describe a whole trip.

ParametersJSON Schema

Name	Required	Description
`sort`	No	value = best price per GB / cheapest Flex first (default); price = cheapest first; data = most data first.
`type`	No	Plan type. Default any.
`limit`	No	Plans to return. Default 10; all_plans_url lists everything.
`bucket`	No	Optional language-region bucket the customer shops in, e.g. "en-gb", "de-de". Wins over language; prices and links are quoted in it.
`currency`	No	Optional ISO 4217 code. Every price in the result is quoted in it.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare "en" is quoted in en-us / USD.
`min_days`	No	Only plans valid for at least this many days (Unlimited Flex counts when days_range allows it).
`destination`	No	Country or region in any language, e.g. "Thailand", "Japon", "Europa", or a 2-letter ISO code. For a city, pass its country.
`destinations`	No	Several countries for one trip; only plans covering ALL of them are returned. Overrides destination.

Output Schema

ParametersJSON Schema

Name	Required	Description
`iso`	No	Resolved ISO code or region slug of the (first) destination.
`note`	No	Present when part of the request could not be honoured (e.g. more than 5 destinations).
`plans`	No
`covered`	No
`message`	No	Present when nothing matched: says why and what to try.
`currency`	No
`returned`	No
`from_price`	No	Lowest price in this result set, shop-formatted (per-day plans count with their day price).
`destination`	No
`destinations`	No	How each requested destination was understood.
`all_plans_url`	No
`pricing_bucket`	No
`total_available`	No	Plans matched before limit; the rest are on all_plans_url.

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (read-only, idempotent, non-destructive, open-world), but the description adds ranking behavior ('best-value plans first'), the covers_via marking for multi-country plans, and what is bundled in the result (facts, coverage lists, direct link). It stops short of pagination or rate-limit context, so a 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with zero waste. The core purpose is front-loaded, and the covers_via detail and routing hint are packed without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with 9 optional params, no required params, and an output schema that carries return values, the description supplies purpose, routing, and result shape. An agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 9 parameters including enums and examples. The description adds only the destination/multi-destination framing, matching the baseline 3 for a fully-documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Find') and resource ('IbiPoint eSIM plans'), plus scope ('one destination or several'). It also names the sibling it is not (recommend_plan), so an agent can route without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use trigger ('a user wants mobile data abroad') and a named alternative with its selecting condition ('use recommend_plan when they describe a whole trip'). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

start_checkoutStart secure checkoutA

Read-onlyIdempotent

Inspect

Hand the customer to the IbiPoint shop to buy one plan. Returns buy_url (the product page where they tap Buy now and pay securely — card, Apple Pay, Google Pay, PayPal, Amazon Pay, Klarna or a local method such as iDEAL | Wero, Bancontact, BLIK or Pix, with an optional discount code) plus the plan name and price in the customer's bucket or currency. No account needed; the eSIM is emailed right after payment. There is no in-chat order tracking.

ParametersJSON Schema

Name	Required	Description
`days`	No	Unlimited Flex only: the duration the customer wants; the returned total_for_days is the checkout total for it.
`bucket`	No	Optional language-region bucket the customer shops in, e.g. "en-gb", "de-de". Wins over language; prices and links are quoted in it.
`currency`	No	Optional ISO 4217 code. Every price in the result is quoted in it.
`language`	No	ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare "en" is quoted in en-us / USD.
`product_id`	Yes	Product id to buy.

Output Schema

ParametersJSON Schema

Name	Required	Description
`days`	No
`price`	No	Read WITH price_basis.
`buy_url`	No	The exact product page to send the customer to. Use verbatim.
`message`	No
`product`	No
`currency`	No
`app_links`	No	Optional store links of the free IbiPoint app (android, ios) - the eSIM works without it.
`price_max`	No
`days_range`	No
`product_id`	No
`price_basis`	No
`presentation`	No
`price_30_days`	No	Unlimited Flex: price for 30 days, discount applied.
`price_is_final`	No
`pricing_bucket`	No
`total_for_days`	No	Unlimited Flex: checkout total for the requested days, discount applied.

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds real context beyond the annotations: the operation is a hand-off that returns a URL, no account is required, the eSIM is emailed after payment, and there is no in-chat order tracking. This is consistent with readOnlyHint/idempotentHint (it only mints a link). It stops short of stating idempotency semantics or any rate/expiry limits on buy_url.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, then return values, then caveats. The parenthetical listing every payment method is long and could be trimmed, but it is defensible context for reassuring a customer; overall it is dense but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering the safety profile, the description is close to complete: it explains the hand-off, the delivery mechanism, and the absence of order tracking. The one gap is explicit routing guidance relative to the plan-discovery siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all five parameters, including bucket precedence over language and currency quoting. The description reinforces the bucket/currency interplay ('in the customer's bucket or currency') but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Hand the customer to the IbiPoint shop to buy one plan') and enumerates the concrete return artifacts (buy_url, plan name, price). An agent can distinguish this checkout hand-off from the read-only siblings get_plan_details, recommend_plan and search_esim_plans without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the agent infers it should call this once a plan is chosen and the customer is ready to pay. The clause 'There is no in-chat order tracking' usefully rules out a follow-up behavior, but no alternative sibling is named and no precondition (e.g. call recommend_plan first) is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

5 tool updatesSep 29, 2026

Changedget_plan_details53 fields changed

addedInput schema / properties / bucket

Added value: +{
+  "description": "Optional language-region bucket the customer shops in, e.g. \"en-gb\", \"de-de\". Wins over language; prices and links are quoted in it.",
+  "type": "string"
+}

addedInput schema / properties / currency

Added value: +{
+  "description": "Optional ISO 4217 code. Every price in the result is quoted in it.",
+  "type": "string"
+}

changedInput schema / properties / language / description

Previous value: -"ISO language of the conversation. Sets the landing-page language/currency of the link."New value: +"ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare \"en\" is quoted in en-us / USD."

changedInput schema / properties / product_id / description

Previous value: -"WooCommerce product id from search_esim_plans."New value: +"Product id from search_esim_plans or recommend_plan."

addedOutput schema / description

Added value: +"One eSIM plan. Every field is present only when the catalogue holds a value for it; an absent field is unknown, never \"no\"."

addedOutput schema / properties / activation_trigger

Added value: +{
+  "description": "\"install\": validity and billing start the moment the eSIM is installed — install only when ready to use. \"first_connection\": the eSIM can be installed before travel; validity starts on first connection to a network at the destination.",
+  "enum": [
+    "install",
+    "first_connection"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / always_on_rate / description

Previous value: -"Unlimited Flex: reduced rate after the daily allowance."New value: +"Unlimited Flex: reduced speed after the daily allowance, e.g. \"512 Kbit/s\". Empty when the plan is unlimited."

addedOutput schema / properties / coverage_count

Added value: +{
+  "description": "Number of countries in coverage_countries.",
+  "type": "integer"
+}

addedOutput schema / properties / coverage_countries

Added value: +{
+  "description": "Every country the plan works in, with the network operators per country when known.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "iso": {
+        "description": "ISO 3166-1 alpha-2, lowercase.",
+        "type": "string"
+      },
+      "name": {
+        "description": "Country name in the requested language.",
+        "type": "string"
+      },
+      "networks": {
+        "description": "Operator names in that country, as the supplier lists them.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / coverage_note

Added value: +{
+  "description": "Coverage caveat to present verbatim, e.g. traffic routed via Hong Kong.",
+  "type": "string"
+}

addedOutput schema / properties / covers_via

Added value: +{
+  "description": "Present when the plan was returned for a country it covers as part of a multi-country plan: the plan's own region name.",
+  "type": "string"
+}

addedOutput schema / properties / currency / description

Added value: +"ISO 4217 currency of every price in this object."

changedOutput schema / properties / daily_high_speed / description

Previous value: -"Unlimited Flex: daily high-speed allowance."New value: +"Unlimited Flex: daily allowance at full speed, e.g. \"2GB\"; \"unlimited\" = unlimited data every day at full speed (fair-use policy)."

changedOutput schema / properties / data / description

Previous value: -"Data Pack: total data label."New value: +"Data Pack: total data label, e.g. \"5GB\"."

addedOutput schema / properties / data_gb / description

Added value: +"Data amount in GB. Meaning given by data_period."

addedOutput schema / properties / data_period

Added value: +{
+  "description": "\"total\": data_gb is the whole plan (Data Pack). \"per_day\": data_gb is the daily full-speed allowance (Unlimited Flex).",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / days

Added value: +{
+  "description": "Validity in days (Data Pack).",
+  "type": "integer"
+}

changedOutput schema / properties / days_range / description

Previous value: -"Only on price_basis \"per_day\": the durations the customer can choose, in days, e.g. \"1-365\"."New value: +"Unlimited Flex: choosable durations in days, \"1-365\"."

removedOutput schema / properties / description
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / expires_on

Added value: +{
+  "description": "Stock expiry date (YYYY-MM-DD) when the product itself has one.",
+  "type": "string"
+}

addedOutput schema / properties / fair_use

Added value: +{
+  "description": "Fair-use policy text from the supplier, when stated.",
+  "type": "string"
+}

addedOutput schema / properties / install_before_travel

Added value: +{
+  "description": "true when the eSIM can safely be installed before departure (activation_trigger first_connection).",
+  "type": "boolean"
+}

addedOutput schema / properties / ip_breakout

Added value: +{
+  "description": "Country whose internet connection the customer appears to use (IP breakout), ISO code(s) — matters for banking apps, streaming and mainland-China access. Vendor fact.",
+  "type": "string"
+}

addedOutput schema / properties / last_updated

Added value: +{
+  "description": "Date the plan was last updated in the catalogue (YYYY-MM-DD).",
+  "type": "string"
+}

addedOutput schema / properties / name / description

Added value: +"Short plan name: destination · data · validity · type."

removedOutput schema / properties / network

Removed value: -{
-  "description": "Speed token only (e.g. 4G/LTE/5G) — never a carrier/operator name.",
-  "type": "string"
-}

addedOutput schema / properties / network_generation

Added value: +{
+  "description": "Network technology, e.g. \"4G/LTE/5G\". Never an operator name.",
+  "type": "string"
+}

addedOutput schema / properties / networks

Added value: +{
+  "description": "Operator names across the plan (deduplicated). Per-country detail is in coverage_countries.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / plan_note

Added value: +{
+  "description": "One-sentence vendor fact to present verbatim when present; overrides the generic type description.",
+  "type": "string"
+}

changedOutput schema / properties / price / description

Previous value: -"Price in currency, to be read WITH price_basis: the full fixed price of the plan when price_basis is \"total\", the price of one day when it is \"per_day\". Never a per-GB rate."New value: +"Price in currency, read WITH price_basis: the full price of the plan when \"total\", the price of ONE day when \"per_day\". Never a per-GB rate. The price shown is the price paid."

changedOutput schema / properties / price_30_days / description

Previous value: -"Only on price_basis \"per_day\": the price for 30 days with the duration discount applied — the reference figure to quote for a stay of about a month. Absent when it cannot be computed; never infer it by multiplying price."New value: +"Only on price_basis \"per_day\": the price for 30 days with the duration discount applied — the reference figure to quote for a stay of about a month. Never infer it by multiplying."

changedOutput schema / properties / price_basis / description

Previous value: -"What `price` means. \"total\" = the whole plan (Data Pack). \"per_day\" = one day (Unlimited Flex): the duration is chosen at checkout within days_range; see price_30_days and price_max."New value: +"What `price` means."

addedOutput schema / properties / price_is_final

Added value: +{
+  "description": "Always true: no tax or fee is added at checkout.",
+  "type": "boolean"
+}

changedOutput schema / properties / price_max / description

Previous value: -"Only on price_basis \"per_day\": the price for the longest duration in days_range, discount applied. Absent when it cannot be computed; never infer it by multiplying price."New value: +"Only on price_basis \"per_day\": the price for the longest duration in days_range (365 days), discount applied. Never infer it by multiplying."

addedOutput schema / properties / pricing_bucket

Added value: +{
+  "description": "language-region bucket the prices and links are quoted in, e.g. \"en-us\".",
+  "type": "string"
+}

addedOutput schema / properties / product_id / description

Added value: +"Product id. Use it for get_plan_details and start_checkout."

addedOutput schema / properties / rating / description

Added value: +"Average customer rating (1-5). Present only when reviews exist."

addedOutput schema / properties / review_count / description

Added value: +"Number of reviews. Present only when > 0."

addedOutput schema / properties / sku

Added value: +{
+  "description": "Catalogue SKU.",
+  "type": "string"
+}

addedOutput schema / properties / summary

Added value: +{
+  "description": "Short description in the requested language, from the product page.",
+  "type": "string"
+}

addedOutput schema / properties / tethering / description

Added value: +"Hotspot / tethering is supported where the network and device allow it (shop rule)."

addedOutput schema / properties / title

Added value: +{
+  "description": "Full product title in the requested language.",
+  "type": "string"
+}

addedOutput schema / properties / topup / additionalProperties
```
Added value: +true
```
addedOutput schema / properties / topup / description
```
Added value: +"Top-up possibility for this plan."
```

addedOutput schema / properties / topup / properties

Added value: +{
+  "how": {
+    "description": "How the customer tops up.",
+    "type": "string"
+  },
+  "kind": {
+    "description": "What TopUp can add without a new eSIM: data (Data Pack), days (Unlimited Flex), or none.",
+    "enum": [
+      "data",
+      "days",
+      "none"
+    ],
+    "type": "string"
+  }
+}

changedOutput schema / properties / topup / type

Previous value: -"boolean"New value: +"object"

addedOutput schema / properties / transparency / description

Added value: +"A per-order Transparency link shows remaining data in near real-time."

changedOutput schema / properties / type / description

Previous value: -"Data Pack or Unlimited Flex."New value: +"Plan type."

addedOutput schema / properties / type / enum

Added value: +[
+  "Data Pack",
+  "Unlimited Flex"
+]

addedOutput schema / properties / unused_valid_days

Added value: +{
+  "description": "Days the eSIM may remain unused after purchase before it expires (supplier value).",
+  "type": "integer"
+}

addedOutput schema / properties / url / description

Added value: +"Product page in pricing_bucket. Use verbatim."

changedOutput schema / properties / validity / description

Previous value: -"Data Pack: validity label."New value: +"Validity label, e.g. \"30 days\"."

addedOutput schema / properties / voice_sms

Added value: +{
+  "description": "Always \"none\": data only, no telephone number, no SMS.",
+  "type": "string"
+}

Addedget_shop_facts
Addedrecommend_plan

Changedsearch_esim_plans66 fields changed

addedInput schema / properties / bucket

Added value: +{
+  "description": "Optional language-region bucket the customer shops in, e.g. \"en-gb\", \"de-de\". Wins over language; prices and links are quoted in it.",
+  "type": "string"
+}

changedInput schema / properties / currency / description

Previous value: -"Optional ISO 4217 override for the headline \"from\" price. Normally derived from language."New value: +"Optional ISO 4217 code. Every price in the result is quoted in it."

changedInput schema / properties / destination / description

Previous value: -"Country or region, e.g. \"Thailand\", \"Japan\", \"Europe\". City names are mapped to their country."New value: +"Country or region in any language, e.g. \"Thailand\", \"Japon\", \"Europa\", or a 2-letter ISO code. For a city, pass its country."

addedInput schema / properties / destinations

Added value: +{
+  "description": "Several countries for one trip; only plans covering ALL of them are returned. Overrides destination.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 5,
+  "type": "array"
+}

changedInput schema / properties / language / description

Previous value: -"ISO language of the conversation, e.g. en, de, ja, th. Sets the landing-page language and currency."New value: +"ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare \"en\" is quoted in en-us / USD."

addedInput schema / properties / limit

Added value: +{
+  "description": "Plans to return. Default 10; all_plans_url lists everything.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / min_days

Added value: +{
+  "description": "Only plans valid for at least this many days (Unlimited Flex counts when days_range allows it).",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "value = best price per GB / cheapest Flex first (default); price = cheapest first; data = most data first.",
+  "enum": [
+    "value",
+    "price",
+    "data"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "destination"
-]New value: +[]

addedOutput schema / properties / destinations

Added value: +{
+  "description": "How each requested destination was understood.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "iso": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "query": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / from_price / description

Previous value: -"Localized \"from\" price string."New value: +"Lowest price in this result set, shop-formatted (per-day plans count with their day price)."

addedOutput schema / properties / iso / description

Added value: +"Resolved ISO code or region slug of the (first) destination."

addedOutput schema / properties / message / description

Added value: +"Present when nothing matched: says why and what to try."

addedOutput schema / properties / note

Added value: +{
+  "description": "Present when part of the request could not be honoured (e.g. more than 5 destinations).",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / description

Added value: +"One eSIM plan. Every field is present only when the catalogue holds a value for it; an absent field is unknown, never \"no\"."

addedOutput schema / properties / plans / items / properties / activation_trigger

Added value: +{
+  "description": "\"install\": validity and billing start the moment the eSIM is installed — install only when ready to use. \"first_connection\": the eSIM can be installed before travel; validity starts on first connection to a network at the destination.",
+  "enum": [
+    "install",
+    "first_connection"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / plans / items / properties / always_on_rate / description

Previous value: -"Unlimited Flex: reduced rate after the daily allowance."New value: +"Unlimited Flex: reduced speed after the daily allowance, e.g. \"512 Kbit/s\". Empty when the plan is unlimited."

addedOutput schema / properties / plans / items / properties / coverage_count

Added value: +{
+  "description": "Number of countries in coverage_countries.",
+  "type": "integer"
+}

addedOutput schema / properties / plans / items / properties / coverage_countries

Added value: +{
+  "description": "Every country the plan works in, with the network operators per country when known.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "iso": {
+        "description": "ISO 3166-1 alpha-2, lowercase.",
+        "type": "string"
+      },
+      "name": {
+        "description": "Country name in the requested language.",
+        "type": "string"
+      },
+      "networks": {
+        "description": "Operator names in that country, as the supplier lists them.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / plans / items / properties / coverage_note

Added value: +{
+  "description": "Coverage caveat to present verbatim, e.g. traffic routed via Hong Kong.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / covers_via

Added value: +{
+  "description": "Present when the plan was returned for a country it covers as part of a multi-country plan: the plan's own region name.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / currency / description
```
Added value: +"ISO 4217 currency of every price in this object."
```

changedOutput schema / properties / plans / items / properties / daily_high_speed / description

Previous value: -"Unlimited Flex: daily high-speed allowance."New value: +"Unlimited Flex: daily allowance at full speed, e.g. \"2GB\"; \"unlimited\" = unlimited data every day at full speed (fair-use policy)."

changedOutput schema / properties / plans / items / properties / data / description

Previous value: -"Data Pack: total data label."New value: +"Data Pack: total data label, e.g. \"5GB\"."

addedOutput schema / properties / plans / items / properties / data_gb / description
```
Added value: +"Data amount in GB. Meaning given by data_period."
```

addedOutput schema / properties / plans / items / properties / data_period

Added value: +{
+  "description": "\"total\": data_gb is the whole plan (Data Pack). \"per_day\": data_gb is the daily full-speed allowance (Unlimited Flex).",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / days

Added value: +{
+  "description": "Validity in days (Data Pack).",
+  "type": "integer"
+}

changedOutput schema / properties / plans / items / properties / days_range / description

Previous value: -"Only on price_basis \"per_day\": the durations the customer can choose, in days, e.g. \"1-365\"."New value: +"Unlimited Flex: choosable durations in days, \"1-365\"."

removedOutput schema / properties / plans / items / properties / description
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / plans / items / properties / expires_on

Added value: +{
+  "description": "Stock expiry date (YYYY-MM-DD) when the product itself has one.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / fair_use

Added value: +{
+  "description": "Fair-use policy text from the supplier, when stated.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / install_before_travel

Added value: +{
+  "description": "true when the eSIM can safely be installed before departure (activation_trigger first_connection).",
+  "type": "boolean"
+}

addedOutput schema / properties / plans / items / properties / ip_breakout

Added value: +{
+  "description": "Country whose internet connection the customer appears to use (IP breakout), ISO code(s) — matters for banking apps, streaming and mainland-China access. Vendor fact.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / last_updated

Added value: +{
+  "description": "Date the plan was last updated in the catalogue (YYYY-MM-DD).",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / name / description
```
Added value: +"Short plan name: destination · data · validity · type."
```

removedOutput schema / properties / plans / items / properties / network

Removed value: -{
-  "description": "Speed token only (e.g. 4G/LTE/5G) — never a carrier/operator name.",
-  "type": "string"
-}

addedOutput schema / properties / plans / items / properties / network_generation

Added value: +{
+  "description": "Network technology, e.g. \"4G/LTE/5G\". Never an operator name.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / networks

Added value: +{
+  "description": "Operator names across the plan (deduplicated). Per-country detail is in coverage_countries.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / plans / items / properties / plan_note

Added value: +{
+  "description": "One-sentence vendor fact to present verbatim when present; overrides the generic type description.",
+  "type": "string"
+}

changedOutput schema / properties / plans / items / properties / price / description

Previous value: -"Price in currency, to be read WITH price_basis: the full fixed price of the plan when price_basis is \"total\", the price of one day when it is \"per_day\". Never a per-GB rate."New value: +"Price in currency, read WITH price_basis: the full price of the plan when \"total\", the price of ONE day when \"per_day\". Never a per-GB rate. The price shown is the price paid."

changedOutput schema / properties / plans / items / properties / price_30_days / description

Previous value: -"Only on price_basis \"per_day\": the price for 30 days with the duration discount applied — the reference figure to quote for a stay of about a month. Absent when it cannot be computed; never infer it by multiplying price."New value: +"Only on price_basis \"per_day\": the price for 30 days with the duration discount applied — the reference figure to quote for a stay of about a month. Never infer it by multiplying."

changedOutput schema / properties / plans / items / properties / price_basis / description

Previous value: -"What `price` means. \"total\" = the whole plan (Data Pack). \"per_day\" = one day (Unlimited Flex): the duration is chosen at checkout within days_range; see price_30_days and price_max."New value: +"What `price` means."

addedOutput schema / properties / plans / items / properties / price_is_final

Added value: +{
+  "description": "Always true: no tax or fee is added at checkout.",
+  "type": "boolean"
+}

changedOutput schema / properties / plans / items / properties / price_max / description

Previous value: -"Only on price_basis \"per_day\": the price for the longest duration in days_range, discount applied. Absent when it cannot be computed; never infer it by multiplying price."New value: +"Only on price_basis \"per_day\": the price for the longest duration in days_range (365 days), discount applied. Never infer it by multiplying."

addedOutput schema / properties / plans / items / properties / pricing_bucket

Added value: +{
+  "description": "language-region bucket the prices and links are quoted in, e.g. \"en-us\".",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / product_id / description
```
Added value: +"Product id. Use it for get_plan_details and start_checkout."
```
addedOutput schema / properties / plans / items / properties / rating / description
```
Added value: +"Average customer rating (1-5). Present only when reviews exist."
```
addedOutput schema / properties / plans / items / properties / review_count / description
```
Added value: +"Number of reviews. Present only when > 0."
```

addedOutput schema / properties / plans / items / properties / sku

Added value: +{
+  "description": "Catalogue SKU.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / summary

Added value: +{
+  "description": "Short description in the requested language, from the product page.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / tethering / description

Added value: +"Hotspot / tethering is supported where the network and device allow it (shop rule)."

addedOutput schema / properties / plans / items / properties / title

Added value: +{
+  "description": "Full product title in the requested language.",
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / topup / additionalProperties
```
Added value: +true
```
addedOutput schema / properties / plans / items / properties / topup / description
```
Added value: +"Top-up possibility for this plan."
```

addedOutput schema / properties / plans / items / properties / topup / properties

Added value: +{
+  "how": {
+    "description": "How the customer tops up.",
+    "type": "string"
+  },
+  "kind": {
+    "description": "What TopUp can add without a new eSIM: data (Data Pack), days (Unlimited Flex), or none.",
+    "enum": [
+      "data",
+      "days",
+      "none"
+    ],
+    "type": "string"
+  }
+}

changedOutput schema / properties / plans / items / properties / topup / type
```
Previous value: -"boolean"New value: +"object"
```
addedOutput schema / properties / plans / items / properties / transparency / description
```
Added value: +"A per-order Transparency link shows remaining data in near real-time."
```
changedOutput schema / properties / plans / items / properties / type / description
```
Previous value: -"Data Pack or Unlimited Flex."New value: +"Plan type."
```
addedOutput schema / properties / plans / items / properties / type / enum
```
Added value: +[
+  "Data Pack",
+  "Unlimited Flex"
+]
```

addedOutput schema / properties / plans / items / properties / unused_valid_days

Added value: +{
+  "description": "Days the eSIM may remain unused after purchase before it expires (supplier value).",
+  "type": "integer"
+}

addedOutput schema / properties / plans / items / properties / url / description
```
Added value: +"Product page in pricing_bucket. Use verbatim."
```

changedOutput schema / properties / plans / items / properties / validity / description

Previous value: -"Data Pack: validity label."New value: +"Validity label, e.g. \"30 days\"."

addedOutput schema / properties / plans / items / properties / voice_sms

Added value: +{
+  "description": "Always \"none\": data only, no telephone number, no SMS.",
+  "type": "string"
+}

addedOutput schema / properties / pricing_bucket
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / returned
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / total_available

Added value: +{
+  "description": "Plans matched before limit; the rest are on all_plans_url.",
+  "type": "integer"
+}

Changedstart_checkout18 fields changed

addedInput schema / properties / bucket

Added value: +{
+  "description": "Optional language-region bucket the customer shops in, e.g. \"en-gb\", \"de-de\". Wins over language; prices and links are quoted in it.",
+  "type": "string"
+}

addedInput schema / properties / currency

Added value: +{
+  "description": "Optional ISO 4217 code. Every price in the result is quoted in it.",
+  "type": "string"
+}

addedInput schema / properties / days

Added value: +{
+  "description": "Unlimited Flex only: the duration the customer wants; the returned total_for_days is the checkout total for it.",
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / language / description

Previous value: -"ISO language of the conversation. Sets the language/currency of the payment page."New value: +"ISO language of the conversation, e.g. en, de, ja. Plan names and country names come back in it when available. Bare \"en\" is quoted in en-us / USD."

changedInput schema / properties / product_id / description

Previous value: -"WooCommerce product id to buy."New value: +"Product id to buy."

addedOutput schema / properties / app_links / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / app_links / description

Previous value: -"Optional links to the free IbiPoint app (android/ios). Mention only when present."New value: +"Optional store links of the free IbiPoint app (android, ios) - the eSIM works without it."

addedOutput schema / properties / days
```
Added value: +{
+  "type": "integer"
+}
```

removedOutput schema / properties / days_range / description

Removed value: -"Only on price_basis \"per_day\": choosable durations in days, e.g. \"1-365\"."

addedOutput schema / properties / presentation
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / price / description

Previous value: -"Price in currency, to be read WITH price_basis: the full fixed price when \"total\", the price of one day when \"per_day\"."New value: +"Read WITH price_basis."

changedOutput schema / properties / price_30_days / description

Previous value: -"Only on price_basis \"per_day\": price for 30 days, discount applied — the reference figure for a month."New value: +"Unlimited Flex: price for 30 days, discount applied."

removedOutput schema / properties / price_basis / description

Removed value: -"What `price` means for this product. See the plan schema."

addedOutput schema / properties / price_is_final
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / price_max / description

Removed value: -"Only on price_basis \"per_day\": price for the longest duration, discount applied."

addedOutput schema / properties / pricing_bucket
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / product_id
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / total_for_days

Added value: +{
+  "description": "Unlimited Flex: checkout total for the requested days, discount applied.",
+  "type": "number"
+}

3 tool updatesSep 22, 2026

Changedget_plan_details5 fields changed

addedOutput schema / properties / days_range

Added value: +{
+  "description": "Only on price_basis \"per_day\": the durations the customer can choose, in days, e.g. \"1-365\".",
+  "type": "string"
+}

changedOutput schema / properties / price / description

Previous value: -"Full fixed price in currency; not per-day or per-GB."New value: +"Price in currency, to be read WITH price_basis: the full fixed price of the plan when price_basis is \"total\", the price of one day when it is \"per_day\". Never a per-GB rate."

addedOutput schema / properties / price_30_days

Added value: +{
+  "description": "Only on price_basis \"per_day\": the price for 30 days with the duration discount applied — the reference figure to quote for a stay of about a month. Absent when it cannot be computed; never infer it by multiplying price.",
+  "type": "number"
+}

addedOutput schema / properties / price_basis

Added value: +{
+  "description": "What `price` means. \"total\" = the whole plan (Data Pack). \"per_day\" = one day (Unlimited Flex): the duration is chosen at checkout within days_range; see price_30_days and price_max.",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / price_max

Added value: +{
+  "description": "Only on price_basis \"per_day\": the price for the longest duration in days_range, discount applied. Absent when it cannot be computed; never infer it by multiplying price.",
+  "type": "number"
+}

Changedsearch_esim_plans5 fields changed

addedOutput schema / properties / plans / items / properties / days_range

Added value: +{
+  "description": "Only on price_basis \"per_day\": the durations the customer can choose, in days, e.g. \"1-365\".",
+  "type": "string"
+}

changedOutput schema / properties / plans / items / properties / price / description

Previous value: -"Full fixed price in currency; not per-day or per-GB."New value: +"Price in currency, to be read WITH price_basis: the full fixed price of the plan when price_basis is \"total\", the price of one day when it is \"per_day\". Never a per-GB rate."

addedOutput schema / properties / plans / items / properties / price_30_days

Added value: +{
+  "description": "Only on price_basis \"per_day\": the price for 30 days with the duration discount applied — the reference figure to quote for a stay of about a month. Absent when it cannot be computed; never infer it by multiplying price.",
+  "type": "number"
+}

addedOutput schema / properties / plans / items / properties / price_basis

Added value: +{
+  "description": "What `price` means. \"total\" = the whole plan (Data Pack). \"per_day\" = one day (Unlimited Flex): the duration is chosen at checkout within days_range; see price_30_days and price_max.",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / plans / items / properties / price_max

Added value: +{
+  "description": "Only on price_basis \"per_day\": the price for the longest duration in days_range, discount applied. Absent when it cannot be computed; never infer it by multiplying price.",
+  "type": "number"
+}

Changedstart_checkout5 fields changed

addedOutput schema / properties / days_range

Added value: +{
+  "description": "Only on price_basis \"per_day\": choosable durations in days, e.g. \"1-365\".",
+  "type": "string"
+}

changedOutput schema / properties / price / description

Previous value: -"Full fixed price in currency; not per-day."New value: +"Price in currency, to be read WITH price_basis: the full fixed price when \"total\", the price of one day when \"per_day\"."

addedOutput schema / properties / price_30_days

Added value: +{
+  "description": "Only on price_basis \"per_day\": price for 30 days, discount applied — the reference figure for a month.",
+  "type": "number"
+}

addedOutput schema / properties / price_basis

Added value: +{
+  "description": "What `price` means for this product. See the plan schema.",
+  "enum": [
+    "total",
+    "per_day"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / price_max

Added value: +{
+  "description": "Only on price_basis \"per_day\": price for the longest duration, discount applied.",
+  "type": "number"
+}

3 tool updatesSep 13, 2026
- First observedget_plan_details
- First observedsearch_esim_plans
- First observedstart_checkout

Related MCP Connectors

e-eSIM Catalog A
com.e-esim
Search travel eSIM data plans worldwide with live prices, plan details and a buy link.
Travel & Transportation E-commerce & Retail
51
Roam2Go eSIM Catalog A
com.roam2go
Search travel eSIM data plans for 230+ destinations with live prices and purchase links.
Travel & Transportation E-commerce & Retail Search
31
eSIM-Global.VIP eSIM Catalog A
vip.esim-global
Find prepaid travel eSIM plans for 200+ destinations with live prices, specs and a buy link.
E-commerce & Retail Travel & Transportation
51
eSIM Finder AOAuth
io.esimfinder
Search, compare & buy prepaid travel eSIM data plans for 190+ countries in 40 currencies, including regional plans and a 12-month Travel Pass.
E-commerce & Retail Search Travel & Transportation
52

Related MCP Servers

PikaSim
Travel & Transportation E-commerce & Retail Cryptocurrency
codebruinc
A
license
Not graded
quality
C
maintenance
Browse, compare, and purchase eSIMs for 190+ countries via AI agents. 12 tools for searching 2,300+ data plans, checking coverage, and buying eSIMs with crypto or card. No account required for browsing.
Updated 16 days ago (2026-10-07 02:32 UTC)
MIT
esimoaofficial
E-commerce & Retail
nbase-io
A
license
Not graded
quality
C
maintenance
Enables AI assistants to search and compare travel eSIM data plans by destination, trip length, data amount, unlimited/daily type, local phone number, local or roaming network, multi-country coverage, budget, hotspot and 5G, returning plan details plus a link to buy. Read-only with no sign-in or API key required.
Updated 21 days ago (2026-10-02 15:24 UTC)
1
MIT
SinoConnection eSIM
Travel & Transportation E-commerce & Retail
SkyUnlimit
A
license
Not graded
quality
D
maintenance
Search and buy travel eSIMs for 200+ countries, with specialized China plans that deliver uncensored internet without a VPN. Exposes five read-only tools to search plans, check device eSIM compatibility, get plan details, get help, and generate a secure on-site checkout link.
Updated 3 months ago (2026-07-16 16:52 UTC)
MIT
mcp-esim
Travel & Transportation E-commerce & Retail Payments & Billing
isabellaliebgott
A
license
A
quality
D
maintenance
Travel eSIMs for 193 countries. Stripe + Bitcoin checkout. QR by email in 30s. No API key.
Updated 5 months ago (2026-06-07 12:48 UTC)
4
22 npm
MIT