Agent & API

Your agent, reading your events

Live today An MCP server and organizer API keys, so the AI agent you already use can read your events, sales and check-ins. Read-only for now: it answers, and it changes nothing.

Start selling

Participants seated at desks during a workshop — A workshop

Works today

Organizer API keys: named, revocable, with an optional expiry
An MCP server, read-only: events, sales, check-in counts and donation totals
Buyer access, off unless you turn it on for a key: orders, buyer details, question answers and donors
Agent activity: every call a key makes, listed for you on Agents & API

Later

Actions that wait for your approval: draft an event, refund an order, message your buyers
Connect your agent in one click, with no key to copy
Webhooks for new orders and check-ins

Connect your agent

In TicketCARE, open Agents & API and create a key. Choose whether it may see buyer details.
In Claude, open Settings, Connectors, Add Custom Connector, and paste the server URL from Agents & API.
Add the key as a request header: Authorization, with the value Bearer and your key.
Ask your question. Revoke the key on Agents & API whenever you want it to stop.

Read-only today.

You: How did the gala sell this week?; Who bought tickets this morning?

Questions organizers ask

Something else? Ask us or book a demo.

Can my agent change anything?

No. Every tool reads. Your agent cannot edit an event, refund an order or message a buyer. Those actions come later, and each will wait for your approval.

Who sees my buyers' details?

A key sees sales and counts only, unless you turn on Buyer access for that key. You can turn it off again at any time.

How do I stop an agent?

Revoke its key on Agents & API. Its next call fails. Agent activity lists every call the key made.

Which agents work?

We test with Claude, as a custom connector. Any other agent that speaks MCP over HTTP and can send a request header can use the same server URL and key.