Waiverfile for AI agents
WaiverFile handles electronic liability waivers, used by activity businesses that need customers to sign a release before participating. 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 Waiverfile.
Get site details
Pull a site's waiver configuration as a read-only check.
Check the event service status
Confirm the waiver service is reachable before sending customers to sign.
Confirm a signed waiver is on file
Check that a customer's signed waiver exists before they're allowed to participate.
2 Waiverfile actions, graded by risk.
Every Waiverfile action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- waiverfile.get_site_detailsGet Site Details
- waiverfile.ping_event_servicePing Event Service
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.
Waiverfile in three steps.
- 01Your users connect WaiverfileThey add their Waiverfile 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 Waiverfile through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('waiverfile', { 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 Waiverfile connects.
Users add their Waiverfile 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 Waiverfile 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 Waiverfile from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Waiverfile and Arc0, answered.
Can I use Waiverfile with Claude, ChatGPT or Cursor?
Yes. Connect Waiverfile 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 Waiverfile actions you allow.
How do users connect Waiverfile?
Users add their Waiverfile 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 Waiverfile actions can my agent take?
2 in total: 2 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Waiverfile?
Yes. Allow read actions and deny writes in the Waiverfile policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Waiverfile too?
Yes. The same Waiverfile connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Waiverfile into your agent.
Your users connect Waiverfile once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan