---
title: "Your first chart with AI"
description: "Describe your venue in plain words and get a seating chart you can edit, check and publish. Three routes, from no setup at all to an AI connected to SeatLayer."
---
You do not need to learn the Designer to make a chart. Describe the venue in
plain words: how many seats, the layout, the ticket types and their prices,
where the bar and exits are. An AI writes that down as a
[Venue Spec](/agents/venue-spec/), a short JSON file, and SeatLayer places
every seat, table and booth. You get a normal chart that you can change,
preview in 3D and publish.
## Pick a route
| Route | What you need | Time |
|---|---|---|
| [1. Any chat AI](#1-any-chat-ai) | Nothing. The free demo Designer works without an account | A few minutes |
| [2. Claude or ChatGPT connected to SeatLayer](#2-claude-or-chatgpt-connected-to-seatlayer) | A SeatLayer account and a one-time connector setup | A few minutes after the setup |
| [3. Copilot in the Designer](#3-copilot-in-the-designer) | A SeatLayer account | A few minutes |
Most of the time goes into writing the description. The build itself is one
step in every route.
## 1. Any chat AI
Works with ChatGPT, Claude, Gemini or any other chat AI, with no connection
to SeatLayer.
Use the free demo at
[app.seatlayer.io/demo/designer](https://app.seatlayer.io/demo/designer),
which needs no account, or open a chart in the Designer in your dashboard.
Choose **New from → Paste from an AI…**.
Choose **Copy prompt for your AI**.
Paste the prompt into your chat AI. Replace the line in square brackets
with your venue, using the [checklist below](#getting-what-you-asked-for).
Copy the AI's whole reply and paste it into **2 · Paste its reply**. You do
not need to cut out the JSON.
If **3 · Check** lists problems, choose **Copy fixes for your AI**, paste
that into the same chat, and paste the new reply back. Repeat until the
check shows a preview.
Compare the summary with what you asked for, then choose
**Build N-place chart**. The build replaces the draft; one **Undo** brings
the old draft back.
The demo keeps charts in your browser. Sign up to publish or to keep the chart
across devices.
## 2. Claude or ChatGPT connected to SeatLayer
The AI builds the chart in your SeatLayer workspace itself, with no copy and
paste.
Add `https://mcp.seatlayer.io/mcp?tools=build` as a custom connector in
[Claude](/agents/connect-claude/) or a custom app in
[ChatGPT](/agents/connect-chatgpt/). A SeatLayer admin approves the
connection on the consent screen, for one chart or a whole workspace.
In a chat with SeatLayer turned on, write something like: "Build me a
400-seat theatre with stalls in two blocks, curved rear stalls, Premium at
80 and Standard at 55, exits on both sides."
The AI writes a Venue Spec, checks it with `build_from_venue_spec` in
`checkOnly` mode, fixes what the check lists, then builds. Approve the
write when your AI asks. The build replaces the chart's draft.
The AI validates the chart and shows a preview on desktop and mobile, with
the counts it built.
Open the chart in the Designer to review it. Publishing is your decision:
the AI can prepare a review, but it does not approve or publish on its own.
## 3. Copilot in the Designer
Open a chart in the Designer from your dashboard, open **Copilot**, and
choose **Edit chart**.
Write the venue in your own words, as in the other routes.
Copilot writes a Venue Spec, checks it, and asks you to confirm because the
build replaces the draft. Confirm, and the chart appears as a revision you
can review.
If **Edit chart** is unavailable on your account, use route 1.
## Getting what you asked for
The AI can only build what the description says. Include:
- **Seats or capacity**: rows and seats per row, tables and chairs per table,
standing capacity, or booth rows and columns.
- **Layout**: straight rows, rows curved around the stage, tables, standing,
booths, or an arena bowl with stands.
- **Ticket types and prices**, most expensive first, and which area each one
covers. Prices are plain numbers.
- **The stage**, or say there is none.
- **Bars, entrances and exits**, and which side they are on.
- **Section names** as buyers should see them, such as "Stalls" or
"North Stand".
A good description:
```text title="good-description.txt"
A 400-seat theatre. Stalls: 10 rows of 24 seats with a centre aisle,
all Premium at 80. Behind them, Rear Stalls: 5 curved rows of 32 seats
with two aisles, Standard at 55. Curved stage at the front. Exits on
the left and right, main entrance at the back.
```
A vague description, which leaves the AI to guess the counts, the prices and
where things go:
```text title="vague-description.txt"
A medium theatre with good seats and cheap seats.
```
### Check the summary
Before you build, compare the counts with what you asked for. The Designer
shows them next to the preview, for example
`400 seats · 2 categories · 2 sections`. Over MCP, the AI gets the same
summary: seats, tables, booths, standing places, sections, categories and total
capacity. If a number is wrong, tell the AI what to change before building.
## Then finish in the Designer
The AI gives you the structure. Finish the rest by hand:
- change row letters, seat numbers, prices and colours;
- move or curve rows, and draw section outlines, which a Venue Spec cannot do;
- look at the chart in the 3D preview;
- [publish](/designer/publishing-and-versioning/) when it is ready.
More: [charts and objects](/designer/charts-and-objects/),
[sections and seat plans](/designer/sections-and-seat-plans/), and the full
[Venue Spec reference](/agents/venue-spec/).