Intelligence from today’s data
Verified ground-level data on whatever you need counted, wherever you work — and answers in plain language.
Organisations that have to be right about a place
Ministries, utilities, operators, lenders and programmes — wherever the next decision depends on what is actually on the ground.
- Example Waterworks
- Demo Transit Authority
- Sample Grid Operator
- Placeholder Telecom
- Demo Development Trust
- Example Logistics
- Sample Agri Board
- Placeholder Retail
Placeholder names, shown while the partner list and marks are being confirmed.
Start with your own questionWhat is LOCI?
Data is only useful when you can see what it means. LOCI turns verified ground-level data into location intelligence.
- Field survey teamsCollected on the ground
- Licensed datasetsSurveyed by others
- Uploaded recordsBrought in as files
- Repeat visitsThe same place, again
Shows the patterns
Where things cluster, and where they are absent.
Tracks the changes
What is different since the last survey.
Helps you plan ahead
Where the next one goes, before it is built.
Two ways in.
An answer is worth nothing where the decision is not being made. Build against the API, or let us shape LOCI to the pipeline you already run.
Call the API
A read-only REST API behind a bearer token. One endpoint takes a question in plain language; another takes a latitude and longitude and returns what is recorded at that point.
POST /v1/askAuthorization: Bearer loci_sk_…Content-Type: application/json{ "question": "Which ward has the highest estimated population?"}HTTP/1.1 200 OKX-RateLimit-Limit: 30X-RateLimit-Remaining: 28{ "data": { "intent": "ranking", "headline": "<one sentence, with the figure>", "facets": [ … ], "table": { "columns": [ … ], "rows": [ … ] }, "sources": [ { "layerId": …, "attribute": … } ], "confidence": "exact", "engine": "deterministic"} }
The request is the reference’s own example. Field names and enumerated values are real; the figures are elided, because what comes back depends entirely on what you have licensed.
- Credential
- A read-only bearer token, prefixed
loci_sk_. There is no write capability a key can hold. - Scope
- Pinned when the key is minted: one project, or everything your organisation can read.
- Out of scope
- Addressing something a key may not read is
404, never403— a refusal that confirmed the thing existed would leak it. - Metering
- Documented token buckets, with
X-RateLimit-Remainingon every metered response — on success as well as on refusal, so a client can slow down before it is turned away.
"engine": "deterministic"
No model in the loop. The figures are an aggregation, and sources names the layer and attribute they came from, so any answer can be checked against the data.
"confidence": "exact" | "partial" | "unknown"
How much of the question actually matched. An unmatched question says so rather than returning a confident sentence about the wrong attribute.
The point lookup is GET /v1/layers/{layerID}/locality — pass a coordinate and it answers with the administrative hierarchy it falls in, the attributes recorded there, and a one-line summary.
Or have one built for you
Not every system speaks HTTP and JSON, and not every pipeline should be rebuilt around one that does. We build the adapter that delivers LOCI into the tools your teams already have open.
What that adapter is depends entirely on what you run, which is why it starts as a conversation with the engineers who would build it rather than as a sign-up form.
Start with the question you cannot answer today
LOCI is where ground truth gets collected, licensed and turned into decisions — about whatever you need counted, wherever you work.