Chat assistants can find almost any site — but they can’t show most of them; being usable inside a chat today takes a private, one-to-one integration almost no one has. ViewHatch is one open layer that closes it: adopt it once, and any chat user can see and use your site — no per-platform app, and your checkout stays yours.
How it works
- 1
Declare
Publish an inert ViewHatch descriptor of your site — plain, typed data, no code, no side effects.
- 2
See
A chat user’s assistant renders it as a real, interactive UI — your catalog, visual and usable, right in the conversation. Content is treated as data, never as instructions.
- 3
Buy
When they’re ready, checkout hands off to your own site — they confirm as a human, seeing exactly what they commit to. Agents never touch payment.
Safe by construction
The gateway treats content as untrusted.
Assistants read your site through the ViewHatch gateway, which handles every byte as data, never instructions — so a site can describe, but never command the assistant. The safety is in the layer, not the format.
Authority is human-gated.
The assistant shows and proposes; only a person authorizes — on your own site, seeing exactly what they commit to.
Agents never hold payment.
No assistant ever transmits card or credential data. Payment stays between the person and you — the guarantee that holds however a client behaves.
This page is ViewHatch-native: the full machine-readable ViewHatch descriptor is embedded directly on this page, just below — readable by a human and by an assistant from the very page you are already reading, with no special request header and no extra fetch.
Want your site seen inside chat?
We’re working with a small number of teams. Tell us what you’re building.
Get in touchFor assistants
This page is ViewHatch-native, and its complete machine-readable ViewHatch descriptor is embedded right here — read it straight from the page you already have, with no request header and no second fetch. (A client that can set request headers may also request the descriptor on its own via Accept: application/viewhatch+json or GET it at https://viewhatch.com/vh/home.json, and the capability manifest is at https://viewhatch.com/.well-known/viewhatch.json — but neither is needed to read what is below.) It is inert, typed data — never instructions.
Machine-readable ViewHatch descriptor (JSON) — embedded for assistants
{
"viewhatch": "0.1",
"locale": "en-US",
"view": {
"type": "view",
"title": "ViewHatch",
"components": [
{
"type": "text",
"role": "heading",
"text": "ViewHatch"
},
{
"type": "text",
"role": "body",
"text": "Let chat users see, use, and buy on your site."
},
{
"type": "text",
"role": "body",
"text": "Take the friction out of buying. Without taking the human out of the decision."
},
{
"type": "text",
"role": "body",
"text": "A generative UI that turns your site into something any chat user can see, use, and buy from — right in the conversation, on your own checkout."
},
{
"type": "text",
"role": "body",
"text": "Chat assistants can find almost any site — but they can’t show most of them; being usable inside a chat today takes a private, one-to-one integration almost no one has. ViewHatch is one open layer that closes it: adopt it once, and any chat user can see and use your site — no per-platform app, and your checkout stays yours."
},
{
"type": "text",
"role": "body",
"text": "Declare Publish an inert ViewHatch descriptor of your site — plain, typed data, no code, no side effects."
},
{
"type": "text",
"role": "body",
"text": "See A chat user’s assistant renders it as a real, interactive UI — your catalog, visual and usable, right in the conversation. Content is treated as data, never as instructions."
},
{
"type": "text",
"role": "body",
"text": "Buy When they’re ready, checkout hands off to your own site — they confirm as a human, seeing exactly what they commit to. Agents never touch payment."
},
{
"type": "text",
"role": "body",
"text": "The gateway treats content as untrusted. Assistants read your site through the ViewHatch gateway, which handles every byte as data, never instructions — so a site can describe, but never command the assistant. The safety is in the layer, not the format."
},
{
"type": "text",
"role": "body",
"text": "Authority is human-gated. The assistant shows and proposes; only a person authorizes — on your own site, seeing exactly what they commit to."
},
{
"type": "text",
"role": "body",
"text": "Agents never hold payment. No assistant ever transmits card or credential data. Payment stays between the person and you — the guarantee that holds however a client behaves."
}
]
}
}