Mogean and Foursquare's Places API: how each is priced
This page covers one Foursquare product, the Places API, using the statements on Foursquare's public pricing page, quoted below. Mogean sells files: each dataset has one published price and the file is delivered at checkout.
It compares how each is bought, not what is in the data, and it makes no claim that either company's data is more accurate or more complete than the other's. Every statement about Foursquare below is quoted from its own public pricing page, dated, and linked to it.
Side by side: how each is priced
| Mogean | Foursquare (Places API) | |
|---|---|---|
| How the price is set | Published prices: brand datasets $19–$79 one-time, category bundles $199–$1,999 one-time, single-state datasets $19–$662 a year, the full US master $14,900 a year. Custom datasets are priced by a published formula: max($29, rows × tier rate) × license multiplier, then max(floor_usd, sum(rows_in_tier * tier_rate) * license_multiplier). Whole-brand, whole-category, and whole-source custom requests are capped at the cheapest published product covering them; filtered selections (states, data sources, columns) are formula-priced and may exceed a broader published product's price.. |
|
| Published rates | One price per dataset, listed on the pricing page and charged as listed at checkout. |
|
| Trying it first | Free sample rows on the dataset pages, no sign-up. |
|
Which way of buying fits
Usage-based pricing fits when you look places up through an API from inside an application and what you pay should follow how much you use it.
A file fits when you want every location for a brand, a category or a state on your own storage, for analysis or to load into your own tool, at a price set by what is in the file. A one-time purchase is a single file, yours to keep; an updates subscription delivers a refreshed file with each release.
The whole ladder, the custom-dataset formula and the license tiers are on the pricing page. How the data is built and checked is on the methodology page, and the schema and loading guides are in the docs.
FAQ
Foursquare's pricing page says “Flexible, volume-based pricing based on your monthly usage of Pro & Premium endpoints with the Foursquare Places API.” (As of October 2026, per Foursquare's public pricing page). For the Pro endpoints its rate table lists “0 – 500 Calls” “$0.00 CPM”; “501 to 100,000 Calls” “$15.00 CPM”; “100,001 to 500,000 Calls” “$12.00 CPM”; “500,001+ Calls” “$9.00 CPM” (As of October 2026, per Foursquare's public pricing page).
Not directly. Foursquare's page prices usage by monthly calls; Mogean prices a file by what it contains. To compare for your case, estimate your yearly lookups, read that tier's rate on As of October 2026, per Foursquare's public pricing page, and set the result against the dataset price on the pricing page. This page does not convert one into the other, because the two do not measure the same thing.
With Mogean: Free sample rows on the dataset pages, no sign-up. Foursquare's pricing page says “Test out Places API for free in our sandbox and then pay-as-you-go. Enjoy up to 10,000 free calls on Pro endpoints.” (As of October 2026, per Foursquare's public pricing page). It also lists “$0/month through 2026” (As of October 2026, per Foursquare's public pricing page) for the Basic plan of Spatial Desktop, a different product from the Places API.
Mogean's methodology lists Foursquare Open Source Places, licensed under Apache License 2.0, as one of the open-data sources that fills category and geographic coverage. Each row carries a provenance tier that says whether it came from there, from a brand's own store locator, from a government registry, or from Overture Maps.