Agent skills, deterministic diagnostics, and optional Designer MCP configuration for choosing, building, and verifying SeatLayer reserved-seating integrations — hosted checkout, buyer SDK, private access, server SDK, mobile, platform, and operator surfaces.
The toolkit does not replace the SeatLayer developer documentation. It teaches an agent how to inspect a repository, select the right SeatLayer surface, load the smallest relevant live documentation set, implement the integration, and prove the result.
Build SeatLayer integrations with agents · SeatLayer developer documentation · SeatLayer reserved-seating platform · SeatLayer buyer seat-map demos · SeatLayer for developers · SeatLayer on GitHub
| Outcome | Start here | Commerce owner |
|---|---|---|
| Share a complete booking page | Hosted Event Page | SeatLayer managed ticketing |
| Put managed checkout in an existing site | Managed embed | SeatLayer managed ticketing |
| Publish one or many events as a site | Organizer Website | SeatLayer managed ticketing |
| Add seating to an existing checkout | SeatPicker or SeatingChart |
Your platform |
| Sell a private, partner, sponsor, or presale allocation | Hosted access link or buyer access session | Depends on the selected product profile |
| Build a mobile buyer experience | React Native, Flutter, iOS, or Android SDK | Your platform |
| Add organizer chart or event operations | Embedded Designer or control room | Your platform |
Read Choose an integration before implementing. A managed hosted surface does not require a host booking endpoint. A platform/custom checkout does.
The developer documentation is the authoritative contract. Registry pages are the authority for the latest published version.
| Surface | Package or source | Documentation |
|---|---|---|
| JavaScript | @seatlayer/js |
Install |
| React | @seatlayer/react |
Install |
| React Native | @seatlayer/react-native |
Mobile |
| Flutter | seatlayer |
Mobile |
| iOS | Swift package | Mobile |
| Android | Kotlin/JitPack package | Mobile |
Server SDKs are secret-key packages. Never bundle them into buyer-facing code.
| Language | Package | Source |
|---|---|---|
| Node.js | @seatlayer/server |
seatlayer-node |
| Python | seatlayer |
seatlayer-python |
| PHP | seatlayer/seatlayer-php |
seatlayer-php |
| Java | io.seatlayer:seatlayer-java |
seatlayer-java |
| Go | github.com/seatlayer/seatlayer-go |
seatlayer-go |
| Ruby | seatlayer |
seatlayer-ruby |
| .NET | SeatLayer |
seatlayer-dotnet |
Server SDK installation · SeatLayer on GitHub
integrate-seatlayer— a portable Agent Skill for implementation, review, troubleshooting, and go-live work.seatlayer-ai doctor— deterministic checks for exposed credentials, server packages in client code, browser-side booking, unsafe buyer-access token handling, missing idempotency and conflict handling, unaudited channel overrides, and weak webhook verification.- Claude Code commands for setup, integration, diagnosis, and verification.
- Codex and Claude plugin manifests.
- Optional remote Designer MCP configuration. OAuth remains chart-scoped and publication always requires an explicit human decision.
Clone the repository:
git clone https://github.com/seatlayer/seatlayer-ai-toolkit.git
cd seatlayer-ai-toolkitInstall the skill into your personal Codex skills directory:
node scripts/install.mjs --target codexThen ask:
Use $integrate-seatlayer to add reserved seating to this repository.
Load the complete plugin:
claude --plugin-dir /absolute/path/to/seatlayer-ai-toolkitAvailable commands:
/seatlayer:setup
/seatlayer:integrate
/seatlayer:doctor
/seatlayer:verify
Install the portable skill into a project:
node scripts/install.mjs --target github --project /path/to/projectThis writes .github/skills/integrate-seatlayer/ without modifying application
code.
Give the agent these two resources:
https://docs.seatlayer.io/llms.txtskills/integrate-seatlayer/SKILL.md
The complete documentation corpus is available at
https://docs.seatlayer.io/llms-full.txt, but focused page routes are preferred
to avoid unnecessary context.
Run the read-only scanner:
node scripts/doctor.mjs /path/to/projectFor machine-readable output:
node scripts/doctor.mjs /path/to/project --jsonThe scanner never reads files outside the target repository, never prints environment-variable values, and ignores dependencies and build output.
- Choose managed ticketing or platform/custom commerce before choosing an SDK.
- Managed hosted checkout owns payment, Orders, tickets, and booking; do not add a duplicate host booking endpoint.
- In platform/custom commerce, the browser selects and holds while a trusted server inspects and books.
SEATLAYER_SECRET_KEYnever enters browser code.- Payment amounts come from trusted server data, not browser input.
bookingRefis the host order identifier and is reused for safe retries.- Inventory conflicts and expired holds are normal recovery paths.
- Buyer access tokens are event- and origin-bound capabilities. Keep them in memory, never in storage, URLs, logs, analytics, or exception text.
- A private event is token-gated and has no public link; it is not hard-off.
- Listing an event on an Organizer Website makes it discoverable on that public Website and must be an explicit organizer decision.
- Webhook signatures are verified from the raw request body.
The live documentation is authoritative when it conflicts with toolkit guidance:
- Build SeatLayer integrations with agents for the overview an agent should read first.
- Follow the agent integration workflow for the step order this toolkit's skill implements.
- Run the complete checkout example to connect a buyer hold id to payment and idempotent booking.
- Sell private, partner, and presale allocations when the event is token-gated rather than public.
- Install a SeatLayer server SDK for the trusted side that inspects holds and books.
- Review SeatLayer integration best practices before going live.
The included .mcp.json points to SeatLayer's remote Streamable HTTP MCP
resource. It uses OAuth 2.1 with PKCE and a chart-scoped authorization boundary.
Availability and publish capability are shown in the SeatLayer dashboard.
The integration skill must not use Designer MCP unless the task involves chart authoring or review. It must never publish without the user's explicit authorization.
Requirements: Node.js 18 or newer and Python 3 for the optional upstream skill and plugin validators.
npm run validate
npm run check:docsThe first command validates manifests, the portable skill, installer behavior, and deterministic diagnostics. The second resolves every referenced SeatLayer documentation URL. The repository intentionally has no runtime dependencies.
MIT © SeatLayer