“Create a Monaco GP screening at Brewbot this Sunday, 3 ticket tiers, 120 seats.”
Checks the race calendar, reuses your saved venue, and drafts the event for you to review.
New for vendors
Connect the AI assistant you already use and manage everything by typing what you want. Create events, check sales, make discount codes, work the door — without filling in a single form.
Real requests, and what happens when you make them.
“Create a Monaco GP screening at Brewbot this Sunday, 3 ticket tiers, 120 seats.”
Checks the race calendar, reuses your saved venue, and drafts the event for you to review.
“How is next weekend's event selling?”
Reads your sales figures and tells you tickets sold, revenue, and where the traffic came from.
“Make a 20% code called EARLYBIRD, good for 50 uses.”
Creates the discount code on your live event and reads the details back to you.
“Who's on the door list tonight?”
Lists attendee names and who has already checked in. Never their phone numbers or emails.
“Email people who came to my last screening about Sunday.”
Shows you the audience size first, then sends once you confirm.
“Which of my events did best last month, and why?”
Compares your events and explains what the numbers suggest.
These are not settings you have to remember to switch on. They are built into how the system works, and they apply to every key, always.
Neither is reachable through a key, by any route. Your login stays yours alone.
A key cannot read itself or make another. Only you can, and only while signed in.
Your assistant can tell you what you are owed and when. It can never see or change the account it goes to.
It sees attendee and audience names so it can be useful at the door. Contact details are stripped out before they ever leave our servers.
Everything it creates is a draft. A human on our team still reviews every event before it goes live.
It tells you how many people a campaign would reach and waits for your yes. Capped at three sends a day.
You also choose what each key can do when you create it. Reading your events and drafting new ones is the default; anything beyond that — the door list, discount codes, sending email — is a separate tick box with a plain explanation of what it allows.
Three steps, about two minutes.
In your vendor dashboard, open API keys and create one. Choose what it is allowed to do — reading your events and drafting new ones is the default.
We give you a ready-made snippet to copy. One line for Claude Code, or a small config block for Cursor and VS Code.
Ask for what you want in plain English. Your assistant does the clicking and shows you the result.
For example, connecting Claude Code is one line:
claude mcp add --transport http lightsoutlatte \
https://api.lightsoutlatte.com/mcp \
--header "Authorization: Bearer YOUR_KEY"Your dashboard fills in the key for you and gives you the right snippet for whichever assistant you use.
Anything that supports the Model Context Protocol can connect. These are the ones we have tested.
Claude Code
One command to connect.
Cursor
Add a small config block.
VS Code
Same config as Cursor.
Claude DesktopComing
Needs a small helper app we are still finishing.
Phone appsComing
Claude, ChatGPT and Gemini on mobile need a sign-in flow we are working on.
Claude on the webComing
Same sign-in flow as the phone apps.
Already a vendor? Create a key and connect your assistant in about two minutes. Not yet? Apply first — it is free.
Questions about the assistant? Email info@lightsoutlatte.com.