AI assistant & MCP
AI that can work on your event data, with limits you can audit.
Ask how yesterday's gate compared to last year. Have it set prices for forty products across six booths. Every answer comes from your own data, and every change it makes is previewed, permitted and logged.
One tool set, two ways to use it
Built-in assistant
In the app, for your team. It acts with exactly the permissions the person chatting already has — never more.
MCP endpoint
Connect Claude, or any MCP client, to your own organisation with a scoped API key that an Admin issues and can revoke at any time.
Questions it answers from your data
Events and their dates. Ticket sales by type — sold, remaining, confirmed and scanned, split by online and manual revenue. Attendance and admission rate, by ticket type and by day. Product sales revenue. Survey results in aggregate.
How many VIP tickets are left for Saturday?
Compare gate numbers with last year.
Which booths made the most yesterday?
Work it does for you
Create and update products, categories, producers, exhibitors, catalog entries and tasks. Set what an event sells at each booth. Draft ticket types, currencies, gates and survey questions.
It works by name. No ids, no slugs, nothing you need to look up — and if a name matches more than one record, it asks you which one rather than guessing.
Guardrails
The part your IT director reads
No delete tools exist
Not restricted — absent. There is no path by which AI removes a record, at any permission tier.
Two-step confirmation
Every create and update returns a preview of the exact change first — old value to new value — and writes nothing until it is confirmed.
Double permission gate
A key can only do what its own scope allows and what the person who issued it is actually allowed to do. Downgrade the user and the key downgrades with them.
Rate-limited writes
Twenty writes a minute per key, on top of one-record-at-a-time operations and a duplicate-name guard.
Whole areas are unreachable
No tools exist for individual tickets, ticket emails, users, settings, payments, refunds or media.
Free text is never quoted
Survey comments are counted in aggregate. Their content is never reproduced.
Every one of these is enforced in the code, not written in a policy document.
"What did the AI change last week?" is one filter.
Every change in Event Base records how it arrived — the app, the assistant, an external AI key, a device, or the system itself — and the activity log filters on it.
Who gets what
Editors read events, ticket sales and attendance, and manage content — products, exhibitors, tasks, and what each booth sells. Admins add sales revenue, survey results, ticket types, gates and currencies, and are the only role that can issue API keys. Viewers cannot use AI tools.
Connect it yourself
The MCP endpoint is your organisation's address followed by /mcp. Authenticate with a bearer token issued on the API Access page, with AI access enabled as a separate opt-in per token.
Questions we are asked
- Can the AI delete our data?
- No. There is no delete tool at any permission level — the capability does not exist rather than being switched off.
- Can it act without us knowing?
- No. Every write is previewed and confirmed first, and every change is recorded in the activity log with the channel it came through.
- Which model powers the built-in assistant?
- Mistral. The provider is configurable, so the model can change without changing the rest of the product.
- And through MCP?
- Whichever model you choose. The MCP endpoint serves your own AI client, so the model, the provider and the data agreement are yours.
- Which AI clients work?
- Any MCP-compatible client, including Claude.
- Do we need the AI features?
- No. They are switched on per organisation, and the platform works exactly the same without them.
See it answer a question about your own event
Thirty minutes, in English or Japanese, using your data rather than a demo set.