Copilot Ask
AVAILABLEControlled release · chart-aware · public recorded example.
Copilot answers questions about the chart open in the Designer, changes it when you ask, and can take a plan or reference image as input. Every change arrives as a revision you review before it publishes. AI-led 3D improvement is not part of this release.
SeatLayer’s AI seating chart generator is Copilot, working inside the venue designer: it answers questions about the open chart, edits it on request, creates a chart from written requirements, and takes a plan or reference image as input. Every AI revision is reviewed before it publishes.

Controlled release · chart-aware · public recorded example.
Clear a long chat and begin with fresh conversation context.
Compatible MCP clients · OAuth · one authorized chart scope.
Controlled release · Copilot changes the open chart on request; you review the revision before it publishes.
A plan or venue image supplies context. It remains a reference—not automatic venue truth.
The useful foundation is the chart model: rows, seats, tables, sections, labels, categories, accessibility data, floors, focal points, and published revisions. Ask receives an authorized summary of the open chart; it does not become the authority for chart state.
A venue image enters that model as a reference, not as a tracing: you can give Copilot a plan or reference image as input to the chart it is working on, uncertainty is disclosed, traces stay private, and your venue data remains authoritative. Arbitrary image or CAD fidelity is not promised — there is no claim of universal photo understanding, vector round-tripping, or automatic venue truth. If you would rather place the layout yourself, the free seating chart maker is a released route with no AI in the loop.
The model may interpret intent and propose a plan. Authorization, tool execution, canonical revisions, validation, evidence, billing, and publish confirmation stay outside the model.
An illustration of the review gate in the site's own design language — not a screenshot, a recorded session, or a live control. Copilot proposes; the revision, the validation result and the publish decision stay with you.
Every run begins in an authenticated workspace and an explicit chart scope.
Unavailable tools remain unavailable even if a model requests or claims approval.
Idempotency, revision conflicts, billing records, and confirmation come from canonical records.
Validation, before/after evidence, rollback scope, and publish state complete the result.
See which inputs Copilot accepts, what it can change, and what you review before publishing.
Explain capacity, sections, accessibility, labels, and review priorities without changing chart state.
Bounded tools and revision-safe writes: a change lands as a reviewable revision with conflict handling and full-scope rollback, and publishing stays a separate step you take.
Describe the room and Copilot plans the geometry, runs capacity and accessibility checks, and hands you a chart to approve. Human approval stays required before anything publishes.
Give Copilot a plan or reference image as input to the chart it is working on. Uncertainty is disclosed, traces stay private, and your venue data remains authoritative.
Requires actual WebGL before/after proof on the same revision, supported-property changes, mobile checks, and a complete 2D fallback.
Claude, Codex, or another compatible MCP client can use one authorized chart scope. SeatLayer retains write and publish authority.
Buyer WebMCP is a separate opt-in browser workflow: a compatible assistant can read an event, find and select seats on the real map, inspect the selection, and optionally place a hold. It cannot check out or take payment.
Use a SeatLayer template, import a supported public seats.io chart into a draft you review, or provide a private source plan through the Designer. Orders, tickets, payments, customers, and private vendor data do not move with chart geometry.
Use the visual Designer and retain ordinary editable chart objects.
Create a native review-required draft; never auto-publish a cutover.
Authorize one chart and keep trace material private from buyers.
No claim of universal photo understanding, vector round-tripping, or automatic venue truth.
Creating a chart from written requirements is an available capability, as is taking a plan or reference image as input to the chart Copilot is working on. Copilot plans the geometry, runs capacity and accessibility checks, and hands you a chart to approve — human approval stays required, and nothing publishes on its own. The limits are unchanged: arbitrary image or CAD fidelity is not promised, there is no claim of universal photo understanding, vector round-tripping, or automatic venue truth, and AI-led 3D improvement is off.
No. The released 3D buyer view is separate from AI-led 3D improvement. Height and related properties remain normal Designer controls.
Designer MCP is a chart-scoped capability for compatible remote-MCP clients. Client support and setup differ; SeatLayer’s docs show each supported route and preserve OAuth and human publish boundaries.
The public estimator covers confirmed sold seats only. SeatLayer has not published an AI allowance or AI price. Any applicable entitlement and cost boundary must be shown before use.
The machine-readable capability registry is published at /ai-capabilities.json. Product and marketing surfaces are checked against that registry.
It is software that turns a question, a written requirement, or a reference into work on a structured seating chart rather than a picture of one. In SeatLayer that is Copilot inside the Venue Designer: it answers questions about the open chart, edits it on request, creates a chart from written requirements, and takes a plan or reference image as input. Rows, seats, tables, sections, labels, categories, accessibility data, floors and published revisions stay the authority, and the API owns every state change.
Yes — as a reference rather than a tracing. You give Copilot a plan or reference image as input to the chart it is working on; uncertainty is disclosed, traces stay private, and your venue data remains authoritative. Arbitrary image or CAD fidelity is not promised: there is no claim of universal photo understanding, vector round-tripping, or automatic venue truth, and what comes back is a revision you review before it publishes.
A floor plan is one kind of plan or reference image the same workflow accepts as input. The released source routes are a blank start, a SeatLayer template, a supported public seats.io import into a review-required native draft, or a private reference workflow through current Designer and MCP boundaries — so a photo informs the draft you then check, it does not become automatic venue truth.
No — there is no silent publish. A change lands as a reviewable revision with conflict handling and full-scope rollback, and publishing stays a separate step you take. Authorization, tool execution, canonical revisions, validation, evidence and publish confirmation all stay outside the model, and unavailable tools remain unavailable even if a model requests or claims approval. Current states and authority boundaries are documented in the agent capability matrix.
Use the released maker for a quick layout, Copilot Ask for chart understanding, or the agent documentation for a controlled integration workflow.