从邮件预订到 AI 原生:Mink Viking Experience 如何成为冰岛首家支持智能体预订的旅游运营商

Twelve years ago, when we started Mink Viking Experience, a “booking” meant a tourist standing in the doorway of our studio on Laugavegur with dripping rain boots, asking if we had room that afternoon. Or it meant a phone call. Or — increasingly — an email exchange that would go back and forth four or five times before a slot was locked in.

We built a reputation the old-fashioned way: authentic costumes, expert staff, genuine Viking craft, and obsessive attention to every photo we delivered. The reviews piled up. We held the #1 spot on TripAdvisor's Fun & Games in Reykjavik for years. We never paid for an ad. Word of mouth did the work.

But by 2024, “word of mouth” had a new problem. Our customers weren't just asking their friends anymore. They were asking AI.

The first thing we built: our own multilingual AI chat on mink.is

Before we get into any of the bigger technical story, we want to point at the most concrete result of all of this work — the chat button in the bottom corner of mink.is. Click it and you're talking to a custom AI assistant built specifically for Mink that can:

  • Speak any language our customers speak. English, Icelandic, German, French, Spanish, Italian, Chinese, Japanese, Arabic — you write in your language, it replies in your language, automatically.
  • Answer questions about Viking history, Norse mythology, Icelandic culture, and things to do in Reykjavík — not just sell you a session. We want travelers to get excited about what they're coming to, not feel like they're being funneled into a checkout.
  • Know our full 82-question FAQ inside and out. Any question about the experience — photos, clothing, wheelchair access, kids, cancellation, gift cards, walk-ins, even our Game of Thrones connections — gets answered from our real knowledge base, not a hallucination.
  • Check real-time availability against our own booking engine. Ask “do you have anything open for two people next Friday in USD?” and the assistant queries our live calendar, converts to USD using today's real exchange rate, and hands back a ready-to-click booking link with the date and participant count already selected.
  • Quote accurate prices in all seven currencies we support (EUR, USD, GBP, CAD, AUD, CNY, ISK) using the exact same live exchange rates our shop uses at checkout — no guessing, no cached approximations, no unpleasant surprises at the payment step.

This is a custom WordPress plugin built for us by Ryan Patrekur at Serfraedingur.is, plugged directly into our live booking engine, our FAQ knowledge base, and our multi-currency exchange rate cache. The result feels less like a chatbot and more like talking to a knowledgeable staff member who happens to be on duty around the clock and speaks every language.

If you take nothing else away from this post, open mink.is and try the chat in whatever language you think in. Ask it something real — an availability question, a question about what's included, a question about Reykjavík. That's the small version of the bigger story. Everything below this point is about how we made it possible for other AI assistants — the ones tourists are using to plan Iceland trips right now on Claude, ChatGPT, Gemini, and Perplexity — to know about Mink and answer the same kinds of questions too.

The Bokun trap most operators fall into

When Icelandic tour operators want to get discoverable on the internet, they sign up with Bokun, Viator, GetYourGuide, Klook, or a dozen other resellers. The deal is simple: you give them inventory, they give you bookings, and they take 20–25% commission. Your availability lives inside their system. Your brand lives inside their marketplace. You don't own the customer relationship — they do.

It works. Until it doesn't.

The trouble is that marketplaces were built for a web where humans compare options side by side. That web is rapidly being replaced. When a couple in Denver plans their honeymoon in Iceland today, they don't scroll through GetYourGuide. They open Claude or ChatGPT and type “plan a four-day Iceland trip for two, including something unusual for our anniversary.” The AI does the research. It picks the activities. It might never see the GetYourGuide listing at all, because it learned about Reykjavik from open web sources: TripAdvisor reviews, travel blogs, sites like ours.

If your business is locked inside a marketplace, the AI is one layer of abstraction away from you. If your business is on the open web — searchable, structured, machine-readable — the AI talks to you directly.

What “AI-native” actually means

For the last few months we've been quietly rebuilding the technical foundation of mink.is around one idea: every piece of information a human can find on our website, an AI agent should be able to find and use too.

That sounds simple. It isn't. It meant rebuilding things at three layers:

Layer 1 — Structured content

We rewrote all 82 of our FAQ answers in both English and Icelandic as proper FAQPage schema. We added LocalBusiness and TouristAttraction JSON-LD to the homepage so search engines and AI assistants know exactly who we are, where we are, what we offer, and what people pay for it. We added an llms-full.txt file that spells out everything important about Mink in a format Large Language Models specifically know how to read. Indoor. Weatherproof. Couples. Families. Cruise passengers. Game of Thrones cast have been here. All of it searchable.

Layer 2 — A public booking API

We built a REST endpoint that returns real-time appointment slots for any date and any group size, in any of seven currencies (EUR, USD, GBP, CAD, AUD, CNY, ISK). It pulls live exchange rates straight from our shop's multi-currency cache, so the prices an AI quotes to a customer in Dallas are the same prices that customer sees at checkout — down to the penny. No hidden conversion fees. No stale rates. No “approximately.”

GET https://mink.is/wp-json/mink/v1/availability?date=2026-04-15&participants=2¤cy=USD

Layer 3 — A Model Context Protocol server

This is the new thing that changes everything. MCP is the open standard Anthropic released in late 2024 that defines how AI assistants connect to external tools and data sources. Since then, OpenAI, Google, Perplexity, Cursor, Cline, and most agent frameworks have adopted it. One standard, every major AI client.

We now run a public MCP server at:

https://mink.is/wp-json/mink-mcp/v1/mcp

It exposes our booking engine as five callable tools any AI can use: check_availability, find_next_available, get_pricing, get_business_info, and get_booking_url. A Claude Desktop user in Tokyo can add our MCP server with two clicks and then ask Claude, in Japanese, “when's the next slot for three people, and what are dinner recommendations nearby?” Claude checks our live calendar, quotes pricing in whatever currency makes sense, and hands back a pre-filled booking link. No marketplace in the middle. No 25% commission. No intermediary.

Why this matters for operators

If you run a tour operation in Iceland — or anywhere — here's the thing to understand. The next decade of travel discovery is not going to look like the last decade. Marketplaces will still exist, but they'll be one channel among many, not the dominant channel. The dominant channel will be whatever AI assistant the traveler happens to use that day. And those AI assistants are learning to use open-web data and open-web APIs directly.

If you're locked inside Bokun or Viator, you compete for attention inside a finite shelf that a travel-planning AI may never even look at. If you're on the open web with proper schema, an llms.txt, a REST API, and an MCP server, the AI can see you, understand you, quote you accurately, and book you.

We are, as far as we know, the first tour operator in Iceland to run a public MCP server. We're also one of the first small tourism businesses anywhere to wire real-time multi-currency pricing directly into agent tools. This isn't a flex — it's an invitation. The tools we built are all straightforward WordPress plugins on top of WooCommerce Appointments and WPML Multi-Currency. Any WooCommerce-based tour operator can do what we did.

The design, engineering, and deployment of this entire system — the MCP server, the REST API, the WCML multi-currency bridge, the live pricing injection into our chat widget, the .well-known/mcp manifest, the IndexNow auto-submission pipeline, the llms.txt knowledge base, and the schema.org structured data — was built and shipped by Ryan Patrekur at Serfraedingur.is. Ryan has executed executive-level web application, automation, interactive, and marketing projects for ja.is, Icelandair, tix.is, Brafa, Loft Hostel, Landsnet, and others — and his firm specializes in AI-native integrations for businesses of every size. If you run a tour operation, a hotel, a ticketing platform, or any WooCommerce-based business and want the same capability on your own site, reach out to Ryan directly at ryan@serfraedingur.is. He can do this for you too.

From email to autonomous

Twelve years ago, booking Mink meant writing an email, waiting for a reply, and trusting a stranger to hold your slot. Now, a traveler in Shanghai can ask their AI assistant in Mandarin to find a time for four people next Tuesday, get a real-time quote in yuan, and book the session — all while we sleep. Our staff focuses on what only humans can do: the costuming, the photography, the Viking hospitality. Everything around that — discovery, availability, pricing, scheduling, confirmation emails, currency conversion, language translation — happens without us lifting a finger.

The reviews that built our reputation over twelve years are the same reviews that AI assistants read today to decide whether to recommend us. The difference is that now, when they do recommend us, they can actually book us — not redirect the traveler to a marketplace that takes a quarter of what we earn, and not send an email into a queue that a human has to answer.

Try it yourself

If you build with AI tools: paste this URL into Claude Desktop, Cursor, Cline, Windsurf, or any MCP-compatible client. You'll get live availability, real-time multi-currency pricing, business info, and our FAQ as connected tools:

https://mink.is/wp-json/mink-mcp/v1/mcp

No authentication, no setup beyond pasting the URL. Runs on MCP protocol 2025-11-25.

If you're building a trip-planner product, a travel AI agent, or any platform that helps visitors plan Iceland trips, the same data is also available as a plain REST API for any tech stack. We'd love to be part of it — email ryan@serfraedingur.is and Ryan (the engineer who built all of this) will help you integrate.

If you're a traveler curious about all this: you can ask Claude, ChatGPT, Gemini, or Perplexity anything about Mink — pricing, what's included, hours, location, or even ideas for what to pair a Viking session with in Reykjavík — and get useful answers, because everything about us is published in machine-readable form. When you're ready to book, head to mink.is/booknow.

We went from hand-writing emails to closing bookings through autonomous agents. Not because we wanted to replace the human craft at the heart of what we do — the costumes, the photography, the Viking hospitality — but because we wanted the technology around it to get out of the way. Once a traveler decides to book, the machinery should be invisible. Now it is.

Velkomin to the agentic web. The infrastructure is in place; the rest follows. Book your session. Skál.


Credits: Design, engineering, and deployment of the MCP server, REST API, WCML multi-currency bridge, IndexNow pipeline, chat-widget live pricing, and AI-native infrastructure described in this post — Ryan Patrekur, Serfraedingur.is. Ryan has executed executive-level web application, automation, interactive, and marketing projects for ja.is, Icelandair, tix.is, Brafa, Loft Hostel, Landsnet, and others, and specializes in AI-native integrations for businesses of any size. Contact: ryan@serfraedingur.isserfraedingur.is.

M

Mink Viking Chat/FAQ

Read our FAQ or ask us anything!

I am an expert on Mink Viking Experience and all of its possibilities — ask me anything - in any language! (FAQ)