AI Event Discovery

ONE SOURCE OF TRUTH

AI sits above the public event contract

The gateway does not read event tables directly. Every tool uses the same canonical public discovery layer that powers the v1 Public Events API, so organiser identity, event dates, location privacy, ticket states and booking actions remain consistent.

AI assistant→MCP gateway→Public Events API→nawhe.event

READ-ONLY TOOLS

Five focused discovery actions

search_events

Search by words, city, country, category, tag, date intent, free events or sort order.

find_events_nearby

Discover events around coordinates with a radius in miles while preserving canonical location privacy.

get_event

Retrieve one published event using its canonical public representation.

get_ticket_options

Read public ticket names, prices, current sale state, remaining quantity and order limits.

get_booking_link

Return the current public CTA and canonical nawhe? or external ticket hand-off without creating a transaction.

CONNECT

Use the MCP endpoint

Compatible clients connect to the public endpoint below. The gateway supports MCP initialization, tool listing, tool calls and ping over JSON-RPC 2.0.

POSThttps://nawhe.com/mcp

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_events",
    "arguments": {
      "city": "London",
      "country": "GB",
      "when": "weekend",
      "per_page": 8
    }
  }
}

A simple GET /mcp returns gateway metadata and the current public tool list for inspection.

HUMAN-CONTROLLED TRANSACTIONS

Discovery can be automated; payment cannot

The gateway cannot create a booking, charge a card, issue a ticket, refund an order, alter an event or access private customer/promoter records. get_booking_link only returns the canonical public hand-off URL so the attendee completes any consequential transaction through the controlled nawhe? or external checkout.

Available

Published event discovery, public organiser data, public location, public ticket state and booking links.

Never exposed

Attendee records, promoter user IDs, payment credentials, payout settings, private addresses, audit logs or admin data.

CONTROLLED OUTPUT

Compact results as inventory grows

AI search tools default to 8 events and cap each response at 20. Pagination metadata tells the client whether another page exists, preventing large event catalogues from being pushed into one model response. Nearby radius is capped at 250 miles.

AI booking hand-off attribution

When an AI client requests the booking-link tool, nawhe? preserves the unmodified canonical URL and may return a separate hand-off URL with a privacy-safe AI referral marker. This helps first-party attribution without creating a booking, changing the event identity or exposing customer data.