This FAQ is grounded in the same economic context and gravity logic used by the API, with practical guidance for product, AI, and operations teams.
Bwendi returns verified context, not just a geocode label. You get administrative hierarchy, nearest place anchors, and gravity-ranked market context so systems can understand what a location means commercially.
Population is often a weak proxy for real market activity. Bwendi models economic pull using throughput, dwell, criticality, transactional behavior, and visit rhythm, then applies distance decay to resolve true catchment gravity.
It is a compact score describing how strongly a place attracts human and commercial activity. Think of it as a practical map of market pull that your product can consume in real time.
Yes. Responses are designed to be prompt-ready and machine-consumable, helping agents reason about location context without guessing from raw latitude/longitude alone.
Core lookups use standard credits, auto-resolve and enrichment consume additional credit tiers, and premium AI interpretation uses higher-cost premium credits. The Pricing page details each capability tier.
No. Bwendi operates as a read-only context oracle with zero-state privacy principles, designed for sensitive production usage where minimizing retained location data matters.
Bwendi covers 249 countries and territories and is designed to perform in mature and informal market structures, where traditional assumptions often break.
Validate your top geographies with sample coordinates, map the right credit tier to each feature, and confirm your fallback strategy for rate limits and retries.
Open a direct support conversation for integration questions, model interpretation, or rollout planning.
Use the documentation for implementation detail, the contact page for rollout questions, and this FAQ for the product behavior most teams ask about first.