BwendiLocation Intelligence

Local Context API

Drop a coordinate. Get the economic truth.

Hub, anchors, metro, economic tier, admin hierarchy, and a context string — for any point on Earth. One authenticated call. Under 80ms.

Get API Key — free API Documentation Pricing

Hub Resolution

The primary commercial centre governing this coordinate — economic tier, distance, cardinal bearing, and place type in a single resolved object.

Anchor Layer

Typed nearby places at three reach bands — immediate (on-foot), local (bike/moto), and reachable (vehicle) — so your logic knows exactly what surrounds every point.

Economic Tier

A single classification — isolated, marginal, integrated, or regional — that places every coordinate on the economic activity spectrum instantly.

Admin Hierarchy

Full nested administrative chain — region, department, district — each typed, labelled, and depth-levelled for rules-engine and routing integration.

Metro Anchor

The dominant city or town the coordinate is economically tied to — with distance and bearing — giving you a human-readable "city" for any point on Earth.

Context String

A verified, pre-formatted location narrative generated in the local language — drop-in ready for any AI prompt, retrieval pipeline, or agent context window.

How It Works

Three steps from coordinate to context.

The Context API takes a country code, latitude, and longitude. It runs a parallel gravity-model resolution and returns a structured JSON object your product or agent can consume immediately.

Send a country code, lat, and lng

Pass the ISO 2-letter country code, latitude, and longitude. Optionally add ?lang= for a translated response or ?expand=true for enriched anchors.

We resolve the full economic context

The engine runs the gravity model, queries the LMDB zone index, resolves the admin chain, and scores the commercial tier — all in parallel, in under 80ms.

Get a structured context object

You receive a single JSON object with hub, hub_stack, anchors, tier, metro, within, country, and context fields — everything your product or agent needs.

Response Fields

One coordinate. Eight layers of economic truth.

Every field is production-typed, language-aware, and ready to wire into your rules engine, AI pipeline, or frontend — without further transformation.

hub

The primary commercial centre governing this coordinate. Includes name, type, economic tier, distance in km, and cardinal bearing.

hub_stack

Priority-ranked array of every nearby market hub — each with tier, distance, and direction. Powers hub-switching and market-stack logic.

anchors

Three reach bands — immediate, local, reachable — each containing typed commercial and infrastructure anchors closest to the coordinate.

tier

Single economic tier string: isolated | marginal | integrated | regional. Maps directly to commercial activity capacity.

metro

The dominant economic metro the coordinate orbits — with name, distance, and bearing. The human-readable "city" for any address.

within

Nested admin hierarchy from immediate container (quarter, neighbourhood) up through district, department, and region — each typed and language-aware.

country

Complete country object — ISO2, name, currency code, symbol, local currency name, calling code, national flag emoji, and principal language.

context

A verified narrative in the local language of the resolved place — drop-in ready for KYC workflows, logistics systems, and AI prompt pipelines.

Built For

What teams ship with Local Context

AI Agent Grounding

Feed the context string directly into an LLM prompt as a structured location fact. No hallucinated place names — grounded, current, verifiable.

Delivery & Logistics

Snap every delivery to the market hub that actually governs it. Use the context string on waybills and receipts in the local language.

Fintech KYC

Capture a customer location as a structured context object at onboarding. The admin hierarchy fulfils address-of-record requirements without a postal system.

Market Segmentation

Segment users by the commercial hub that governs their location — not by a static city list. Tier and metro give you real economic stratification.

Insurance & Risk Pricing

Use economic tier and metro distance to price location-based risk — urban vs. rural classification and commercial access from a single call.

Contextual Advertising

Layer the resolved hub and anchor data onto ad targeting to activate campaigns only where commercial activity supports conversion.

Field Operations

Surveyors, health workers, and agricultural teams tap once — get a structured context object that writes directly to forms and databases.

E-commerce Checkout

Replace free-text address fields with a hub-resolved context string for customers in markets with no formal postal codes. Reduce failed deliveries.

Live Demo

Try it — API key required

Enter a country code and coordinates. The call goes to api.bwendi.com/context in real time. Sign in to use your free API key — the browser session is passed automatically.

LatitudeLongitude

Sample response — Yaoundé, Cameroon

{
  "hub": {
    "name": "Yaoundé",
    "type": "regional_capital",
    "tier": "regional",
    "distance": 2.4,
    "bearing": "NW"
  },
  "tier": "regional",
  "metro": { "name": "Yaoundé", "distance": 0 },
  "within": [
    { "type": "district",   "name": "Ekounou" },
    { "type": "department", "name": "Mfoundi"  },
    { "type": "region",     "name": "Centre"  }
  ],
  "country": { "name": "Cameroon", "iso2": "CM",
               "currency": "XAF", "flag": "🇨🇲" },
  "context": "Ekounou, Yaoundé, Région Centre, Cameroun.",
  "credits": 1
}

Don't have a key yet? Get one free →

Start Building

A coordinate is all you need.

1 credit. One call. Hub, anchors, tier, metro, admin hierarchy, and a context string. Anywhere on Earth.

Get API key — it's free API Documentation See All Use Cases