Skip to content
InternetData

API or database

When to call the InternetData API and when to download its databases: freshness, latency, volume, what each answers and what each costs.

Both carry the same data. They differ in where the lookup runs.

APIDatabases
Where it runsOur servers, one request per lookupYours, in memory
LatencyA few tens of milliseconds, plus the networkMicroseconds
FreshnessOur current dataAs of your last download; most rebuild daily
What it answersEvery field your plan includes, in one answerOne dataset per file, joined by you
PricingA plan's monthly lookupsA license per database
Best forSign-ups, logins, checkouts and other single decisionsLogs, analytics, firewalls and very high volume

Most integrations start with the API and move a high-volume path to a database later. The SDKs and the databases each have a quickstart.