Comparisons
How InBe is different from other platforms and services you may have used.
Overview
When building with location data, you've probably used or considered the Google Places API. It's powerful and the industry standard for a reason. However, it was designed for an earlier era. While Google Maps has user-facing features people love, many of those flows aren’t available via their Places API, and stitching them together takes multiple APIs, many calls, and lots of custom logic.
We built InBe to address the gaps we found while building modern applications. Here's a direct comparison of key features.
Feature comparison: InBe vs. Google Places API
Feature | InBe | Google Places API |
---|---|---|
Multi-point search | Yes | No |
Group features | Yes | No |
Dietary needs | Advanced | Basic |
Deep preference filtering | Yes | No |
Rich data in one call | Yes | No |
Custom location weighting | Yes | No |
Additional calls for images | No | Yes |
Menus | Yes | No |
Events | Yes | No |
Bookings | Yes | No |
Results per search | 20 | 20 |
Good-for contexts (dates, groups, business, etc.) | Advanced | Basic |
Place highlights (reasons to go) | Yes | No |
Note: Google provides excellent global maps, navigation, and base place data. InBe focuses on intelligent matching, multi-user context, and deeply structured venue data for product flows.
The InBe difference: a practical example
Let's look at a common product requirement:
As a user, I want to invite a friend to dinner. The app should suggest restaurants halfway between us that are good for conversation and offer vegan options.
With the Google Places API, you would typically:
- Geocode both user addresses (2 API calls).
- Calculate the geographical midpoint yourself.
- Perform a "nearby search" around that midpoint (1 API call).
- Iterate through the results, making a "place details" call for each one to check for "vegan" in reviews (N API calls).
- Manually filter out places that aren't "good for conversation."
- Finally, present the list to the user.
With InBe, you make one API call:
At a glance
Google Places flow: typical calls
- Geocode user addresses: 2
- Nearby search at midpoint: 1
- Place details for filtering: N
Total: 4–20+ calls per user session
InBe flow: typical calls
- Match and filter with preferences: 1
- Detail request only when user selects a place: 1
Total: 2+ calls per user or group session
On average, we are roughly 1/3 the cost of Google Places API.
When to use both
Google provides excellent global maps, navigation, and broad POI coverage. Many teams pair that with InBe for intelligent matching, multi-user context, and deeply structured venue data. Use your preferred maps SDK for visualization, and call InBe to power the decision flow (find, weigh, and return the best options in one response).
Request pricing
We give all new customers £10 credit, giving you over 1600 requests to get started.
Request type | Price per 1000 |
---|---|
Search | £6 |
Detail Basic | £8 |
Detail Advanced | £12 |
Venue Menus | £6 |