Discovery is social. Keep it that way.

InBetween gives community and social platforms the venue data and group matching to turn shared inspiration into real plans, without pushing members out to a map.

Get Started

Discovering

London · Covent Garden

Group of 4
Outdoor seating
Buzzing
Walkable
api.inbe.us/v1/search
POST
{
"locations": [{ "locationName": "Covent Garden, London" }]
"mode": { "mode": "POINT", "maxDistance": 400 }
"preferences": { "goodFor": ["groups", "outdoor seating"], "establishmentFilters": ["goodForGroups", "outdoorSeating"] }
}
5 spots the group can agree on
Native to your social graph

For social networks, community apps, and local discovery platforms

From 'we should go' to 'we are going'.

Communities generate intent constantly: someone shares a place, a thread agrees to meet, a group forms around a plan. Then the practical part arrives and everyone scatters to maps and search engines to work out whether it can actually happen.

That scattering is where plans, and engagement, quietly die. The decision needed venue detail and group logic; the platform had neither.

InBetween supplies both. Rich venue profiles and multi-person matching let your platform carry a plan from suggestion to decision without anyone leaving.

What breaks today

  • Members deep-link out to maps at the decisive moment.
  • Plans stall without tools to reconcile the group's constraints.
  • The social context is lost the moment planning leaves the platform.

What you can ship

  • Plans made start to finish inside your platform.
  • More shared inspiration converting into real-world meetups.
  • Retention built on things that happened, not just things that were scrolled.

How it works for you

  1. 01

    Enrich posts and threads with venue data

    Recommendations, event posts, and group chats draw on structured venue profiles.

  2. 02

    Resolve the group's constraints

    Locations, diets, and preferences reconcile in one request instead of a hundred messages.

  3. 03

    Let the group decide in place

    Shortlists members can save, share, and vote on, inside the thread where the idea started.

Every venue. Every detail.

Precision metadata for apps that help people meet, eat and drink.

Venue intelligence

Ultra detailed venue data

Get detailed information about venues, including menus, pricing, ambiance, and more.
Smart matching

Preference driven

Wow your customers with recommendations and information tailored for them.
Multi-location search

Tools for multiple locations. Find restaurants, bars and cafés based on multiple sets of preferences and locations.

In-app experience

Loyal to you

Keep users inside your app by giving them the info they need to make decisions.
Decision support

Built for decision-making

A suite of tools designed to enable you to answer customer needs directly.

Social discovery infrastructure

Turn shared intent into shared plans.

Open up a new world for your users with InBe's preference-aware venue discovery—built for group venue matching, dietary search, and ranked shortlists.

No card required. Full core API access.

Keep exploring

Questions teams ask

Built for developers who connect people to places

Connecting users to real-world places shouldn’t mean stitching geocoding, routing, Places search, and ranking yourself. One preference-aware search replaces the pipeline.

api.inbe.us/v1/search200 OK
POST
{
"locations": [
{ "lat": 51.523, "lon": -0.158, "label": "Alex" },
{ "lat": 51.493, "lon": -0.098, "label": "Sam" }
],
"mode": { "mode": "POINT", "maxDistance": 750 },
"preferences": {
"goodFor": ["date", "cocktails", "conversation"],
"catersFilters": ["vegetarian"],
"establishmentFilters": ["servesCocktails"]
}
}
response
{
"centerPoint": { "Lat": 51.508, "Lon": -0.128 },
"radius": 750,
"establishments": [
{
"displayName": "The Lantern Room",
"distanceMeters": 142,
"matchScore": { "total": 0.94 }
},
{
"displayName": "Barrio Soho",
"distanceMeters": 186,
"matchScore": { "total": 0.91 }
}
]
}

Fair middlegrounds

Multi-person locations in one call; we balance travel so you don’t build routing yourself.

Preferences that actually match

Dietary, vibe, good-for, and constraints as first-class inputs, not post-filters on pins.

Pay for the hard parts

Core search and enriched place data stay cheap; you pay where decision intelligence earns its keep.

Tools for user decisions

Ranked shortlists and experience-ready answers so your product keeps users in-flow, not off to a map.

Illustrative scenario

0ms

Ranked shortlist in one call

Preference-aware search returns a decision-ready shortlist without stacking Places, routing, and enrichment calls.

~15× faster vs multi-call pipelinesNot a live benchmark
RESTWorks with any stack
curl -X POST https://api.inbe.us/v1/search \
  -H "API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "locations": [
      { "lat": 51.523, "lon": -0.158, "label": "Alex" },
      { "lat": 51.493, "lon": -0.098, "label": "Sam" }
    ],
    "mode": { "mode": "POINT", "maxDistance": 750 },
    "preferences": {
      "goodFor": ["date", "cocktails", "conversation"],
      "catersFilters": ["vegetarian"],
      "establishmentFilters": ["servesCocktails"]
    }
  }'

Start in minutes with the knolage you can scale without stress.

Generous free usage to evaluate, startup credits to grow, and a migration path when you are ready to switch from stacked Places pipelines.