Known

The Known pillar is about being understood by AI agents. It captures who a venue is, what makes it distinctive, and who it's for.

The challenge

A venue's website tells a human story. Photos, prose, design choices. Humans read between the lines.

AI agents need explicit structure. "Intimate" needs to mean something specific. "Romantic" needs to connect to occasions like anniversaries. "Design-forward" needs to be a recognisable category, not just a marketing phrase.

Known turns implicit character into explicit structure that agents can reason about.

What Known contains

How Known is built

Groundry assembles Known from multiple sources:

  • Existing content (websites, listings, descriptions)
  • Direct input from the venue
  • Third-party data where available
  • Verification from trusted sources

The process structures this information into a consistent format. Claims link to evidence in the Trusted pillar.

An example

A boutique hotel's Known might include:

CategoryContent
TypeHotel, boutique, 24 rooms
VibeIntimate, design-forward, locally-rooted
AmenitiesSpa, restaurant, garden, EV charging
Ideal forCouples, creative retreats, milestone celebrations
OccasionsAnniversaries, reconnection trips, digital detox

When an agent receives a query like "somewhere quiet for a few days away from screens," this structure lets it match confidently rather than guess from keywords.

What agents can do with Known

  • Match queries to venues based on character, not just category
  • Describe venues accurately when recommending
  • Explain fit to guests asking "why this place?"
  • Filter appropriately when a venue wouldn't suit

The structure enables reasoning. An agent can understand that a family-friendly resort probably isn't right for a romantic weekend, even if both are "nice hotels."