AI agents (MCP)
Events and tickets with an AI agent
An agent can set up an event programme and report on how it is selling. What happens at the door stays in the owner interface, on purpose.
Setting up an event
Describe the programme:
Set up a monthly supper club, first Friday of each month for the next six months, 7pm, 24 seats. Early bird €45 for the first 10, standard €55 after that.
That is an event, six dates, and two ticket tiers. Adjust from there:
The April one is a special — make it €65 and 16 seats.
Add a December date on the 20th instead of the first Friday.
Ticket tiers can be added and repriced at any time.
Reporting
This is what the connection is genuinely good for:
How's the supper club selling? Which dates need pushing?
Who's coming on the 6th?
How many tickets went out for the March event, and what did it take?
Attendee lists show names and status. Email addresses appear only when the agent looks up one specific ticket — so "who's coming" does not dump your mailing list into a chat window.
The door stays yours
Deliberately not available to an agent, at all:
- Issuing a ticket
- Checking someone in
- Voiding, refunding or resending a ticket
- Editing attendee details
- Any access or ticket code
Ticket codes are never returned, in any response, and an agent cannot search on one either. That second part matters: if you could ask "is code ABC123 valid?" you would have a way to test guesses against the door. So the answer is simply not available.
If you need to check someone in, void a ticket or look up a code, that is the owner interface — where you are looking at the person in front of you.