Numbers for the venue
Three days before the Acme summer meetup the events lead asks how many tickets are out. Memtro reads the event: 186 issued of 220 available and the revenue so far, so she can give the venue a firm headcount.
Ask how many tickets an event has sold, and how many people have checked in.
Connect Ticket Tailor with an API key and Memtro reads your box office: events and series with tickets issued and revenue, orders with totals, refunds and payment method, and issued tickets with their check-in state. Buyer emails, phones and addresses are never read out. A key reaches one box office. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can issue a ticket to a named attendee, which spends one credit and emails them only if asked, or permanently void a ticket, which refunds nobody.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Ticket Tailor tool, reads what it needs, and answers with the source cited.
These tools change something in Ticket Tailor. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Ticket Tailor, choosing the same kinds; the tab shows Ticket Tailor's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Ticket Tailor signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Ticket Tailor is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
How many tickets have we sold for the Acme summer meetup?
What revenue has the Northwind workshop series taken so far?
How many people have checked in at tonight's event?
Which orders for the Brightwave Ltd launch were refunded?
Issue a speaker ticket for the summer meetup to Priya Nair
Three days before the Acme summer meetup the events lead asks how many tickets are out. Memtro reads the event: 186 issued of 220 available and the revenue so far, so she can give the venue a firm headcount.
Laura Bennett asks Memtro to give the Northwind workshop's guest speaker, Priya Nair, a ticket from the speakers hold and email it to her. Memtro issues the ticket, which spends one credit, and Ticket Tailor emails it to Priya.
The teams that lean on Ticket Tailor most, a question each of them asks, and what they connect beside it.
A record in Ticket Tailor is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In your Ticket Tailor box office open Settings → API and generate a new API key
Copy the key, which starts sk_. A key reaches one box office only, so make one for each box office
Paste the API key into Connections → Ticket Tailor in Memtro and connect
Ask how many tickets you have sold for your next event
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Ticket Tailor tools are the same everywhere.
Only when you ask, and only what it has been granted: issue a ticket for an event to a named attendee, spending one credit, emailing them only if asked; void an issued ticket (permanent), optionally back to a hold. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In your Ticket Tailor box office open Settings → API and generate a new API key.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Ticket Tailor, choosing the same kinds; the tab shows Ticket Tailor's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time