Can I pay in rubles or by bank transfer?

Today the only implemented payment method is the Telegram bot via Telegram Stars — no ruble price is charged and no automatic invoicing exists yet. A bank-transfer arrangement for a legal entity isn't an automated feature; it's discussed individually — message us on Telegram and we'll work out the details.

Do you support migrating from MaxMind, IPinfo or ip-api.com?

Yes, at the level of a documented JSON schema — the current response format is in the API docs, and migration is a common reason companies evaluate this service. A dedicated field-by-field mapping guide is planned but not published yet; until it ships, get in touch and we can help map specific fields.

Is pricing metered per request or per IP address?

Per unique IP address per day, not per request. Looking the same address up many times in one day only counts once against that feature group's daily budget — a real advantage over a flat per-call price for repeat business traffic.

What does your geolocation data's source licensing look like?

Every geo response names its winning source in geo.source. An authenticated request on a verbose-enabled plan additionally returns that source's license and reference URL in geo.license/geo.url, so you can record proper attribution for your own compliance needs.

Do you offer an SLA, a dedicated support contract, or a signed DPA?

No — none of those exist today. Support runs through the Telegram bot linked in the footer, and there is no formal SLA, support contract, or data-processing agreement in place yet. If your business needs one, tell us, but we won't claim it before it exists.

An IP Data API Built for Business — Transparent Pricing, Live Registry Data

A predictable, per-unique-IP-metered IP data API for companies evaluating a move from another provider: RDAP registry data fetched from the registry and cached, geolocation with source licensing, and threat intelligence plus an explainable fraud score built in, not sold as an add-on.

Evaluating a MaxMind alternative or an IPinfo equivalent for a Russian or CIS business? This service's tier catalog is transparent and live — every plan's limits below come straight from the same /api/v1/tiers catalog the pricing page uses, repeat lookups of the same address within a day cost nothing extra thanks to per-unique-IP-per-day metering, and the registry data itself is queried from the registry's own RDAP service per address on demand, cached briefly, rather than served from a static snapshot database refreshed on someone else's release schedule.

This page is the business buying case — for integration details and code samples see the developer API page, and for a deep dive into fraud and risk signals see the fraud detection page.

Why businesses evaluate IP lookUp

Every point below is a real, verified property of the current API — not a roadmap promise.

Per-unique-IP-per-day metering — repeat lookups of the same address inside the same day cost nothing extra; the meter counts distinct IP addresses, not requests, a real cost advantage over a flat per-call price for high-repeat business traffic.
Live RDAP-sourced registry data — the network.rdap record is queried from the registry's own RDAP service per address on demand and cached briefly, not served from a periodically imported bulk snapshot database; geo readings instead come from multiple sources kept current by scheduled import jobs, with every response naming exactly which source won (see provenance below).
Source provenance and licensing — every geo response names its winning data source (geo.source); an authenticated request on a verbose-enabled plan additionally returns that source's license and reference URL (geo.license/geo.url) for your own attribution records.
Threat intelligence and fraud scoring included — threat.isMalicious draws on ten reputation feeds and fraud.score is a transparent, deterministic in-house rollup over this service's own signals; both are part of the base product, not a separately priced add-on.
No signup required to evaluate — a basic lookup works with no account, so a technical evaluation can start well before any commercial conversation.

Current plans and limits

Fetched live from the same catalog the pricing page uses — nothing below is hardcoded, so it never drifts out of date.

Loading current plans…

* Per-minute and per-day limits are counted per unique IP address looked up. An overall request-rate ceiling also applies at the gateway, independent of the per-minute/per-day limits above, returning HTTP 429 once exceeded.

Plans and top-ups are purchased through the Telegram bot using Telegram Stars — see the pricing page for current prices.

Need a bank transfer for a legal entity? That isn't an automated feature today — message us on Telegram and we'll discuss it individually.

Migrating from another IP data provider

Many companies evaluating this API are migrating an existing integration built on MaxMind GeoIP2, IPinfo, ip-api.com or a similar provider. A field-by-field migration guide with mapped response shapes is planned but not published yet — the current JSON response schema is documented in full in the API docs' data reference, which is the best starting point for mapping your existing fields today.

Want help mapping a specific integration ahead of the guide's release? Get in touch on Telegram.

Ready to evaluate it for your business?

Read the full API docs See plans & get an API token Contact us on Telegram

Frequently asked questions

Can I pay in rubles or by bank transfer?: Today the only implemented payment method is the Telegram bot via Telegram Stars — no ruble price is charged and no automatic invoicing exists yet. A bank-transfer arrangement for a legal entity isn't an automated feature; it's discussed individually — message us on Telegram and we'll work out the details.
Do you support migrating from MaxMind, IPinfo or ip-api.com?: Yes, at the level of a documented JSON schema — the current response format is in the API docs, and migration is a common reason companies evaluate this service. A dedicated field-by-field mapping guide is planned but not published yet; until it ships, get in touch and we can help map specific fields.
Is pricing metered per request or per IP address?: Per unique IP address per day, not per request. Looking the same address up many times in one day only counts once against that feature group's daily budget — a real advantage over a flat per-call price for repeat business traffic.
What does your geolocation data's source licensing look like?: Every geo response names its winning source in geo.source. An authenticated request on a verbose-enabled plan additionally returns that source's license and reference URL in geo.license/geo.url, so you can record proper attribution for your own compliance needs.
Do you offer an SLA, a dedicated support contract, or a signed DPA?: No — none of those exist today. Support runs through the Telegram bot linked in the footer, and there is no formal SLA, support contract, or data-processing agreement in place yet. If your business needs one, tell us, but we won't claim it before it exists.