Selling walkthrough videos to Airbnb hosts, with Claude and a handful of photos
Start from a listing's public photos, generate a cinematic flythrough in one command, sell it to the host. The exact prompt, both paths (ViewMax over MCP or kie.ai over API), real market pricing, and what the pitch leaves out.
August 11, 2026 · 11 min read
The idea
An Airbnb host has decent photos and no video. Video is what keeps an eye on a listing, and it's exactly what they can't produce themselves: it takes a drone, an operator, and half a day on site.
You start from their public photos and build a continuous flythrough, interior to exterior, without ever leaving your desk.
You're not selling a video, you're selling the trip a videographer no longer has to make.This guide covers the full chain: how to pick a listing worth the effort, the exact prompt that produces the shot, both ways to generate it depending on whether you have an API key, what to actually charge, and the two or three things not to do.
The Claude AI Lab is my Skool community where I share my Claude systems and the more advanced modules. Access is $67/month.
Join the Lab →Picking the listing
Not every property works for this. What you want is a listing where video adds something the photos can't show: volume, a sequence of rooms, a view.
Three criteria are enough to sort fast. The property should be high end (the host has margin that makes a $300 to $600 purchase painless), it needs an outside worth the trip (pool, terrace, panorama, facade), and the photos must be sharp and consistent with each other, shot in the same light.
Save five to seven photos that tell a path, not five angles of the same room. Typically: a bedroom or living room in wide, the window or opening you'll exit through, the facade, the pool or terrace, and one full view from outside. That order becomes your camera move.
If you can't tell from the photos where the camera enters and where it leaves, move to the next listing. A property with no obvious path produces a flat shot, and a flat shot doesn't sell.
Wiring ViewMax into Claude
ViewMax connects to Claude as a connector, which means you order the generation in plain language instead of opening yet another interface. This is the path to take if you'd rather not touch code.
Three steps, exactly as the setup page gives them:
The exact URL to paste into the connector:
https://www.viewmax.io/api/mcp
Once it's wired, you never leave the conversation: you drop in your photos, give it the prompt from the next section, and get the file back. An account is required, and you authenticate at connection time.
It's www.viewmax.io/api/mcp that goes into the connector, not the address of the instructions page. The page explains, the API serves.
Asking Claude for the shot
This is the part that surprises people: there's no cinematography prompt to write. You drop your photos into the conversation and ask for the shot in one sentence.
Generate me a professional walkthrough of this property using ViewMax connector.
That's it. The connector takes the images, works out the camera path, and returns the file. As long as the default render suits you, there's no duration, format, or movement to specify.
That brevity only exists because of the connector, and the distinction is worth understanding: here a product layer interprets your request and writes the cinematography for you. Going through the raw API in the next section, you address the video model directly, without that intermediary, and then you have to describe the shot in detail. Same result, two levels of writing.
If the first render isn't right, add one constraint at a time in the same conversation, in plain language: start inside the bedroom, exit through the large window, finish on the facade, keep it to ten seconds. You iterate in natural language instead of rewriting a block.
No people in the shot, no burned-in text, and above all a house that is actually the one in the photos. A model that drifts toward a generic villa hands you a file that looks good and can't be sold.
The API path with kie.ai
If you already have an API key and would rather script it, the same result comes off kie.ai, which exposes the Seedance models. This is the path for producing in volume rather than one at a time.
The most capable model is bytedance/seedance-2-5. The bytedance/seedance-2, bytedance/seedance-2-fast and bytedance/seedance-2-mini variants exist if you want to trade quality against cost.
Here there's no product layer interpreting your request: you're talking to the video model directly. This is therefore the only point in the chain where the prompt has to be long, and where you describe the camera path yourself.
The skeleton that works, adapted to the property:
Continuous single-take cinematic FPV drone shot, luxury real estate showcase of
the [PROPERTY TYPE] shown in the reference photos, in [LOCATION]. The shot STARTS
INSIDE the [STARTING ROOM] (the one in the reference photos: [2 OR 3 CONCRETE
DETAILS, beams, bed, light]). The camera glides forward slowly in a smooth
elegant arc around [FOCAL POINT], showing the room, then drifts toward the [EXIT
OPENING] with its view over [WHAT YOU SEE].
The camera flies out through the open [OPENING] to the exterior, smoothly climbs
above the roof, then rotates 180 degrees to look back and reveal the full
property exactly as in the reference photos: [FACADE], [GARDEN], [POOL OR
TERRACE], with [PANORAMA] around.
Match the architecture, furniture, materials and landscape exactly to the
reference photos. Bright sunny day, crisp natural light, photorealistic,
stabilized gimbal motion, constant slow graceful speed, no cuts, no people, no
text, no watermark.
Three elements carry the result. STARTS INSIDE in capitals forces the starting point, without which the model opens outdoors nine times out of ten. The three-beat path (arc around a focal point, drift toward the opening, then exit and rotate 180 degrees) gives the shot its structure: you discover the whole property after leaving it. Match ... exactly to the reference photos stops the model inventing a different villa, and it's the line that protects your sale.
The call goes through the usual jobs pipeline: POST /api/v1/jobs/createTask, then poll recordInfo until the state is success.
{
"model": "bytedance/seedance-2-5",
"input": {
"prompt": "<the detailed prompt above>",
"reference_image_urls": ["<photo url 1>", "<photo url 2>", "..."],
"aspect_ratio": "16:9",
"resolution": "720p",
"duration": 10,
"generate_audio": false
}
}
Three constraints only surface in use, and each one costs you a failed generation if you don't know it.
first_frame_url and reference_image_urls are mutually exclusive. Sending both returns a 422. For a path that crosses several scenes, put ALL the photos in reference_image_urls and force the starting point in the prompt, with the STARTS INSIDE above.generate_audio to false: you want a clean rush to edit, not a generated soundtrack you'll have to strip out.One practical note: downloading the finished file from kie.ai's temporary CDN can be blocked depending on your network. If the retrieval curl fails while the job sits at success, it isn't your script, it's the domain. Route the URL through an image proxy or pull the file from another machine.
Going through the API doesn't improve the video, it removes the clicks. As long as you're making one video now and then, the connector is enough. The script pays off once you're producing several a day.
Selling it to the host
The part everyone rushes. You have a video, you still have to place it, and this is where the project becomes income or stays an exercise.
The channel is already in the listing: scroll to the bottom of the page and use the button that lets you message the host. No database to buy, no email to hunt down.
The message that works is short and shows the result before it mentions money. You made a video of THEIR property, that's your only real argument, so don't bury it under three paragraphs of introduction.
Hi [FIRST NAME],
I put together a short flythrough of your place using the photos from your
listing, just to see how it would look. Here it is: [LINK]
If you like it, I'll send you the full quality file, cleared for use on your
listing and your social accounts. If not, keep it anyway, it's on me.
[YOUR FIRST NAME]
On price, it's worth being precise, because this is where the loudest promises circulate. Here's what the market actually pays: a short social clip for a vacation rental sits around $75 to $200, a more finished short promo video between $200 and $600, and a listing video including drone work between $400 and $1,500.
Your deliverable looks like the third category and costs like the first. That gap is what you're monetizing. Asking $300 to $600 puts you where a host says yes without a long negotiation, and below the point where you'd have to justify a trip you never made.
A host looking at the finished video isn't buying a promise, they're buying a file they already want to use. That's the only reason cold outreach works here when it fails almost everywhere else.
The honest math
The reasoning going around on this play fits in a line: two videos a day for twenty-eight days, at $500 each, so $28,000. The arithmetic is correct. What it assumes is much less so.
It assumes every host you contact buys, which no cold outreach ever does, and that you hold the top of the market range on every sale. Across fifty-six approaches, a realistic conversion rate on cold outreach with a demo attached is a single-digit percentage, not tens of percent.
So the useful number isn't the total, it's the unit cost. One video takes about fifteen minutes and a few cents of generation. At that cost you can afford to give away ten to sell one and still come out well ahead. That's the real mechanic: not sales volume, but a demo that's essentially free to produce.
The guardrails
Three rules keep this from turning against you.
The photos aren't yours. Using them to build a demo you send to the host themselves is one thing. Publishing that video on your own channels before they've bought it is another, and you hold no rights to it. Keep the demo private until the sale.
Never claim you filmed on site. The host knows their property better than you do, they'll spot the discrepancies, and a lie about method kills the sale right as it was closing. The honest framing is simple: it's generated from your photos.
Watch the video before you send it. An invented room, a door opening onto nothing, furniture warping as the camera passes: the model gets it wrong sometimes, and it's your name on the message. Ten seconds of viewing settles it.
What you actually keep
This isn't one more hustle. It's a textbook case of the only thing that matters in outreach: you found a spot where producing the proof costs less than promising the result.
The host isn't buying your skill, they're buying a file they've already seen. That's why cold outreach lands here when it's ignored everywhere else, and it transfers well beyond Airbnb: anywhere you can build the demo before the conversation, the conversation gets easy.
Pick a listing with an obvious path, describe one continuous shot with a forced starting point and a rotation on the way out, give the first video away, and charge between $300 and $600. The rest is repetition.
Want to go further?
In the Lab, I share my end-to-end Claude workflows, the ones that save me hours every week.
A dedicated session or program, tailored to your tools and use cases.
And day-to-day, I post one reel a day on Instagram: @quentin_iamarketing