Points-of-Interest ranking,
tuned to your customer.
One REST call returns the best places near a point. You control how "best" is defined: weight the tiers, boost the categories your users care about, set how fast score drops with distance. A family-travel app and a nightlife app hit the same endpoint and get different answers.
Top 5 in Paris
- No results.
cURL
Updates as you change inputscurl 'https://api.poiscore.com/v1/pois/nearby?lat=48.8584&lng=2.2945&radius_m=8000&limit=5&tier_s=5&tier_a=3&tier_b=1.5&tier_c=0.8&base_offset=0.5&w_fame=0.3&w_quality=0.2&tau_m=6000' \ -H 'Authorization: Bearer sk_live_...'
These are live calls to /v1/pois/nearby. Switch the profile and the list re-ranks in front of you.
Why teams pick it
Scoring you control
Pass weights and boosts on the request, or save them to a profile and attach it to an API key. Query near the Eiffel Tower and it comes back #1 by default; tell the API you're a family app and the museums move up.
No per-call data fees
The data comes from OpenStreetMap, Wikidata and Wikipedia, so there's no usage-based licence tax like Google Places. You pay a flat monthly price and you're free to cache and store what you get back.
Ranked by fame, not star ratings
A place's score comes from how many languages its Wikipedia article exists in and how often people read it — a fame_score that's the same for everyone. Nothing to fake, no reviews to moderate.
Fast enough to call on every keystroke
Radius queries run on a PostGIS spatial index across 600k+ places in 100 cities. Repeat lookups come straight from a Redis cache.
Keys built for production
sk_live_* bearer tokens, hashed at rest with scrypt. Each key has its own daily limit, usage log and optional domain allow-list, so a leaked browser key can't be used from anywhere else.
Runs in the EU
Hosting, email and payments all sit in the EU. Under the hood it's just Postgres and Redis, so if you need it on your own servers, that's on the table for enterprise plans.