Humanitix for AI agents
Humanitix is a not-for-profit ticketing platform for events, used by organizers to sell and manage tickets while donating all of the platform's profits to charity. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Humanitix.
Look up an event's details
Pull an event's ticket types and capacity before promoting it to a mailing list.
Check ticket sales for an event
Check current registrations for an event to decide whether to open more tickets.
List events by tag
List events tagged to a category to find similar upcoming happenings.
3 Humanitix actions, graded by risk.
Every Humanitix action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- humanitix.get_tagsGet Tags
- humanitix.get_eventGet Event
- humanitix.get_eventsGet Events
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Humanitix in three steps.
- 01Your users connect HumanitixThey add their Humanitix api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Humanitix through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('humanitix', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Humanitix connects.
Users add their Humanitix api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Humanitix connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Humanitix from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Humanitix and Arc0, answered.
Can I use Humanitix with Claude, ChatGPT or Cursor?
Yes. Connect Humanitix to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Humanitix actions you allow.
How do users connect Humanitix?
Users add their Humanitix api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Humanitix actions can my agent take?
3 in total: 3 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Humanitix?
Yes. Allow read actions and deny writes in the Humanitix policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Humanitix too?
Yes. The same Humanitix connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Humanitix into your agent.
Your users connect Humanitix once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan