How it works

{
  "viewhatch": "0.1",
  "locale": "en-US",
  "view": {
    "type": "view",
    "title": "How it works",
    "components": [
      {
        "type": "text",
        "role": "heading",
        "text": "How it works"
      },
      {
        "type": "text",
        "role": "body",
        "text": "How it works"
      },
      {
        "type": "text",
        "role": "body",
        "text": "Let chat users see your site. Take the friction out of buying. Without taking the human out of the decision."
      },
      {
        "type": "text",
        "role": "body",
        "text": "People are shifting how they browse and buy: they ask a chat assistant. The assistant can find almost any site — but it can’t show most of them. ViewHatch is the open layer that closes that gap: a protocol a site publishes and a generative UI that renders it, so any chat user can see, use, and buy on the site — safely, with the human always in control."
      },
      {
        "type": "text",
        "role": "body",
        "text": "For merchants who want to be a real, usable presence where their customers now shop — inside AI chat — without rebuilding for every platform, waiting on approval, or handing over their checkout."
      },
      {
        "type": "text",
        "role": "body",
        "text": "Found, but not seen An agent can read your page as messy HTML. What it can’t do is present your site as something a person can use — a visual, interactive experience in the conversation. That surface exists today only through bespoke, one-to-one integrations and per-platform app programs: build an app, get approved, one platform at a time, and often hand the platform your checkout. Most sites are shut out, and the ones that get in are locked in."
      },
      {
        "type": "text",
        "role": "body",
        "text": "One layer, not a thousand integrations A merchant publishes a ViewHatch descriptor: a small, typed, inert description of what the site offers — no scripts, nothing that runs. Any chat user whose assistant speaks ViewHatch can then see the site, rendered by one shared generative UI, not a bespoke app you had to build. Write once; be seen anywhere ViewHatch is spoken. Sites that haven’t adopted it can still be shown as a best-effort, clearly-marked unverified view; adopted sites get the full, verified, interactive experience."
      },
      {
        "type": "text",
        "role": "body",
        "text": "The gateway treats content as untrusted. These guarantees come from the ViewHatch layer — the gateway that reads on the assistant’s behalf and the inert renderer that presents it — not from the descriptor format. The gateway handles a site’s data as data: it can inform, never instruct."
      },
      {
        "type": "text",
        "role": "body",
        "text": "Authority is human-gated. Assistants propose; people decide — on the merchant’s own site, seeing exactly what they commit to."
      },
      {
        "type": "text",
        "role": "body",
        "text": "Agents never transmit payment authorization. Permanent, by design. Checkout is a human handoff to the merchant’s real page — the property that holds no matter how a client behaves."
      }
    ]
  }
}