For assistants and the people who use them
Publish a site your AI built.
Then keep working on it.
Plenty of things will put a page your assistant wrote on the internet. What happens next is where they stop: the site is a folder, and every change means sending the whole thing again.
PromptSwing hosts it as a shop. Your assistant can read it back, change one page, restore an earlier version, and sell through a checkout that pays into your own account.
Start hostingQuestions, answered
How do I publish a website my AI assistant built?
Connect PromptSwing to your assistant over MCP and call land_site with the files it generated. The store goes live on its own address with a certificate. If a store is already there, the first call does not publish: it returns what would be replaced and a confirmation, and only a second call carries it out.
Can it edit the site afterwards, or does it have to rebuild it?
It can edit it. read_site returns the files that are live, so your assistant sees what it is changing instead of starting again. add_page, update_page and delete_page each change one file. Until 2026-09-09 this was not possible and every change meant republishing the whole site.
If it only sends the page it changed, does everything else get deleted?
Not in patch mode, and that is structural rather than a promise: the patch path has no code that removes a file. Your images, your favicon and your stylesheet survive an edit that never mentioned them. A full replace can still drop files, and when it would, it names every one of them before it does it.
What if a change breaks something?
Every publish is kept as its own version. revert_site lists them and puts the site back to one of them — no rebuild, and the version you are leaving is kept too.
Is this just hosting, or does the shop actually work?
It sells. A landed store gets a catalogue your assistant can read and write, a checkout that settles into your own Stripe account, cart recovery, review requests after an order, and order signals you can read back. That is the difference between publishing a website and publishing a shop.
Who owns the site and the customer data?
You do. The content, the products, the customer data and the domain are yours, and PromptSwing hosts the infrastructure. If you leave, you take all of it with you. Money from your shop settles into your own payment account — PromptSwing is never the merchant of record for your sales and takes no commission on them.
What does it cost?
Hosting starts at $20 a month for the site and the hosting. Hosting a site you bring, with cart recovery, reviews and order intelligence around it, is $100 a month. There is no free tier and no trial — hosting requires an active subscription, and your assistant will be refused if there is not one.
What does it NOT do?
It does not build the site for you on this path — your assistant does that, and PromptSwing is where it lands. A page that was built elsewhere only reports carts and orders where it calls the documented signal endpoints; assess_site tells you which of those calls are missing before you land, but nothing on our side can add them for you. And an assistant cannot buy the subscription — a person does that once, in a browser.
Connecting: PromptSwing runs a remote MCP server at https://api.promptswing.com/api/connector, discovered through RFC 9728 protected-resource metadata and authorised by the merchant over OAuth 2.1. A machine-readable summary of everything on this page is at /llms.txt.