Headout for AI agents
Headout is a travel experiences and activities booking platform for tours, attractions, and entertainment worldwide. Teams use it to manage this booking flow without a manual back-and-forth over email. 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 Headout.
Browse experiences in a city
List available tours and activities in a destination city for a trip itinerary.
Check ticket availability
Look up inventory for a specific experience and date before recommending it to a traveler.
Get product details
Pull the full details for a specific tour, including pricing and duration, before booking.
8 Headout actions, graded by risk.
Every Headout action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
8Look things up. Allowed by default.
- headout.list_citiesList Cities
- headout.list_products_v2List Products V2
- headout.get_product_by_idGet Product By ID
- headout.list_categories_v2List Categories V2
- headout.list_collections_v2List Collections V2
- headout.list_subcategories_v2List Subcategories V2
- headout.list_inventory_by_variantList Inventory by Variant
- headout.list_products_by_categoryList Products By Category
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.
Headout in three steps.
- 01Your users connect HeadoutThey add their Headout 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 Headout through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('headout', { 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 Headout connects.
Users add their Headout 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 Headout 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 Headout from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Headout and Arc0, answered.
Can I use Headout with Claude, ChatGPT or Cursor?
Yes. Connect Headout 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 Headout actions you allow.
How do users connect Headout?
Users add their Headout 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 Headout actions can my agent take?
8 in total: 8 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Headout?
Yes. Allow read actions and deny writes in the Headout policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Headout too?
Yes. The same Headout connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Headout into your agent.
Your users connect Headout 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