Does an AI co-host need your Airbnb password?

No. It never sees your password, and it has no login of yours to hold. Everything an AI co-host needs arrives three ways, none of them a credential: Airbnb grants listing access through its own co-host invite with the scope you choose, your guest messages travel through a mail rule that lives in your mailbox, and your approvals are one-word email replies. We run a live co-hosted listing this way, and at no point in setting it up did the host type a password anywhere except Airbnb itself. If a service asks you to hand over your Airbnb login so its AI can answer guests, the right response is to close the tab — a shared password can do everything you can do, and nothing about answering guests requires that.

Access comes from an invite, and you pick the scope

Airbnb already has a front door for letting someone work on your listing: the co-host invite. You send it from your listing's settings, and the access level is chosen by you at invite time — on our live listing the host selected "Calendar and messaging access," which is exactly what message handling needs and nothing more. Payouts, pricing, taxes, the listing's existence: all outside the grant. The co-host operates inside a permission Airbnb enforces, under an identity Airbnb knows, visible on your listing where you can see it. A password has no scope. An invite does.

Your messages travel by a rule you own

The second piece is how guest messages reach the AI at all: a rule in your own mailbox that redirects Airbnb's notification mail to the service's ingest address. You create it, in your mail settings, in about a minute — nobody logs into your email, because nobody can: no credential for your mailbox was ever shared either. That rule is also a kill switch you hold unilaterally. Delete it and the AI goes deaf the same minute, with nothing to ask and nobody to notify. Compare that with a connected account, where you have to trust the other side to honour a disconnect.

The only thing you ever type is SEND

Day to day, the loop asks you for one word. A drafted reply arrives in your inbox and you answer SEND, or SKIP, or REPLY: with your own words — no dashboard, no session, no password entered on anyone's site. The security there is carried by a signed token in the notice and a sender check against your account, so the approval is yours without you ever holding a credential that could leak. A system that never collects your password cannot lose it.

The identity checks point the other way

Here is the part that surprises people: in this arrangement, the one who has to prove who they are is the co-host, not you. When we accepted the invite on our listing, Airbnb stopped the acceptance cold until the co-host account passed identity verification — government ID, at the moment of clicking Accept. You are not being asked to trust an anonymous service with your keys; you are extending a scoped, revocable permission to a verified identity, on a platform that records the relationship. That is the correct direction for the trust to flow.

Revoking it all takes two clicks and no cleanup

The test of any access arrangement is what leaving it costs. Here: remove the co-host in your Airbnb settings, delete the mail rule in your mailbox. Done. There is no password to rotate, because none was shared; no API key to hunt down, because none exists; no wondering whether a copy of your login lives on in someone's database. Both switches were on your side of the wall the whole time. And the same boundary governs what the AI could ever see day to day — guest messages, and only guest messages, never the account behind them.

If you want to see what the AI does with the access it actually gets, paste your listing into the demo at /try and ask it what your guests ask. It will answer from your listing's public facts — no password required there either, which is rather the point.