# JooEvents

> JooEvents helps organizers run proposals, review, speakers, schedules, and the operational details around an event. This public site is a product overview, not the API origin for a particular installation.

## Start here if you are connecting an agent

- [Connection guide](https://docs.jooevents.com/agents/quickstart.md): Create and store a narrowly scoped key, then let an external agent orient itself.
- [How the external API works](https://docs.jooevents.com/agents/operating-model.md): Direct reads, human-approved changes, availability, and recovery.
- [Agent recipes](https://docs.jooevents.com/agents/recipes.md): Short, discovery-first call sequences for common work.
- [API documentation map](https://docs.jooevents.com/llms.txt): The concise index of public JooEvents integration and operator documentation.

## Product

- [Product walkthrough](https://jooevents.com/): What JooEvents does, with links into the browser demo.
- [Browser demo](https://jooevents-demo.joocorp.com/app): A fictional conference running locally in the browser. It is not an API origin and does not issue API keys.
- [Accelevents-format export demo](https://jooevents-demo.joocorp.com/app/integrations/accelevents): Prepares a ZIP of location, speaker, and session CSVs for manual import. It does not connect to the Accelevents API or keep the two systems in sync.
- [Connect Airtable](https://docs.jooevents.com/integration/airtable-self-host.md): Configure managed, per-area sync between JooEvents and a selected Airtable base.
- [Source](https://github.com/thebowlboy/jooevents): The public JooEvents repository.

## Important boundary

JooEvents does not host an agent. A third-party agent connects to the organizer's own JooEvents installation. That installation's `/api/v1/llms.txt`, `/api/v1/openapi.json`, and authenticated catalogs are the current authority for what the agent may do.