Everyday places and real minutes for every address. Paid once, stored forever.

Everything in one API

Places, minutes, addresses and climate. One key, one bill.

Most teams buy this from three vendors and glue it together. Here it comes from one API, with one data version behind every answer.

Read the API documentation

What you can build

Four places where the same answer earns its keep.

How it runs

Live in four steps. After that, the keeping is ours.

1. 01

   Create an account

   The Free plan starts at once. Create your key in the console and make your first call in minutes.

2. 02

   Send addresses

   Send an address and we find it, or send coordinates. One at a time from your product, or a whole list as a bulk job.

3. 03

   Store the answers

   Write every response into your own database and serve it from there. The answers are yours to keep.

4. 04

   Refresh on release

   On each new data release your saved addresses are recomputed. You read the new answers; nothing to rebuild.

For your engineers

Three ways in.

curl https://nilq.com/api/v1/places/analyze \
  -H "Authorization: Bearer $NILQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"country_code": "PT",
       "location": {"latitude": 38.7101,
                    "longitude": -9.1374},
       "radius_meters": 800,
       "category_ids": ["foursquare:4bf58dd8d48988d1e0931735"],
       "metrics": ["count", "travel_time_nearest"],
       "mode": "walk"}'

POST /api/v1/jobs
Idempotency-Key: catalogue-2026-10

{"operation": "place_analysis",
 "records": [ ... ],
 "analysis": { ... }}

202 Accepted
GET /api/v1/jobs/{id}/results

claude mcp add --transport http nilq \
  https://nilq.com/api/v1/mcp \
  --header "Authorization: Bearer $NILQ_API_KEY"

Keep it

Pay once per address. Keep the answer.

Storage rights

Store every response in your own database, ship it in your product and keep it after the contract ends. One condition travels with the data: every stored fact keeps its source line.

Answers you can explain

Every answer names its sources and data version. When a client asks why you said eight minutes, you open the record and show where it came from.

Refresh without rework

New data releases recompute your saved addresses. A refresh that fails keeps the last good answer and says so, so a page never shows a blank.

Coverage

Europe, market by market. Then further.

A market goes live when its places, routes and addresses pass the same checks as the ones below. Tell us which market you need; it shapes the order.

How NILQ compares

Priced on what you keep, not on what your visitors click.

Per address, not per call

Per-call pricing grows with your traffic. NILQ is priced on the addresses you keep, a number finance already knows, so a good month for marketing is not a bad month for the invoice.

Storage rights, not caching rules

Many location licences limit what you may store. Ours lets you keep every answer in your own database.

One call, not two vendors

Places from one vendor and travel time from another means two contracts, two renewals and two data versions. NILQ returns both in one response.

Maintained, not homemade

The sources are open and a sprint gets you a prototype. NILQ runs the routing, the matching and every data release for you, year after year.

Pricing

Priced on addresses you keep.

From Starter up there is no monthly lookup ceiling, and every answer is yours to store. Prices exclude VAT.

A saved address is one active saved location per customer reference; updating it does not use another slot. More than 500,000 addresses, more markets, your own deployment or different terms: from €1,990 a month, quoted against your scope at api@nilq.com. Use is governed by the Terms.

Scope

What the API answers, and what it leaves to others.

NILQ answers what surrounds an address and how long daily life takes from its door. Data about the property itself or about people stays with the specialists you may already use.

• Public transport times
• Live traffic
• Demographics
• Footfall
• Valuations
• Ownership records