# Eventdoor developer docs (/)

Eventdoor runs your live and on-demand event platform. These docs cover the two ways to work with it from outside the admin.

## Connect an AI assistant [#connect-an-ai-assistant]

<Cards>
  <Card title="Connect Claude" href="/ai-assistants">
    Add Eventdoor to Claude on the web or desktop as a custom connector.
  </Card>
  <Card title="Connect Claude Code" href="/ai-assistants/claude-code">
    One command in a terminal.
  </Card>
  <Card title="What an assistant can do" href="/ai-assistants/permissions">
    It acts as you, reads what you can read, and edits page drafts only when an
    organization admin allows it.
  </Card>
</Cards>

## Call the REST API [#call-the-rest-api]

<Cards>
  <Card title="Get started" href="/rest-api">
    Issue a credential and make your first call.
  </Card>
  <Card title="Authentication" href="/rest-api/authentication">
    Read or write, one organization or the whole platform, and when a credential
    expires.
  </Card>
  <Card title="API reference" href="/rest-api/reference">
    Every operation a credential can call: hubs and broadcasts.
  </Card>
</Cards>

There are no webhooks or SDKs; everything else is done in the Eventdoor admin.

## AI resources [#ai-resources]

These docs are written to be read by AI agents and coding assistants as well as people.

- [/llms.txt](/llms.txt) lists every page with a one-line summary.
- [/llms-full.txt](/llms-full.txt) has every page as Markdown in one file.
- Every page has a `.md` version: add `.md` to its address (this page is [/index.md](/index.md)). **Copy Markdown** at the top of each page copies it.
- The OpenAPI spec for the REST API is at [/rest-api/openapi.json](/rest-api/openapi.json).
- To let an assistant work on your Eventdoor platforms, not just read these docs, [connect it over MCP](/ai-assistants).