Tell Copilot
Describe the room inside the Designer. Copilot builds it in one step you confirm, then changes it when you ask: add a bar, curve the back rows, add a dance floor. It also answers questions about the open chart.
What Copilot does today →You do not have to learn a seating-chart tool. Describe the venue to Copilot, paste what ChatGPT or Claude wrote, or let your AI build it over MCP, and SeatLayer builds a real chart. Finish it by hand: curved rows, tables, the stage, prices and accessible seats. Publish once, and the buyer picker, 3D view, live inventory and box office all read it, hosted, embedded in your product, or through the seat map API.
Each one writes a Venue Spec: what the venue has and where, in words. SeatLayer checks it, names any problem by field, and builds a normal chart you can edit. Nothing goes on sale until you publish. How each way works.
Describe the room inside the Designer. Copilot builds it in one step you confirm, then changes it when you ask: add a bar, curve the back rows, add a dance floor. It also answers questions about the open chart.
What Copilot does today →New from, then Paste from an AI. Copy our prompt into any chat AI, describe the venue, paste the reply. Works in the free demo Designer, no account.
Try it in the demo Designer ↗Connect Claude, ChatGPT or any MCP client. It builds the whole venue in one call and checks it first. A person still approves publishing.
Connect an agent →Select a row, table or section and change it in the side panel. Seats, layout, prices and access needs all live in one chart, previewed in 2D and 3D. When you publish, buyers see that exact version until you publish again.
Publishing and versioning ↗
Straight, curved or fanned rows, round and square tables, booths and standing areas.
Sections, floors, the stage, bars, entrances, exits, signs and labels show buyers how the venue is laid out.
Paint price levels, add ticket types, and fix warnings before the chart goes on sale.
Mark wheelchair spaces, companion seats, captioning and more. Buyers can filter for them.
Upload a plan image or PDF page and click it. One click on a printed seat adds every seat in that block, lettered from the stage and joined across aisles. On a large venue, each click adds a section with its seats. Click the stage or a bar and it becomes a shape of the same size. Each click is one undo step, and plan reading runs in your browser.
Measure one seat, then drag from a row's first printed seat to its last: the row follows the curve and leaves the aisles open. Upload a PNG, JPEG or WebP, or one selected PDF page from a file up to 15 MB and 100 pages (the page is rasterized). Your trace, its bytes and provenance never reach buyers, and it is separate from the optional URL-only buyer background.
A bounded SVG/DXF subset becomes editable shapes, which covers most drawings. There is no SVG export: downloads are PNG, JSON or a clean chart PDF, not a native PDF round-trip.
Every template opens in the Designer. Change the seats, labels and prices until it matches your venue.
Put the Designer inside your own product so your customers draw their own venues. Your server opens a short session for one chart; your secret key never reaches the browser.
The control panel is a live board for each event. Add it to your admin with the SDK and your organizers watch sales, holds and blocks as they happen, and run the event without leaving your product. Each person sees only the tools you allow.
Your server decides each operator's tools; no secret key reaches the browser. Embedded control panel guide ↗
Still have a question? or email hello@seatlayer.io.
dse_… session bound to one workspace, one chart and one origin; the SDK mounts the returned designer URL and validates messages. Your product reacts to ready, saved, published, close and error events, replaces the session before or after expiry, and revokes it immediately when access ends, so organizers edit charts inside your CMS without a SeatLayer login each. The embedded designer guide has the end-to-end flow.sk_ credential to mint a short-lived dse_ Designer session; the browser receives only that origin-, workspace- and chart-scoped session. Published charts are addressed by the rest of the platform: a public buyer picker uses { event, publicKey } for direct public bootstrap, while a private audience replaces publicKey with a token provider. Separately, Designer MCP lets a compatible MCP client work through one authorized chart scope using deterministic tools, validation and review gates; permission, canonical revisions and publishing stay with SeatLayer and the person, and a session may publish only what it was explicitly permitted to.Open the free demo Designer and paste from any AI, or start from the Grand Theatre. Or talk with us about the Designer inside your ticketing or venue product.