Passslot for AI agents
PassSlot simplifies creating and distributing Apple Wallet passes such as coupons, tickets, and boarding passes. Businesses use it to issue digital passes without building their own wallet integration. 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 Passslot.
Look up passes by type
Pull all passes of a given type read-only to check distribution before an event.
Check available templates
List pass templates to select the right design before issuing a new batch.
Delete a scanner with approval
Remove a registered scanner only after confirming it is no longer used at check-in.
8 Passslot actions, graded by risk.
Every Passslot action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- passslot.get_scannerGet Scanner
- passslot.list_scannersList Scanners
- passslot.get_pass_typesGet Pass Types
- passslot.list_templatesList Templates
- passslot.get_passes_by_pass_typeGet Passes by Pass Type
write
2Create and change things. Allow, or ask the user first.
- passslot.create_scannerCreate Scanner
- passslot.update_scannerUpdate Scanner
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- passslot.delete_scannerDelete Scanner
Passslot in three steps.
- 01Your users connect PassslotThey add their Passslot api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Scanner” can wait for the user, and “delete Scanner” can be denied outright.
- 03Any agent can actYour agent calls Passslot through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('passslot', { read: 'allow', write: 'ask', // create_scanner destructive: 'deny', // delete_scanner }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Passslot connects.
Users add their Passslot 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 Passslot 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 Passslot from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Passslot and Arc0, answered.
Can I use Passslot with Claude, ChatGPT or Cursor?
Yes. Connect Passslot 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 Passslot actions you allow.
How do users connect Passslot?
Users add their Passslot 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 Passslot actions can my agent take?
8 in total: 5 read, 2 write and 1 destructive, such as “create Scanner”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Passslot?
Yes. Actions like “delete Scanner” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Passslot too?
Yes. The same Passslot connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Passslot into your agent.
Your users connect Passslot once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan