OneTapCheckIn for AI agents
OneTapCheckIn helps organizations run events by managing attendee profiles, check-ins, and attendance alerts. Event and operations teams use it to track who showed up and when. 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 OneTapCheckIn.
Check in a participant
Update a participant's attendance record the moment they arrive at an event.
Look up a participant list read-only
Find participants registered for an event before printing badges or sending reminders.
Remove a participant with approval
Take a participant off a list only after an organizer confirms the removal is correct.
19 OneTapCheckIn actions, graded by risk.
Every OneTapCheckIn action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- onetapcheckin.find_listsFind Lists
- onetapcheckin.list_alertsList Alerts
- onetapcheckin.find_profilesFind Profiles
- onetapcheckin.list_passportsList Passports
- onetapcheckin.get_organizationGet Organization
- onetapcheckin.find_participantsFind Participants
- onetapcheckin.get_profile_custom_fieldsGet Profile Custom Fields
write
9Create and change things. Allow, or ask the user first.
- onetapcheckin.create_listCreate List
- onetapcheckin.update_listUpdate List
- onetapcheckin.create_profileCreate Profile
- onetapcheckin.update_profileUpdate Profile
- onetapcheckin.create_profilesCreate Profiles
- onetapcheckin.add_participantsAdd Participants
- onetapcheckin.update_participantUpdate Participant
- onetapcheckin.update_participant_attendanceUpdate Participant Attendance
- onetapcheckin.update_participant_attendance_batchUpdate Participant Attendance Batch
destructive
3Delete, cancel or archive. Ask first, or deny outright.
- onetapcheckin.delete_listDelete List
- onetapcheckin.delete_profileDelete Profile
- onetapcheckin.remove_participantRemove Participant
OneTapCheckIn in three steps.
- 01Your users connect OneTapCheckInThey add their OneTapCheckIn api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create List” can wait for the user, and “delete List” can be denied outright.
- 03Any agent can actYour agent calls OneTapCheckIn through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('onetapcheckin', { read: 'allow', write: 'ask', // create_list destructive: 'deny', // delete_list }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How OneTapCheckIn connects.
Users add their OneTapCheckIn 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 OneTapCheckIn 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 OneTapCheckIn from any agent.
OneTapCheckIn and Arc0, answered.
Can I use OneTapCheckIn with Claude, ChatGPT or Cursor?
Yes. Connect OneTapCheckIn 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 OneTapCheckIn actions you allow.
How do users connect OneTapCheckIn?
Users add their OneTapCheckIn 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 OneTapCheckIn actions can my agent take?
19 in total: 7 read, 9 write and 3 destructive, such as “create List”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in OneTapCheckIn?
Yes. Actions like “delete List” 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 OneTapCheckIn too?
Yes. The same OneTapCheckIn connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug OneTapCheckIn into your agent.
Your users connect OneTapCheckIn once, under your brand. Your agent gets 19 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan