Intelligence · Component · destination-hotel-grounding
Destination and hotel grounding cards
What it does
Retrieve structured destination/hotel context, traveller fit, transport and nearby POIs from travel grounding data.
Core pattern
Entity-based fact retrieval + fit reasons and evidence
- Input
- Destination or hotel identity
- Output
- Grounded cards and evidence context
Key parameters
| Name | Type | Default | Values |
|---|---|---|---|
| query | string | — | — |
| limit | integer | 20 | 1–1000 |
| city | — | — | — |
Maturity and limits
Dedicated grounding tools and database query modules. Static source inspection only; no runtime, provider, deployment or test-pass claim.
Apache-2.0 with NOTICE obligations; supplier content retains separate rights. Agent scopes, booking PII and trusted card/payment flows require isolation.
Industry tags
- Travel & hotelsSource-supported industry
For work involving destinations, room rates and bookings, use entity-based fact retrieval followed by fit reasons and evidence.
- Manufacturing & industryTransferable use
For unified lookup of spare-part catalogs and equipment records, use entity-based fact retrieval followed by fit reasons and evidence.
Skills pack
Contract scaffold and deterministic mock
Download · 10KBSHA-256 c1bad942d82cf9d0d40fb293a59084151b63366d2f4edf8d92f6fc25d953d11e
Related components
-
Image and text product similarity search
Shared image-text retrieval + similarity tiers and attribute filters
Working 1 pipeline -
Hotel benefit evidence and comparison
Side-by-side benefit facts + commitment status distinction
Working 1 pipeline -
Multilingual hybrid retrieval and online reindexing
Multi-route retrieval fusion + access filters and index switching
Working not yet in a pipeline -
Travel master and inventory synchronization
Upstream record staging + import audits and snapshots
Working 1 pipeline