The one link: one address per business, every assistantNov 4, 2026A business signs up and gets one address. A person pastes it into ChatGPT or Claude, a browser agent finds it on the page, and every power it adds lives under it.
- One address per business; its powers live under it. Never one link per power as the primary address.
- Three layers in order: hosted powers.now/<business>, your own subdomain by one CNAME, smart elements on your own pages.
- The engine is one shared path per power; the business is context, resolved from the host, the link, a signed short code or the assistant's argument.
Two honest tiers inside chat: nothing connected, and connectedNov 4, 2026Nothing connected: the assistant reads the page and hands the visitor a deep link. Connected: our card renders inline through MCP Apps. We tested both, so we say both.
- Nothing connected: the assistant renders its own card from our page and the read API and hands over a deep link. Real, useful, not our card.
- Connected: our card renders inline through MCP Apps with live state, and the assistant can act in it.
- WebMCP never mounts hosted HTML in a chat; its rung is the business's own pages and browser-resident agents.
What a power is, and why the word mattersNov 4, 2026A power is one definition that renders inside ChatGPT, inside Claude and on your own site, sharing one live state. Not a widget, not a chatbot, not a plugin.
- A power is one definition with three renderings: the page, the card in chat, the layer for agents.
- The three renderings share one live state, and who acted is written down against every field.
- Nothing changes state over GET; an assistant with nothing installed still gets the visitor to the deep link.