Questions about iplyt

iplyt is an IP geolocation API. Send an IP address and receive structured location, ASN, network, and organization data.

Developers and product teams who need reliable GeoIP data for fraud prevention, localization, analytics, compliance logging, or access control — without running their own geolocation infrastructure.

The homepage lookup preview uses an internal server-side proxy to show sample results. Production integrations use the platform API at /api/v1/lookup with your API key from the dashboard.

Yes. New accounts receive a trial period with a monthly lookup quota. A credit card is only required when you choose a paid plan or your installation explicitly requires one at signup.

Select a plan in the billing portal. Without an active subscription, API access may be restricted — your account data remains until you export or delete it.

After registration, open API keys in the dashboard, create a key, and copy it immediately. Keys are shown only once.

Subscriptions run through Stripe. Monthly and annual billing are supported; annual plans receive up to 20% off. Lookup quotas reset each billing period.

Each successful single-IP request counts as one lookup. A POST with multiple IPs counts one lookup per IP in the batch (up to 100 per request). Failed requests due to client errors may not count — see your plan details.

Yes — upgrade or downgrade through the billing portal. Stripe proration rules apply to mid-cycle changes.

For high volume, custom domains, SLA, or dedicated support, contact us for an enterprise offer with tailored limits.

A Service Level Agreement defines response times and availability targets for support and infrastructure. Standard plans include email support without guaranteed response times; Enterprise can include a formal SLA.

Stripe Checkout supports common card payments and local methods depending on your region. Invoices and bank transfer may be available on enterprise plans.

POST /api/v1/lookup accepts up to 100 IPs per request. Request bodies are limited to 10 MB. Bulk lookup page_size ranges from 1 to 1000 (default 50).

Successful lookups can include location (city, country, coordinates, timezone), ASN, network flags (e.g. hosting), organization details, and optional extended geo reference data on Enterprise.

Yes. The lookup engine caches responses in memory with a configurable TTL (default one hour). Repeated queries for the same IP return cached results until expiry.

Yes. Both IPv4 and IPv6 addresses are accepted on all lookup endpoints.

iplyt maintains regularly updated geolocation datasets. Enterprise plans can include extended city, state, and country reference fields when available for a match.

Lookup IPs are processed to return results and may appear in aggregated usage metrics. We do not sell lookup data. See our Privacy Policy for retention details.

You are responsible for lawful basis when processing personal data derived from IPs. iplyt provides tools for logging and access control; configure retention and DPA as required for your use case.

Open a ticket under SaaS Support in the dashboard. Include request IDs, example IPs (if safe to share), and timestamps for faster resolution.

Yes — see the Docs section for quickstart, authentication, lookup endpoints, bulk API, and error codes.