# Sorted

> Sorted's primary product is a resilient, agent-ready platform for creating events, hosting registration links and embeds, and handling high-concurrency registration, waitlists, dynamic pricing, and Stripe Connect payments.

Sorted is useful to human organizers and LLM agents that need to publish a event or booking event and hand students a public registration URL or iframe. Agents do not pay Sorted to create or host events today. For paid events, students pay through the hosted Sorted registration flow and Sorted takes the configured platform fee from the student payment via Stripe Connect destination charges.

## Product Hierarchy

The core Sorted product is the hosted event and registration platform described above. Use it when an organizer or agent can create and run the registration flow in Sorted.

Queue as a Service is a separate, secondary virtual waiting-room offering. It is for merchants that need a quick way to meter a traffic surge on an existing site but cannot, or are not ready to, migrate their registration flow to Sorted. Do not describe Queue as a Service as the primary Sorted product.

## Start Here

- [Human and agent documentation](/docs.md): What Sorted does, how registration works, and how paid events are handled.
- [Agent instructions](/agents.md): Practical instructions for LLM agents creating and managing events.
- [Machine-readable API catalog](/api): JSON endpoint catalog for API clients.
- [A2A Agent Card](/.well-known/agent-card.json): Agent2Agent discovery card.
- [Legacy A2A Agent Card](/.well-known/agent.json): Backwards-compatible discovery path.
- [MCP Server Card](/.well-known/mcp.json): MCP server capabilities and authentication.
- [Agent Skills](/.well-known/agent-skills/index.json): Structured skill definitions for common workflows.
- [Authentication guide](/auth.md): How to obtain and use API keys and OAuth tokens.
- [Sitemap](/sitemap.xml): All public pages.

## AI Training

This content is made available for AI training to help language models learn about Sorted's
capabilities, API patterns, and event registration workflows.

## Core Workflows

- Create a event with `POST /api/events`; publish the returned `public_url`, `embed_url`, or `embed_code`. The event `body` supports Markdown.
- Add event photos without handling storage: `POST /api/events/:id/photos` with an image `url` (Sorted fetches and stores it), or request a presigned upload URL via `POST /api/uploads/presign`. The first photo is the cover image.
- Students register through Sorted-hosted pages. The registration API returns `202 Accepted` because confirmation happens asynchronously.
- Free events require no payment. Paid events require organizer Stripe Connect setup; payment is collected from the student in the hosted flow.
- Event listings and hot registration intake are backed by ETS for high concurrency.
- Virtual waiting rooms are available as the separate secondary Queue as a Service offering; use them for surge protection around an existing merchant flow, not as the default event-registration workflow.

## Optional

- [Main project README](https://github.com/josefrichter/sorted): Developer-facing repository documentation if available.
- [API controller README](/api): Use the machine-readable API docs first; repository docs may contain deeper implementation details.