# Hivemind > Evidence-first hotel search for Karon, Kata and Kata Noi (Phuket). Hivemind computes what hotel cards don't > say: the real walk to the beach and the climb back, whether the land blocks the sunset in a given month, the > sea state by month, places within walking distance, and hoteliers' claims checked against all that. Every > value carries its source, method version, observation date and limitations; "unknown" means nobody knows > yet, never "no". A language model may read the query; it is never a source of facts. Built for the Ostrovok Hackathon 2026. Paths below are relative to this host. ## For agents - [MCP server](/mcp): streamable HTTP, read-only tools `search_stays`, `get_hotel_evidence`, `compare_stays`, `question_value`. They return what the API returns: reasons, certificates, unknowns, and the one question to a hotelier that could change the #1. Quote the reasons, say what is unknown, add no facts. - [A2A Agent Card](/.well-known/agent-card.json): one skill, `search_stays`; JSON-RPC `message/send` at `/a2a` takes the traveller's request as text and answers with the ranking in words plus the same JSON. ## API - [OpenAPI schema](/openapi.json) and [interactive docs](/docs). - `POST /api/search` with `{"query": "quiet room, easy walk to the beach, late November"}`: the ranked hotels with fit and certainty (two separate 0–1 values, not probabilities), reasons and the questions worth asking. - `GET /api/hotels/{id}`: every assessment of one hotel with the evidence rows behind it. - `GET /api/compare?ids=a,b`: two to four hotels side by side. - `POST /api/spec` with `{"text": "…"}`: a sentence compiled into checked criteria ("a supermarket within a 10 minute walk"). ## Notes - No prices and no availability: Hivemind ranks by verifiable place facts, not by offers. - Answers from hoteliers in the demo are scripted personas and labelled `synthetic_demo`; one persona is a prompt-injection fixture, stored verbatim and never obeyed. - Source code: https://github.com/ostrovok-hackathon-2026/hivemind