November 4, 2026 · 2 min read · verified source

The one link: one address per business, every assistant

A 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

powers.now is the one link for every assistant your customers use. A business signs up and gets one address: powers.now/<business>, or its own domain. Every power it adds lives under that address. There is never one link per power as the primary address, because a business is one thing and its customers ask for it by name.

Two promises, in this order on every surface. For the business: signing up is easy. Claim the link, pick a power, it is live. For their users: engaging is easier. One link, any assistant, nothing installed, the card does the rest.

Three layers, shipped in this order

Hosted. powers.now/<business>, claimed at sign-up and live at once. Free, and $19 a month per power when you go live.

Your own subdomain. powers.<business>.com, one CNAME to powers.now. We terminate TLS through Cloudflare for SaaS custom hostnames, and the same pages run on the same engine. All powers, up to five, under your own subdomain, at Business, $49 a month.

Your own pages. Smart elements on <business>.com itself, plus a line in your llms.txt and a /.well-known/power.json on your domain. One script tag or one element per page. Your domain declares your powers to every agent that reads it, on your authority, not ours.

The hosted link and the subdomain are the on-ramp. The own-pages layer is the product, because an agent reading acme.com then finds Acme actionable on Acme's own page.

Why not acme.com/powers

A path on your domain needs a proxy you control. Most businesses cannot add one. Every business can add a CNAME and a line to a text file. So the path is offered only where a business already runs a proxy, and the subdomain is the default.

How the element knows the business

The engine is one shared path per power, the way a payment link is one shared checkout. The business is context, never a second copy of the code. The power resolves the business from the host the request arrived on, then from the business segment of a hosted link, then from a signed short code carried in a link an agent learned from the business's llms.txt, then from the business argument an assistant passes because it knows who the person is talking about. With none of these, the default is powers.now itself.

The person on the other side is known the same way: one powers.now sign-in, remembered across every business's powers.

powers.now/book is the first example of a business's link in use. It is our own Lead Scheduler: a real calendar, real holds, real bookings. It stays the destination for our own intro calls, and it is the bare-path default when no business is named.

What WebMCP adds

WebMCP is a proposed web standard for exposing structured tools to AI agents from a page. It is the reason the own-pages layer exists: a smart element on your page declares its tools to the agent in the browser, and the same element renders the card. The standard is under active discussion, so we use it where it is present and fall back where it is not.

Takeaways

  1. One address per business; its powers live under it. Never one link per power as the primary address.
  2. Three layers in order: hosted powers.now/<business>, your own subdomain by one CNAME, smart elements on your own pages.
  3. 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.
  4. powers.now/book is the first example of a business's link in use, and it is ours.

Questions answered

What is the one link?

The single address a business gets when it signs up with powers.now: powers.now/<business> hosted, or the business's own domain carrying the same powers. Every power the business adds lives under it.

Can I put my powers on my own domain?

Yes. At Business, one CNAME gives you powers.<business>.com with the same pages on the same engine. On your own pages, a smart element plus a line in your llms.txt and a /.well-known/power.json declare your powers on your own domain.

Why not acme.com/powers as a path?

A path on your domain needs a proxy you control, which most businesses do not run. Every business can add a CNAME and a line to a text file, so the subdomain is the default and the path is offered only where a proxy already exists.

What this article is about

Sources

  1. powers.now, powers.now (read 2026-11-04)The one link for every assistant your customers use.
  2. powers.now, the guide for agents, powers.now (read 2026-11-04)powers.now is the one link for WebMCP and smart-element interfaces: a business signs up and gets one address, powers.now/<business> or its own domain, and every power it adds lives under it.
  3. What it costs, powers.now (read 2026-11-04)$19 a month per power when you go live. Business $49 a month. All powers, up to five, under your own subdomain by one CNAME.
  4. Cloudflare for SaaS, Cloudflare (read 2026-11-04)Cloudflare for SaaS allows you to extend the security and performance benefits of Cloudflare's network to your customers via their own custom or vanity domains.
  5. The /llms.txt file, llmstxt.org (read 2026-11-04)We propose adding a /llms.txt markdown file to websites to provide LLM-friendly content.
  6. How you add it, powers.now (read 2026-11-04)Claim the link, pick a power, it is live; where the link lives (hosted powers.now/<business>, your own subdomain by one CNAME, your own pages).
  7. Lead Scheduler, the guide for agents, powers.now (read 2026-11-04)Live instance. This is powers.now's own Lead Scheduler: a real calendar, real holds, real bookings, real confirmation emails.
  8. WebMCP, Chrome for Developers (read 2026-11-04)WebMCP is a proposed web standard to help you build and expose structured tools for AI agents. WebMCP is under active discussion and subject to change in the future.

Updated November 4, 2026Version 3MarkdownEntry