Give your agent real venue knowledge.

InBetween is a tool your agent can call: structured venue data and preference matching that turn 'find us somewhere for dinner' into a grounded, actionable answer.

Get Started

User request

Natural-language ask lands in the agent.

Restaurant for six after an event — veggie, near the station.

Restaurant for six after an event?
Veggie options please
Within 10 min of the station
1.4s

Thinking & tooling

Resolve constraints, then call InBetween.

Thinking…
Parse party size & dietary
Geocode station proximity
Next: call venue search toolagent

The Lantern Room

Match found · 4 min walk

Veggie
Quiet
Tables for 6
Near station

The Lantern Room — quiet, veggie-friendly, ££, 4 min walk, tables for six.

Grounded reply to user0.2s

For AI agent and conversational product teams

Agents are only as good as their tools.

'Find us somewhere for dinner' is exactly the kind of request agents should excel at. Without structured data behind them, they guess: hallucinated opening hours, vague dietary claims, venues that closed last year.

InBetween gives agents a proper tool. Dietary coverage, atmosphere, noise, seating, and multi-person midpoints are structured parameters, so the model queries facts instead of generating plausible ones.

The result is an assistant that takes a messy, human request and returns a shortlist the user can act on, without ever leaving the conversation.

What breaks today

  • Agents grounded in web search confidently return wrong venue details.
  • Thin place tools cannot answer questions about vibe or group suitability.
  • Users abandon the chat when a recommendation cannot be acted on.

What you can ship

  • Recommendations grounded in verified data rather than plausible text.
  • Multi-person, preference-aware requests handled in a single tool call.
  • Planning that finishes inside the conversation.

How it works for you

  1. 01

    Register InBetween as a tool

    Clean JSON schemas make function declarations straightforward in any agent framework.

  2. 02

    Let the model query facts, not guesses

    Dietary needs, vibe, distance, and group constraints resolve against verified venue data.

  3. 03

    Return answers users can act on

    Ranked shortlists render as cards in the conversation, ready to confirm, share, or book.

api.inbe.us/v1/search200 OK
POST
{
"locations": [{ "lat": 51.51, "lon": -0.12 }]
"mode": { "mode": "POINT", "maxDistance": 800 }
"preferences": {
"catersFilters": ["vegetarian"]
"goodFor": ["groups", "cocktails", "conversation"]
}
}
response
"establishments": [{
"displayName": "The Lantern Room"
"distanceMeters": 320
"catersFlags": ["vegetarian", "vegan"]
"matchScore": { "total": 0.94 }
}]
Venue assistant

Restaurant for six after an event?

Veggie options please

Within 10 min of the station

The Lantern Room — quiet, veggie-friendly, ££, 4 min walk, tables for six.

The Lantern Room

Match found

Veggie✓
Quiet✓
4 min walk✓
Tables for 6✓

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.

A tool worth calling

Ground your agent in real venue data.

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.

Start building for freeExplore the API

Keep exploring

Questions teams ask

Built for developers who connect people to places

Start buildingExplore the API

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"]
    }
  }'
Full examples in docs

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.

Start in minutes

No sales call. Sign in, grab a key, and ship a first search.

Start building

Build — free forever

£10 of usage every month, full core API, no card required.

See Build plan

InBe for Startups

£2,500 usage credit, Grow-level features, and onboarding support.

Startup programme

Switch with confidence

Migration credits from £500, dual-running help, and high-spend matched offers.

Migration programme