Build with agents | SeatLayer Developer Docs

Give a coding agent the exact SeatLayer context, constraints, and verification criteria it needs to implement an integration.

SeatLayer publishes the same documentation in two forms: a designed site for people and clean Markdown for coding agents. You should not have to rewrite product knowledge into a prompt before an agent can help.

Install the SeatLayer AI Toolkit

The open-source SeatLayer AI Toolkit packages the repository-first workflow as a portable skill. It adds focused live-doc routing, a read-only integration doctor, verification checklists, and optional Designer MCP configuration. The public Markdown documentation remains the source of truth.

git clone https://github.com/seatlayer/seatlayer-ai-toolkit.git
cd seatlayer-ai-toolkit
node scripts/install.mjs --target codex

Then ask Codex: Use $integrate-seatlayer to add reserved seating to this repository.

git clone https://github.com/seatlayer/seatlayer-ai-toolkit.git
claude --plugin-dir /absolute/path/to/seatlayer-ai-toolkit

Start with /seatlayer:setup, then use /seatlayer:integrate.

git clone https://github.com/seatlayer/seatlayer-ai-toolkit.git
cd seatlayer-ai-toolkit
node scripts/install.mjs --target github --project /path/to/project

Give the agent https://docs.seatlayer.io/llms.txt and the toolkit’s skills/integrate-seatlayer/SKILL.md.

Run the deterministic doctor without installing anything:

node scripts/doctor.mjs /path/to/project

Agent-readable surfaces

Resource	Use it for
`/llms.txt`	Compact index with the right page for each task
`/llms-full.txt`	Complete documentation for a large context window
`/<page>/index.md`	Clean Markdown for one rendered page
`/<section>/llms.txt`	All pages in one section
SeatLayer SDK	Inspect supported JavaScript and React package source
SeatLayer for Flutter	Install the Flutter package; inspect source in seatlayer/seatlayer-flutter
SeatLayer iOS SDK	Inspect the public Swift package and current preview contract
SeatLayer React Native SDK	Integrate the typed Expo, iOS, and Android package and inspect its bridge contract
SeatLayer Android SDK	Integrate the native Kotlin view, coroutine controller, and origin-restricted bridge
SeatLayer AI Toolkit	Install the portable agent workflow and diagnostics
SeatLayer GitHub	Discover all public SeatLayer repositories

The Markdown pages are generated from the same source as the human docs. They do not drift into a separate, abbreviated “AI version.”

What an agent must understand first

Before implementation, the agent should be able to state these invariants:

A chart is reusable venue geometry; an event is a published chart with independent live inventory.
The browser holds seats. Your server books them after it validates the hold and runs payment or order logic.
A secret key is server-only. It must never appear in a browser bundle, mobile app, log, screenshot, or generated example.
Prices and item details used for charging come from the server-side hold inspection, never from browser input.
bookingRef is a stable order reference and makes booking retries idempotent.
A 409 is a normal inventory conflict path and must have an intentional buyer experience.

A prompt that produces a better implementation

seatlayer-agent-prompt.txttext

Implement SeatLayer reserved seating in this repository.

Read first:
- https://docs.seatlayer.io/llms.txt
- https://docs.seatlayer.io/start/quickstart/index.md
- https://docs.seatlayer.io/examples/complete-checkout/index.md
- https://docs.seatlayer.io/integrations/best-practices/index.md

Before changing code:
1. Inspect the existing frontend, backend, checkout, payment, environment-variable,
   error-handling, and test patterns.
2. Explain where the SeatLayer browser picker and server booking call belong.
3. Identify any decision you cannot safely infer.

Implementation constraints:
- Browser holds; server books.
- Never expose SEATLAYER_SECRET_KEY to client code.
- Inspect the hold server-side and calculate the charge from its items.
- Use the existing order id as bookingRef and safely retry with the same value.
- Treat HTTP 409 as a recoverable inventory conflict.
- Preserve the repository's framework conventions and styling.
- Add tests for success, expired hold, booking conflict, duplicate retry, and
  missing server credentials.
- Do not invent SDK methods or response fields. Use the documented HTTP contract.

When finished:
- Run the repository's typecheck, tests, lint, and build.
- Report changed files, assumptions, and any production configuration still needed.

Replace the URLs with local Markdown routes if the agent can browse the running docs site.

Recommended agent workflow

Orient

Read the overview and inspect the host repository. Locate the checkout boundary, payment authority, order identifier, environment handling, and current tests.

Plan against contracts

Name the browser-to-server payload, the server-to-SeatLayer requests, every credential location, and the failure behavior before editing.

Implement the smallest complete loop

Render → select → hold → inspect → pay → book. Avoid unrelated refactors and avoid hiding essential behavior inside a demo-only abstraction.

Test failure paths

Prove expired holds, 409 conflicts, payment failures, duplicate booking retries, and missing credentials—not only the happy path.

Hand off

Return changed files, verification output, assumptions, environment variables, webhook work, and the exact manual journey a human should test.

Designer agents (Preview)

The remote Designer MCP lets an authorized agent inspect a private venue reference, create deterministic geometry, validate the result, and submit evidence for review.

Connect from Dashboard → Agent connections. The endpoint is environment-specific and the product guides the OAuth 2.1 + PKCE authorization for a specific chart.

Definition of done

An agent-assisted integration is not complete until:

the secret key is read only on the server;
the backend ignores buyer-supplied pricing;
the same bookingRef can be safely retried;
conflict and expiry paths return the buyer to a useful state;
responsive, keyboard, and mobile behavior have been checked;
test-mode inventory completed an end-to-end booking;
generated code follows the host application’s conventions; and
the human owner can explain the resulting data flow.

Continue with the complete checkout example or the platform integration guide.