---
title: "The one link: one address per business, every assistant"
slug: "the-one-link"
summary: "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."
canonicalUrl: "https://dev.powers.now/blog/the-one-link"
status: "published"
publishedAt: "2026-11-04T23:46:07.870Z"
updatedAt: "2026-11-04T23:46:07.870Z"
version: 3
author: "powers.now"
publisher: "powers.now"
language: "en"
trust:
  state: "verified_source"
  score: 0.9
topics:
  - "the one link"
  - "powers"
  - "agent-first presence"
entities:
  -
    id: "powers-now"
    type: "Organization"
    name: "powers.now"
    sameAs:
      - "https://powers.now/"
      - "https://dev.powers.now/llms.txt"
    description: "The one link for WebMCP and smart-element interfaces: one address per business."
  -
    id: "the-one-link"
    type: "Concept"
    name: "The one link"
    sameAs:
      - "https://dev.powers.now/add-it"
    description: "powers.now/<business> hosted, or the business's own domain carrying the same powers. One address per business; its powers live under it."
  -
    id: "chatgpt"
    type: "Product"
    name: "ChatGPT"
    sameAs:
      - "https://chatgpt.com/"
    description: "Where a person pastes the link, or adds the powers.now connector."
  -
    id: "claude"
    type: "Product"
    name: "Claude"
    sameAs:
      - "https://claude.ai/"
    description: "Where a person pastes the link, or adds the powers.now custom connector."
  -
    id: "webmcp"
    type: "Concept"
    name: "WebMCP"
    sameAs:
      - "https://developer.chrome.com/docs/ai/webmcp"
    description: "A proposed web standard for exposing structured tools for AI agents from a web page."
  -
    id: "cloudflare-for-saas"
    type: "Product"
    name: "Cloudflare for SaaS"
    sameAs:
      - "https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/"
    description: "Custom hostnames: how a business's own subdomain reaches powers.now by one CNAME with TLS terminated by us."
  -
    id: "llms-txt"
    type: "Concept"
    name: "llms.txt"
    sameAs:
      - "https://llmstxt.org/"
    description: "A proposed Markdown file at a site's root that tells language models what the site offers."
  -
    id: "lead-scheduler"
    type: "Product"
    name: "Lead Scheduler"
    sameAs:
      - "https://powers.now/book/"
    description: "powers.now's own live power and the first example of a business's link in use."
edges:
  -
    from: "powers-now"
    to: "the-one-link"
    relation: "is"
  -
    from: "the-one-link"
    to: "chatgpt"
    relation: "is pasted into"
  -
    from: "the-one-link"
    to: "claude"
    relation: "is pasted into"
  -
    from: "the-one-link"
    to: "cloudflare-for-saas"
    relation: "reaches a business's own subdomain through"
  -
    from: "the-one-link"
    to: "llms-txt"
    relation: "is declared on a business's domain in"
  -
    from: "the-one-link"
    to: "webmcp"
    relation: "carries smart elements that speak"
  -
    from: "lead-scheduler"
    to: "the-one-link"
    relation: "is the first example of"
claims:
  -
    id: "c1"
    text: "powers.now is the one link: a business signs up and gets one address, powers.now/<business> or its own domain, and every power it adds lives under it."
    citations:
      - "s-llms"
      - "s-home"
    status: "supported"
  -
    id: "c2"
    text: "The hosted link is free, and $19 a month per power when the business goes live."
    citations:
      - "s-pricing"
    status: "supported"
  -
    id: "c3"
    text: "At Business, $49 a month, all powers up to five run under the business's own subdomain by one CNAME."
    citations:
      - "s-pricing"
      - "s-add-it"
    status: "supported"
  -
    id: "c4"
    text: "A business's own subdomain reaches powers.now through Cloudflare for SaaS custom hostnames, which serve a customer's own domain through Cloudflare's network."
    citations:
      - "s-saas"
    status: "supported"
  -
    id: "c5"
    text: "llms.txt is a proposed Markdown file at a site's root that gives language models the site's content in their terms."
    citations:
      - "s-llmstxt"
    status: "supported"
  -
    id: "c6"
    text: "powers.now/book is powers.now's own live Lead Scheduler with a real calendar, real holds and real bookings."
    citations:
      - "s-book-llms"
    status: "supported"
  -
    id: "c7"
    text: "WebMCP is a proposed web standard for exposing structured tools to AI agents, still under active discussion and subject to change."
    citations:
      - "s-webmcp"
    status: "supported"
citations:
  -
    id: "s-home"
    url: "https://powers.now/"
    title: "powers.now"
    publisher: "powers.now"
    accessedAt: "2026-11-04"
  -
    id: "s-llms"
    url: "https://dev.powers.now/llms.txt"
    title: "powers.now, the guide for agents"
    publisher: "powers.now"
    accessedAt: "2026-11-04"
  -
    id: "s-pricing"
    url: "https://dev.powers.now/pricing"
    title: "What it costs"
    publisher: "powers.now"
    accessedAt: "2026-11-04"
  -
    id: "s-saas"
    url: "https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/"
    title: "Cloudflare for SaaS"
    publisher: "Cloudflare"
    accessedAt: "2026-11-04"
  -
    id: "s-llmstxt"
    url: "https://llmstxt.org/"
    title: "The /llms.txt file"
    publisher: "llmstxt.org"
    accessedAt: "2026-11-04"
  -
    id: "s-add-it"
    url: "https://dev.powers.now/add-it"
    title: "How you add it"
    publisher: "powers.now"
    accessedAt: "2026-11-04"
  -
    id: "s-book-llms"
    url: "https://powers.now/book/llms.txt"
    title: "Lead Scheduler, the guide for agents"
    publisher: "powers.now"
    accessedAt: "2026-11-04"
  -
    id: "s-webmcp"
    url: "https://developer.chrome.com/docs/ai/webmcp"
    title: "WebMCP"
    publisher: "Chrome for Developers"
    accessedAt: "2026-11-04"
questions:
  -
    question: "What is the one link?"
    answer: "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."
  -
    question: "Can I put my powers on my own domain?"
    answer: "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."
  -
    question: "Why not acme.com/powers as a path?"
    answer: "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."
takeaways:
  - "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."
  - "powers.now/book is the first example of a business's link in use, and it is ours."
actions:
  -
    type: "read"
    label: "Read how you add it"
    url: "https://dev.powers.now/add-it"
  -
    type: "book"
    label: "Book an intro call with powers.now"
    url: "https://powers.now/book/"
---

# 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.

## Our own link, in use

`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

- 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.
- 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.

## Sources

- [powers.now](https://powers.now/) — powers.now
- [powers.now, the guide for agents](https://dev.powers.now/llms.txt) — powers.now
- [What it costs](https://dev.powers.now/pricing) — powers.now
- [Cloudflare for SaaS](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/) — Cloudflare
- [The /llms.txt file](https://llmstxt.org/) — llmstxt.org
- [How you add it](https://dev.powers.now/add-it) — powers.now
- [Lead Scheduler, the guide for agents](https://powers.now/book/llms.txt) — powers.now
- [WebMCP](https://developer.chrome.com/docs/ai/webmcp) — Chrome for Developers