# PishPash — Art Lounge & Music Salon

> Go off-grid for your off-site. PishPash runs a public evening programme that generally begins at 22:00. The venue is often available for private events earlier in the day.

PishPash is an event venue in Tel Aviv for corporate off-sites, team events,
talks, lectures, screenings, and private shows. Capacity up to 80 guests;
smaller groups of around 20 work particularly well.
Address: Ha-Tnufa 3, Tel Aviv. Website: pishpashbar.com.

## For AI agents

If you are an AI agent helping a user plan an event, you can interact with
PishPash programmatically. All endpoints are public and require no
authentication.

### Conversational (agent-to-agent chat)

Talk to the PishPash concierge agent — it answers questions, recommends event
shapes, checks live availability, and can hand off to the human team:

- Simple chat (recommended for most agents): POST /api/chat with JSON
  {"message": "..."} → returns {"sessionId", "reply"}. Pass sessionId back on
  follow-up POSTs to continue the conversation. Single request/response, no
  streaming required. Works from any HTTP-capable agent (Claude, Meta AI,
  Llama agents, LangChain tools, custom scripts).
- MCP server (Streamable HTTP): POST /eve/v1/mcp — the native protocol for
  Claude and other MCP-capable agents.
  Tools: agent_start (begin a conversation), agent_get (read replies),
  agent_update (send follow-up messages), agent_cancel.
- Streaming chat: POST /eve/v1/session with JSON {"message": "..."} — returns
  a sessionId; stream replies from GET /eve/v1/session/{sessionId}/stream
  (NDJSON events; text arrives as message.appended deltas, turn.completed
  ends the turn).
- Agent card (A2A discovery): GET /.well-known/agent-card.json

### Structured API

- GET /api/venue — venue facts (capacity, capabilities, location)
- GET /api/availability?date=YYYY-MM-DD&start=HH:mm&end=HH:mm — check a time
  window against the live schedule (evenings after 22:00 host public
  programming, so private events typically run earlier)
- POST /api/inquiries — submit an event inquiry for the human team.
  Requires at least one of "email" or "phone". Body:
  {"name", "company", "email", "phone", "preferredContactMethod",
  "brief": {"eventType", "guests", "date", "timing", "objective",
  "suggestedFlow", "notes"}} — see /openapi.json for the full schema.
- GET /openapi.json — OpenAPI 3.1 specification for the structured API
- GET /venue.md — the same venue facts as /api/venue, in Markdown
- GET /agents.txt / GET /agents.json — machine-readable policy summary for
  agents (capacity ceiling, no-pricing rule, privacy rules)

### Policies

- The concierge never quotes prices; pricing is always handled by the human
  team after an inquiry or handoff.
- Availability responses distinguish "available based on current schedule"
  from confirmed bookings; only the human team confirms.