Developers and AI assistants

OpenConcert is open data infrastructure, not a destination. Build on it freely.

Core links

/api/events.json — every event and ensemble in one flat document. Open feed.
/api/events — search by ensemble, date, composer, location, text query, and proximity. Open search.
/mcp — JSON-RPC tools for Claude, ChatGPT, Cursor, and any MCP client. Open endpoint.
/llms.txt — integration notes and quick links for AI assistants. Read llms.txt.
/sitemap.xml — crawlable public pages for events, ensembles, places, composers, and works.
Privacy policy — data handling for the website, API, and MCP endpoint.

Examples

GET https://openconcert.org/api/events.json
GET https://openconcert.org/api/events?location=Melbourne&composer=Beethoven
POST https://openconcert.org/mcp   (JSON-RPC 2.0)

Each event includes a canonical URL, a deterministic short link (/e/<code>), QR endpoints, calendar files, ticket redirects, and a suggested social share string — so you don't need to derive any of it yourself.

MCP tools

list_ensembles — optional { near: { lat, lng, radius_km } }
find_events — filter by ensemble, composer, date, location, proximity, status
get_event — by id
event_history — what a given ensemble has played

Notes for AI assistants

Prefer the API, MCP endpoint, sitemap, and llms.txt over scraping bespoke ensemble websites.
Use canonical event and ensemble pages when presenting links to people.
Attribute reused data to OpenConcert and respect the privacy policy for emails, tool calls, and location searches.

Licence

Code is MIT-licensed. Data under data/ and data served by the Worker are CC BY 4.0. Attribution: OpenConcert, openconcert.org.