Approved websites

By default the assistant answers from your catalog, your documentation and the conversation in front of it, and reads nothing else on the internet. This page is how you widen that, one destination at a time. An empty list is not a misconfiguration — it is the default, and a perfectly good place to leave it.

When it is worth it

The case for approving a site is nearly always the same: the answer changes and you do not control where it changes.

• A status page, so “is anything down right now” has a current answer.
• A public price list you publish elsewhere and update more often than you update your assistant.
• A partner’s documentation, when your product depends on theirs and their answer is the one that matters.

What an entry says

The domain

A single hostname, or every subdomain of one. Not an address on a private network, and not a bare IP — both are refused, because either would turn a reading tool into a way to probe the inside of a network.

An optional path

Confine the assistant to part of a site — /guide, say. Left empty, the whole domain is readable. Narrower is better: you are approving what an automated reader may fetch, not what you personally trust.

Respecting the site’s rules

On by default: before reading anything, we check whether the site publishes rules for automated readers and obey them. Turn it off only for a site you control or have permission to read.

A note to yourself

Why this is approved, for whoever reviews the list in six months. The assistant never sees it.

What it can and cannot do with an approved site

Approving a site is narrower than it sounds.

• At most two pages are read in the course of answering one question.
• It reads what any visitor to that address would see. It does not sign in, and it carries no credential of yours.
• Reading only. Nothing on an approved site can be changed, submitted to, or acted upon.
• Pausing or removing an entry takes effect immediately, including for anything read recently.

Next steps