Viator for AI agents
Viator lets travelers search and book tours and activities worldwide, used here to find and surface experiences for a trip. 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 Viator.
Search experiences in a destination
Find tours and activities available at a destination for given dates.
Get details on an experience
Pull full details, like duration and inclusions, for a specific experience, a read-only lookup.
Confirm before finalizing a booking
Check details with the user before completing a booking, since it charges the traveler's payment method.
2 Viator actions, graded by risk.
Every Viator 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.
- viator.search_experiencesSearch experiences
- viator.get_experience_detailsGet experience details
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.
Viator in three steps.
- 01Your users connect ViatorThey add their Viator no auth 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 Viator through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('viator', { 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 Viator connects.
Viator needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.
The same Viator 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
- No auth
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Viator from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Viator and Arc0, answered.
Can I use Viator with Claude, ChatGPT or Cursor?
Yes. Connect Viator 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 Viator actions you allow.
How do users connect Viator?
Viator needs no credentials. Arc0 still applies your policies and records every call, so public tools get the same controls as private ones.
Which Viator 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 Viator?
Yes. Allow read actions and deny writes in the Viator policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Viator too?
Yes. The same Viator connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Viator into your agent.
Your users connect Viator 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