Location agent
The Location agent — meeting venue, airport, neighbourhood
Scores meeting venue distance, airport proximity, neighbourhood fit, transport options, and local context.
Scores meeting venue distance, airport proximity, neighbourhood fit, transport options, and local context.
What it does
The Location agent computes practical distances — to the meeting venue if specified, to the relevant airport, to the centre of the neighbourhood the traveller has implicitly indicated. It also scores neighbourhood fit (quiet/buzzing, family-suitable/business-suitable) and surfaces transport options.
Example inputs
- "15 min walk to meeting"
- "20 min taxi to airport"
- "quiet residential area"
Outputs
location_score with: distance to meeting, distance to airport, neighbourhood type, transport options
Try the live booking flow
Scores meeting venue distance, airport proximity, neighbourhood fit, transport options, and local context. — much of this is already running under the hood on the current IMPT booking flow.
Search hotels →Other agents
Frequently asked
What does the Location agent actually do?
Scores meeting venue distance, airport proximity, neighbourhood fit, transport options, and local context.
Does it run on every search?
Yes. The orchestrator dispatches all 10 agents in parallel for every search. Each agent has a time budget; if one runs slow, partial results stream into the UI while it finishes.
What if it can't find an answer?
It returns 'unknown' with confidence. The ranking engine uses the absence of evidence as a signal — a hotel where the Amenities agent can't validate Wi-Fi will rank lower than one where it can.
Where do I see this in production?
app.impt.io. The Swarm UI surfaces what each agent found — Phase 1 build in progress.