For providers

Provider terms

These are the terms you accept by listing an eSIM catalog on eSIMradar, by calling our provider API, or by connecting to our MCP server. They apply to all three the same way — the MCP server is a different door into the same API, not a separate product with separate rules.

The short version: listing is free and automatic, and it is not a right. We decide what appears on this site and we can remove a provider, a plan, or a whole catalog whenever we judge that it should not be there. Paying us does not change that, because an affiliation buys a disclosed marker and nothing else. Send us accurate plans, do not pad your catalog, and do not abuse the API — and none of the rest of this page will ever concern you.

Who these terms cover

Anyone who registers a provider account, submits a catalog over the REST API or the MCP server, registers a feed for us to pull, or is listed on this site as an eSIM provider. You accept them by doing any of those things. If you are integrating on behalf of a provider, you are agreeing on their behalf and you need their authority to do so.

There is no guarantee of being listed

Self-onboarding is automated, so in practice a valid catalog goes live without anyone at eSIMradar looking at it. That is a convenience, not an entitlement. This site is an editorial product and we retain full discretion over what appears on it.

Where a removal is something you can fix — a validation failure, a dead purchase URL, an inaccurate price — we will say what it was, because a provider who can correct the problem is more use to our readers than one who is gone. Where it is a judgement about whether your catalog belongs here, the decision is ours and it is final.

Your catalog has to be true

Everything you send is shown to travellers as fact and compared against every other provider on the same arithmetic. Inaccurate data does not just mislead a reader; it moves other providers down a ranking they earned. This is the obligation we take most seriously.

No spam listings

A comparison site is only useful if the list is a list of genuinely different options. Filling it with variations of the same product to occupy more rows is the fastest way to make it useless, so we treat it as a serious breach rather than a technicality.

We may remove individual plans, cap how many of your plans appear on a page, or remove your catalog entirely. Which of those we choose is our decision, and we are not obliged to warn you first.

Fair use of the API and the MCP server

The provider API and the MCP server exist so you can publish your own catalog without talking to anyone. Both are covered by the same rules, because they are the same surface reached two ways.

What happens automatically

Most enforcement here is code, not judgement, and it runs on every submission. None of it is a penalty — it exists so a bad response from your side does not become bad data on ours.

Ranking is computed, and it is not for sale

Plans are ordered by price per gigabyte, calculated from the price and allowance you submit. The ordering is computed before we know who has a commercial relationship with us, and no payment, affiliation or partnership changes it.

An affiliation changes which plans we put forward, and we disclose each place on the site itself: eligibility for the gradient "top pick" marker, the "Our picks" shelf above a board, appearance in the featured partners rail, which is labelled as a paid placement wherever it appears, and the "Recommended" tab of a destination or region board. A provider with no relationship with us is listed, ranked, linked and compared identically, and its plans appear in full under the board's other three sorts.

Your data, and what we do with it

You keep ownership of everything you send. We need permission to show it, and you need the right to send it.

We do not promise the API will be up

The provider API and the MCP server are provided as they are, with no guarantee of availability, performance or backwards compatibility beyond what we publish. We may change, deprecate or withdraw endpoints and tools. Where a change would break a working integration we will try to give notice and a migration path, but building anything that depends on our uptime is at your own risk.

Suspension, removal, and leaving

Either side can end this. Neither side owes the other a notice period.

Changes to these terms

We will update this page as the API and the site change. Continuing to submit catalogs or keep a listing after a change means you accept the current version. Where a change materially affects what you are allowed to do, we will say so on this page rather than quietly editing a sentence.

Something here that does not fit how you work?

Tell us before you build around it. Most of these rules exist because of a specific way the data can go wrong, and if your catalog breaks one of them for a good reason we would rather know than remove you for it.