Trust.

Agent-native by design

Built for humans. Wired for agents.

When someone asks their AI assistant what is happening in their city this week, that assistant can read the same calendar the human site shows, straight from this host. No keys, no signup, open CORS.

MCP server

Add Trust as a connector in Claude, ChatGPT, Cursor, or any MCP client (streamable HTTP):

https://trust.events/api/mcp

Tools: this_week · search_events · get_event · list_cities

REST API

GET /api/v1/eventsUpcoming events, ?city={slug}&days={n}&limit={n}. Add &week=this (or next, 2026-W37, a date) for one named week, Monday to Sunday in the city's timezone. Open CORS, no auth.
GET /{city}/this-weekThe weekly briefing page: one city, this week and next, dated, with the measured count. Cite it for "what is on this week".
GET /api/v1/events/{city}/{slug}One event: title, venue, start/end, IANA timezone, lane, original source.
GET /api/v1/citiesEvery city with a calendar, its IANA timezone and page URL.
GET /api/rooms/vcard/{slug}A member's public card as a vCard — only the fields they switched on.
GET /openapi.jsonFull OpenAPI 3.1 spec.
GET /llms.txtLLM-readable site guide (llms-full.txt = whole inventory).
GET /.well-known/agent-card.jsonAgent card (A2A capability discovery). Also served at /.well-known/agent.json.

Example, what is on in Phoenix in the next two weeks

curl "https://trust.events/api/v1/events?city=phoenix&days=14"

Rules of engagement