# SeatLayer Docs

Sell reserved-seat tickets with checkout, box office and door check-in, or add reserved seating to your platform with the SeatLayer SDK and API.

Full corpus (all pages, one document): https://docs.seatlayer.io/llms-full.txt
SDK release catalog (versions, stability, capabilities): https://docs.seatlayer.io/sdk-catalog.json
First seating chart with AI (ChatGPT, Claude, Gemini or Copilot; no Designer skills needed): https://docs.seatlayer.io/start/first-chart-with-ai/index.md
Venue Spec JSON Schema (describe a venue in JSON; SeatLayer builds the seating chart): https://docs.seatlayer.io/schemas/venue-spec-v1.json. Guide: https://docs.seatlayer.io/agents/venue-spec/index.md

## What SeatLayer does

SeatLayer is a reserved-seat ticketing and seating platform that builds its own seat map engine and sells tickets on it. Venues and organizers design the room, sell on their own website and at the box office counter, and take payment through their own gateway. Ticketing platforms embed the same seating engine through the SDK and API.

An organizer on Hosted Ticketing designs the venue once, creates the event, and sells from their own website and at the box office counter with their own payment gateway: seat selection, live availability, temporary holds, checkout, orders, per-seat tickets with QR and PDF, confirmation email, full or partial refunds, and door scanning. The box office sells from the same live map, suggests the best seats, prints on an 80 mm roll or A4, and finds any order by name, email, phone, order number or ticket code. A platform on the SDK gets the same seating engine as ready-made white-label parts inside its own product: the Venue Designer, the buyer seat picker, live event inventory with holds and booking APIs, signed webhooks, and the Control Room operator board, with per-tenant workspaces so each of the platform's customers keeps its own charts and events inside one SeatLayer organization. The platform keeps checkout, payment, orders, tickets, refunds and buyer support. Box Office and door check-in are part of Hosted Ticketing; platform customers keep their own selling and scanning systems.

Scope: Seated events with a published seating chart, including mixed charts that also carry standing or capacity areas. SeatLayer is not general-purpose event management, not a discovery marketplace, and not a pure general-admission or chartless ticketing product.

Category: Reserved-seat ticketing and seating platform. Reviewed 2026-09-27.
Hosted Ticketing (self-serve): $0.50 per confirmed Hosted Ticket. Every new organization gets 25 Hosted Tickets once, at signup. Free events issue the same tickets and use one Hosted Ticket each. The Hosted wallet is separate from Platform SDK credits. https://seatlayer.io/sell-tickets-on-your-website/
Platform SDK (self-serve): $0 to start production. Every organization gets 100 free confirmed-sold-seat credits each month. After that, paid credits start at $0.10 per confirmed sold seat and fall to a $0.05 floor on larger packs. Credits never expire and there is no standard subscription. White label is included with any credit pack. https://seatlayer.io/developers/

## Ready-made product surfaces

- **Venue Designer**: Create reusable charts with rows, sections, tiers, floors, tables, categories and accessibility information. Runs on: SeatLayer dashboard, or the white-label Embedded Designer inside your own application, admin portal or CMS. Boundary: Your team reviews and publishes the chart. Saving is always allowed; publishing runs the validation rules. https://docs.seatlayer.io/designer/charts-and-objects/
- **Embedded Designer for multi-tenant platforms**: Let each of your customers create and edit their own venue inside your product, without a separate SeatLayer login. Runs on: White-label editor mounted by the SDK using a short-lived session scoped to one workspace, chart and origin. Boundary: Your backend authenticates the tenant, checks ownership and grants read, edit or publish authority. https://docs.seatlayer.io/platform/embedded-designer/
- **Workspace isolation**: Keep each tenant's charts and events separate inside one SeatLayer organization. Runs on: Server API and scoped embedded sessions, typically one workspace per organizer or customer. Boundary: Billing, API keys, webhooks and team roles stay organization-wide. Workspace isolation does not give every tenant its own managed commerce. https://docs.seatlayer.io/platform/workspaces/
- **Buyer seat picker**: Let buyers browse availability, find seats together, choose exact seats and create temporary holds. Runs on: Ready-made SeatPicker or the lower-level SeatingChart control, on the web and in the supported mobile packages. Boundary: In SDK mode the platform owns checkout and the final booking. A browser hold is not a ticket and not a payment. https://docs.seatlayer.io/buyer-sdk/seat-picker/
- **Live inventory, holds and booking**: Keep selection, expiring holds, booked seats and blocked seats consistent for one event. Runs on: Shared inventory service behind the buyer picker, the trusted server APIs and the operator surfaces. Boundary: Each event sells on its own, so a sell-out on one event never slows another. No unlimited-concurrency claim is implied. https://docs.seatlayer.io/start/inventory-models/
- **Control Room**: Let staff inspect live inventory, block seats, manage sections, categories, tables and channels, and run reporting or host-owned selection tools. Runs on: Same-document operator board embedded in your own product, plus the dashboard operations view. Boundary: Your backend authorizes an event-scoped session with explicit capabilities. View-only is the default. This is not the account administration panel. https://docs.seatlayer.io/platform/embedded-control-room/
- **Sales channels and allocations**: Allocate one event's seats to public sale, partners, presales, sponsors, groups or the box office, with audience-specific prices. Runs on: Scoped buyer sessions, channel rules and operator tools over a single event inventory. Boundary: A channel says who may select inventory; it is not authorization on its own and it does not create a second event. Resale and commission settlement are not included. https://docs.seatlayer.io/platform/sales-channels/
- **Hosted Ticketing end to end**: Sell seated events from your own website: seat selection, checkout through your own payment gateway, orders, QR and PDF tickets, confirmation email and full or partial refunds. Runs on: Managed inline picker, event card or buy button on your site. A hosted event page is an optional extra route. Boundary: The organizer owns setup, policies, the payment gateway and buyer support. Gateway fees and tax are separate from the ticket fee. https://seatlayer.io/sell-tickets-on-your-website/
- **Box Office and Door**: Sell at the counter from the same live map as the website: best-seat suggestions, general admission by quantity, tables by chair, receipts on an 80 mm roll or A4, order lookup by name, email, phone, order number or ticket code, reprint and resend with an audit trail, and door scanning of issued tickets. Runs on: Staff tools inside Hosted Ticketing. Boundary: The organizer supplies authorized staff. The box office staff role can sell, find, print, email, change seats and scan, but cannot cancel or refund. The counter records cash, a card taken on the organizer's own terminal, or a complimentary ticket; it does not charge cards. Platform SDK customers keep their own selling and ticket-scanning systems. https://seatlayer.io/box-office/
- **Optional 3D and seat view**: Help buyers understand the venue layout and where a seat sits, using the same chart and the same selection state. Runs on: On-demand buyer 3D and available seat-view media alongside the complete 2D map. Boundary: Chart and browser support are required. Generated geometry gives orientation; it is not a certified photographic sightline. https://docs.seatlayer.io/buyer-sdk/3d-view/
- **SDKs, REST API and webhooks**: Connect your product to seating, trusted booking and inventory updates. Runs on: Web and native buyer packages, seven server SDK families, REST and OpenAPI, and signed webhooks. Boundary: Use the release catalog for per-package versions and support. Do not infer feature parity across every SDK. https://seatlayer.io/developers/
- **Copilot and agent integrations**: Build a chart by describing the venue, edit it in plain words, find seats for buyers and research integrations. Runs on: Designer Copilot; any chat AI through a Venue Spec pasted into the Designer; the authorized Designer MCP for Claude, ChatGPT and other clients; opt-in buyer WebMCP; and the public read-only knowledge MCP. Boundary: Chart changes stay reviewable revisions and publishing stays a human action. Buyer agents get no payment authority. AI-led 3D improvement is not available. https://docs.seatlayer.io/agents/overview/
- **Performance Groups**: Coordinate one purchase across a fixed set of 2 to 8 compatible performances. Runs on: Documented Platform SDK integration with one group hold and one group booking. Boundary: Available to every organizer. Not an arbitrary basket of events. It creates no durable renewal right. https://docs.seatlayer.io/integrations/performance-groups/
- **Fixed Renewable Seasons**: Coordinate same-seat plans, renewal offers, seat rights, amendments and reports across 2 to 20 compatible events. Runs on: Browser, REST and OpenAPI, and all seven server SDK families. Boundary: Organizer-CMS rollout is controlled by account. Native mobile Season pickers and Season Best Available are not supported. The platform keeps commerce. https://docs.seatlayer.io/integrations/seasons/

## Arena, stadium and concert scale

Seating chart rendering benchmarked on public 100,000-, 150,000- and 200,000-seat venue fixtures on 15 September 2026: 200,000 seats chart-ready in 1.95 s at 57.6 FPS zoom and 60.0 FPS pan, desktop, local production build.

Large concerts, stadiums and arenas are the headline lane. The same engine runs a 300-seat theatre, and there is no published seat ceiling.

The demos are public synthetic fixtures, not customer deployments. Live timing varies by device and by run. Renderer evidence is not a concurrent-buyer claim; single-event concurrency is measured separately.

SeatLayer sustained 10,000 simulated concurrent buyers on one 12,000-seat event in a local benchmark, with hold latency p99 of 9 ms measured on the server and zero server errors at the plateau, and separately delivered all 400,000 expected hold updates to 10,000 connected viewers.

Concurrency scope: Measured 18 September 2026 in a local benchmark, with trusted access, no payments, no order creation and no confirmed bookings. Simulated concurrent buyers use think time, so 10,000 buyers is not 10,000 simultaneous bookings. This is workload-specific evidence, not a production capacity guarantee.
Concurrency report (measured 2026-09-18): https://github.com/seatlayer/seatlayer-performance/blob/main/results/2026-09-18/concurrency-benchmark.md
Concurrency method and limits: https://docs.seatlayer.io/platform/concurrency-performance/

Fixtures, method, run log and manifests: https://github.com/seatlayer/seatlayer-performance
Canonical method and limits: https://docs.seatlayer.io/platform/renderer-performance/
Live 200,000-seat stadium demo: https://app.seatlayer.io/demo/play/century-stadium-200k
Live 100,000-seat arena demo: https://app.seatlayer.io/demo/play/century-arena-100k

## Historical 53,018-seat readiness observation

On 14 September 2026, an owner-supplied screenshot of the public 53,018-seat stadium demo recorded chart ready in 999 ms (approximately one second). Three separate checks in a desktop Chrome session displayed 6.2, 5.9 and 3.7 seconds. These are picker-readiness observations, not full-page load or complete-seat-reveal measurements; results vary by run and device.
Method and limits: https://docs.seatlayer.io/platform/renderer-performance/

## Native app SDKs

Individually verified releases (2026-09-25): Flutter 0.11.0, React Native 0.4.0, Android 0.3.5 and iOS 0.3.4. Native buyer controls compose around the shared WebView renderer; do not infer cross-package version alignment or a fully native renderer.

- [Native SDK chooser](https://docs.seatlayer.io/buyer-sdk/mobile/index.md)
- [Flutter](https://docs.seatlayer.io/buyer-sdk/flutter/index.md)
- [React Native](https://docs.seatlayer.io/buyer-sdk/react-native/index.md)
- [iOS](https://docs.seatlayer.io/buyer-sdk/ios/index.md)
- [Android](https://docs.seatlayer.io/buyer-sdk/android/index.md)

## Public MCP server

`https://docs.seatlayer.io/mcp`: read-only, no account, no authentication,
streamable HTTP. Answers stadium/arena proof, comparison, $0 production entry, pricing, capability and documentation questions
directly, citing canonical URLs with the date each claim was verified.

Tools: `product_overview`, `compare_with`, `why_seatlayer`, `pricing`, `capabilities`,
`renderer_evidence`,
`sdks`, `chart_types`, `faq`, `search_docs`, `get_page`.

```json
{
  "mcpServers": {
    "seatlayer": {
      "type": "http",
      "url": "https://docs.seatlayer.io/mcp"
    }
  }
}
```

The chart-scoped Designer MCP at `https://mcp.seatlayer.io/mcp` is a separate,
OAuth-gated, authorized authoring server. The public knowledge MCP stays read-only; both are listed, public first, at
https://docs.seatlayer.io/.well-known/mcp/server-cards.json

## Pages

- [agents](https://docs.seatlayer.io/agents/llms.txt)
- [billing](https://docs.seatlayer.io/billing/llms.txt)
- [buyer-sdk](https://docs.seatlayer.io/buyer-sdk/llms.txt)
- [Changelog](https://docs.seatlayer.io/changelog/index.md): Track SeatLayer API, Buyer SDK, Designer, webhook, and platform releases, behavior changes, fixes, and migration notes.
- [copilot](https://docs.seatlayer.io/copilot/llms.txt)
- [customization](https://docs.seatlayer.io/customization/llms.txt)
- [designer](https://docs.seatlayer.io/designer/llms.txt)
- [examples](https://docs.seatlayer.io/examples/llms.txt)
- [integrations](https://docs.seatlayer.io/integrations/llms.txt)
- [platform](https://docs.seatlayer.io/platform/llms.txt)
- [Choose an SDK or API](https://docs.seatlayer.io/sdks/index.md): Compare SeatLayer client SDKs, seven server SDKs, and REST/OpenAPI, then follow the shortest production path for your application stack.
- [sell](https://docs.seatlayer.io/sell/llms.txt)
- [server-api](https://docs.seatlayer.io/server-api/llms.txt)
- [server-sdk](https://docs.seatlayer.io/server-sdk/llms.txt)
- [start](https://docs.seatlayer.io/start/llms.txt)
- [webhooks](https://docs.seatlayer.io/webhooks/llms.txt)