SayLive.ai

Add the SayLive connector

SayLive works as a connector over the Model Context Protocol. You add it once to the assistant you already use, then it stays available in every conversation. The gesture is the same everywhere -- add the connector, authorise it -- but each assistant keeps it in a different place.

In Claude (web or desktop):

1. Open Settings, then Connectors.
2. Add a custom connector and paste the SayLive connector URL.
3. Authorise SayLive when prompted. This links your account so publishes land in the right place.
4. That is it. SayLive now appears among your assistant's tools, on desktop, web and mobile.

In ChatGPT:

1. Open Settings, then Connectors, and turn on Developer mode (under Advanced settings).
2. Create a connector and paste the SayLive connector URL.
3. Authorise SayLive when prompted, then enable it from the tools menu in the conversation.

In any other assistant that supports MCP connectors:

1. Add a remote MCP server (Streamable HTTP) with the SayLive connector URL.
2. Authorise SayLive in the window that opens. The SayLive tools appear in the client.

A paid assistant plan is usually required for custom connectors: Claude Pro, Max and Team include them, and so do paid ChatGPT plans.

Publish your first site

Once the connector is added, publishing is a sentence in the chat. What decides whether the site is any good is what you asked for before it: start with the brief.

1. Ask your agent to build the site. Describe the pages, the content and the tone.
2. Review it in the conversation and ask for changes until it looks right.
3. Say "publish my site". SayLive receives the files, checks them, and puts them online.
4. Your agent replies with the live address, for example yoursite.saylive.site.

Your AI team

Your site is not run by a bare model: it is run by a persona, a named collaborator with a role, a personality and a way of working, downloaded into the assistant you already use. SayLive never rents you an AI. It hands yours a personality, and directs it with our craft.

• Nilo, the Web Builder, is on your team from the first day: he is included with every site, and his pride is the essential perfectly executed
• You can recruit others, like Alma, the Brand & Web Designer. Recruiting is a one-time purchase: a teammate is yours for life, on all your sites
• One persona works on a site at a time. To switch, say so in the conversation: "let Alma take over this site" is the whole gesture
• Nothing is lost when you switch: the brand memory belongs to the site, not to the persona, so a handover is a handover, never a restart

Your team lives in your SayLive space, under AI Team: who is on it, who can be recruited, and who is coming.

Business Blueprints

Prompting is not that simple. Ask for "a site for my law firm" and the model does its best with an average of what it has seen. A Blueprint is the framing that makes up for it: it brings your assistant close to your trade, with the right questions to ask you, the pages a site like yours actually needs, the classic mistakes of your sector, and the claims to verify before publishing.

• Acquired once, for one site of your choice, future revisions included
• Nothing to install and nothing to read: your assistant receives the matter in its brief on every conversation, and applies it by itself
• Written in English and French, served in the language of your site

The catalogue covers trades like restaurants, law practices, health practices, photographers, craftsmen and more. Browse it in your SayLive space, under Blueprints.

What a publish is, and how many you get

A publish is one delivery of the whole site: your agent hands over the files, they are checked, and they become a new version. It is the unit everything else is counted in, so it is worth two minutes of your time.

• Each site carries a capital of 150 publications. That is a capital, not a monthly allowance: nothing resets on the first of the month, and nothing expires
• No more than 20 publications in any rolling hour. Enough for a person working in passes, deliberately tight for an agent stuck retrying
• A publication is only counted when the delivery succeeds
• If the capital ever runs out, a one-time top-up adds another 150. Your site stays online either way

For scale: rebuilding a small site from scratch in a working session costs a handful of publications. 150 is what a site consumes over years of ordinary edits, and the number is there so an agent in a retry loop cannot quietly burn through it in a minute.

Update and roll back

Every publish is a new immutable version. You never lose an earlier one.

• To update, go back to the conversation, ask for the change, and say "publish" again
• Publishing puts the new version online right away, on the same address
• Each publish creates a new version, kept alongside the previous ones
• To undo, ask your agent to roll back to the earlier version. The switch is instant
• Your agent works on the site's draft, seeded from what is online, so a fix stays a fix

Work in progress lives in the site's draft, a private workspace kept at SayLive rather than in the conversation. Close the chat mid-edit and nothing is lost: any later conversation, on any assistant, resumes exactly where the previous one stopped. Editing the draft is free and invisible to your visitors; only publishing spends a publication and moves the site.

Taking a site down, and keeping it

A site is something you own, not a subscription that lapses. If it no longer needs to be online, take it down from its page in your space: the address stops answering right away, and everything else stays.

• Your versions, your draft, your media and your brand memory are kept, with no time limit and at no cost
• Putting it back online is one click, whenever: nothing expires in the meantime
• Your own domain is disconnected and stays yours; you reconnect it when the site comes back
• The name is freed on your account, so a new site can take it over in the meantime

Erasing a site for good exists too, and only you can ask for it: take the site down first, then confirm by typing its address. The site leaves your space immediately and the files are erased after a 30-day window. Receipts and support history stay, the way accounting does.

Keeping old addresses working

An address that used to work and suddenly returns "not found" is a quiet loss: search results, bookmarks, a link from someone else's site, a QR code on a printed flyer. Your site can keep those addresses alive by redirecting them, and your assistant sets that up in the conversation.

Two moments bring it up, and your assistant asks rather than deciding for you:

• You are redoing a site that already existed. Tell your assistant the old addresses — its sitemap, its most visited pages, or just the ones you remember — and each one gets pointed at its new home
• A page moves later on. When a change renames or removes a page that was already online, your assistant asks whether the old address should keep working, and only then writes the rule

Redirects live inside the version, like the rest of the site. They go live with the publish that carries them, they roll back with it, and they work on your SayLive address as well as on your own domain. Your site's page in your space lists the ones currently applied, so you can check without asking.

A permanent move also passes on the search ranking of the old address, which is the point of doing it at all. A page you deliberately retire can be marked as gone for good instead, which is what removes it from search results.

Reviewing before it goes live

By default, publishing puts the site online. That is the point of SayLive, and it is what the name says. Some sites reach a stage where you would rather look at the next version before your visitors do.

The staging option adds a second address to the site, alongside production. Once it is on, publishing prepares the version there instead of going live, the site that is online does not move, and one sentence promotes the version you kept.

• A staging address of your own, never indexed by search engines
• Publishing prepares, it no longer goes live by itself
• Say "put it online" when you are happy, and production moves
• It is offered once the site is live: before that there is no production to protect

Without the option, nothing changes and nothing is hidden from you: rollback is still one sentence away, and it is what most sites use instead. The habit that makes either of them rarely necessary is reviewing the page before you publish it.

Have your site reviewed

Every publish hands back a review link, next to the live address. It opens your site with a small review layer on top, and it exists for two readers: you first, then the people you share it with.

Start with yourself. Open the link, browse your own site, and click where something is off: a photo, a line, a spacing. Say it in one sentence. The page and a screenshot of what you were seeing travel with the remark on their own, so you never upload or describe anything. Then tell your assistant to work through the review tickets, and it fixes them point by point.

• The link is secret and never inside the site: a visitor without it sees an ordinary page
• Your reviewers need no account: they click, they write, they are done
• The screenshot takes itself at the moment the reviewer aims, and costs nothing on your media quota
• Every site includes 25 review tickets, trial included; a one-time top-up adds more when a real review session eats them

Republishing never re-issues a link you already shared, and you can close the door at any time by asking your assistant to turn the review link off.

Photos and other files

A publish carries the site itself: HTML, CSS, JavaScript, SVG. Photos and other binary files live in your media library instead, uploaded once and reusable by every version.

1. Open your site in your SayLive space and go to Medias.
2. Upload the photos you want on the site (50 MB included, extendable).
3. Tell your agent to use them: each file is available at /_media/its-name.jpg

Your agent sees the list of uploaded files, so it can place them itself. It never has to link a stock photo from another site, which is the kind of image that disappears months later. The guide on images covers weight, dimensions and alt text.

Use your own domain

A site is live on a SayLive subdomain from the first publish, for example yoursite.saylive.site. That address is permanent. A domain of your own is added on top of it, never instead of it: once it is connected, both addresses answer.

SayLive does not sell domain names. Buy yours from any registrar and you stay its holder: your address should never depend on us. Connecting it is included in the payment for the site, so there is nothing more to buy, and no right that expires. It does need a paid site: a free trial that could obtain a credible name with a valid certificate is exactly the shape of a phishing page. Why we refuse to sell names, at length.

1. Open your site in your SayLive space, go to Domain name, and enter the domain you own. Use the www form, like www.yoursite.be.
2. Add the DNS record we show you in the DNS zone of that domain, at the registrar where you bought it: one CNAME, from your name to connect.saylive.site, TTL left at its default.
3. Click Check now. We look at two different things, and both must be green: that your record is visible, and that the HTTPS certificate is issued.

Your agent can do all of it from the conversation instead: it hands you the exact record, then checks where the connection stands whenever you ask.

• The record only concerns that one name. Your email keeps working, because MX records are separate records that nothing here touches
• The bare domain (yoursite.be, without www) works too, but most registrars refuse a CNAME there: use an ALIAS or ANAME record if yours offers one, otherwise redirect the bare domain to the www
• Your site stays online the whole time, on its SayLive address, including while you wait
• Removing a custom domain never takes the site offline, and the name stays yours at your registrar

The “Made with SayLive” badge

A small badge sits at the bottom of the page. It is added when the page is served, not written into your files, which is worth knowing before you go hunting for it: deleting it from the HTML changes nothing, because it was never in the HTML. The switch is what controls it.

The badge carries your own referral link. Someone who clicks it and ends up buying credits you €10, and the person who arrives through it gets €20 off. That is the trade: it is there during the trial and on a basic site, and it pays its way.

• Recruiting a persona unlocks the switch. It does not flip it: the badge stays until you take it off yourself
• From there it is yours in both directions: turn it off, or put it back, at any time
• The switch is in your space, on the site's page, and your agent can work it too
• Removing it takes your referral link off the site, which is the only reason to think twice

Handing a site over to its owner

Built for someone else? When the work is done, the site transfers to their own SayLive account: their billing, their domain, their space. You keep nothing you do not want to keep.

• The transfer moves the whole site: versions, draft, media, form inbox, review tickets and brand memory travel together
• Their assistant picks up where yours stopped: the memory belongs to the site, so the handover loses nothing
• Your other sites and your account are untouched: hand over one site, keep the rest

Start it from the site's page in your space: you name the future owner's email, they accept from their own account, and nothing moves until they do. You can take the offer back at any point before that.

Supported files and limits

SayLive publishes static sites: from a one-pager to a full multi-page build, in one language or several. What does not fit is accounts, databases and server code.

Item	Supported
Pages and markup	HTML
Styling	CSS, inline styles
Behaviour	Static JavaScript (no server)
Assets	Images, fonts, icons (via your media library)
Not supported	Server code, databases, logins

If your project needs accounts, a database or server logic, that is a full web application rather than a static site, and a different kind of build. What fits and what does not, case by case.

Whatever you publish stays yours: download any version as a ZIP from your space and host it anywhere, any time.

Troubleshooting

• The connector does not appear: check that your assistant plan supports custom connectors, then re-add it
• Publish is rejected: your agent may have included an unsupported file type. Ask it to keep the site static
• Domain not resolving yet: DNS propagation takes a few minutes to a few hours after you add the record. Nothing is lost, leave the record in place and check again later
• Domain still waiting after a day: check the Name field at your registrar. Some want just www, others the full www.yoursite.be, and a record saved under the wrong name never appears
• The check says the certificate is being issued: the DNS part is done and there is nothing left to do, it usually takes a few minutes

Setup questions.

Do I need to install anything?

No. You add the SayLive connector inside your assistant, which is a few clicks and an authorisation. There is nothing to download.

Can I publish a site an agent made in a past conversation?

Yes, as long as you still have the files. Bring them into a conversation with the connector added and ask to publish.

How many sites can I publish?

As many as you like. You pay €99 once per site, after the 14-day free trial, and each one is independent. There is no monthly limit, no bundle to subscribe to, and no total that grows over time.

How many times can I update my site?

Each site carries a capital of 150 publications, which is a capital and not a monthly allowance: nothing resets, nothing expires. The cadence is capped at 20 publications per rolling hour so a retrying agent cannot burn through it. If you ever exhaust it, a one-time top-up adds another 150 and the site stays online throughout.

Can I remove the “Made with SayLive” badge?

Recruiting a persona unlocks the switch, and you work it yourself from your space or by asking your agent. It never comes off on its own: the badge stays until you remove it. It is worth knowing what it does before you take it off: it carries your own referral link, so a visitor who clicks it and buys credits you €10. You can put it back at any time.