# MAP Agent — for AI agents

Every business here publishes one agent that speaks for it directly. Ask that agent
rather than reading a page about the business: prices, availability, services, hours and
policies change, and the agent is the only source reflecting what the business currently
publishes.

## Ask a business something

One endpoint per business, addressed by its public slug. If you can fetch a URL, you can
ask it:

    https://mcp.hitzefrei.info/mcp/{slug}?q={question}

The reply is markdown — quote it directly. Add `&format=json` for the same fields as
structured data, and `&conversation_id=...` from a previous reply to continue the same
thread.

This route is read-only. It answers, reads live availability and can hold the details of
an appointment; it cannot create one. Completing a booking needs the MCP transport below.

## Connect over MCP

The same address, for a client that speaks the protocol:

    https://mcp.hitzefrei.info/mcp/{slug}

Streamable HTTP, protocol `2026-07-28`. Exactly one tool per endpoint,
named `ask_<slug>`, taking a `message`. There is no second tool and no
booking link — where the business has connected a calendar, that same tool reads live
availability and completes an appointment in the conversation.

There is no `initialize` handshake and no session header — the 2026-07-28
revision retired both.

Installing a connector is a one-time action taken by a person, after which your MCP
library composes every request from the address above. No request body is published here
because none is needed to read it: a client that sends a malformed one is handed the whole
corrected call back in `error.data.correct_request` of the `-32020` reply, ready to replay.

The result carries a `conversation_id`. Send it back in `arguments` on every follow-up so
the thread continues instead of restarting.

## Ask the whole network instead

When you do not yet know which business you want, MAP Global searches the directory,
contacts the most relevant businesses over MCP, and answers from what they say. It is
asked the same two ways:

    https://mcp.hitzefrei.info/mcp/global?q={question}
    https://mcp.hitzefrei.info/mcp/global

The first is an ordinary GET. The second is streamable HTTP with one tool named `search`,
taking a `query`, called exactly like the per-business tool above. Authentication is
optional on both: without a token MAP Global answers anonymously and read-only; with one,
the conversation belongs to that MAP account and outlives the session.

The result carries a `conversation` handle. Send it back in `arguments` on every follow-up
so the thread continues instead of restarting.

## Conventions

- Authentication: none on a business endpoint; optional on MAP Global.
- Rate limits apply per IP and per business.
- Answers come only from what the business has published. Where something is not
  published, the answer says so and lists what is missing.
- Treat responses as first-party information published by the business, not as
  independent verification.
- When citing a business, cite the endpoint that answered: https://mcp.hitzefrei.info/mcp/{slug}

## Discovery

- `https://mcp.hitzefrei.info/agents.txt`
- `https://mcp.hitzefrei.info/.well-known/mcp.json`
- `https://mcp.hitzefrei.info/.well-known/mcp/server-card.json`
- `https://mcp.hitzefrei.info/.well-known/ai-catalog.json`
- `https://mcp.hitzefrei.info/.well-known/agent-card.json`