AMP builds the page; a filter still decides who sees it
AMP (amp.pr) is an AI website builder: describe your site in a sentence, or start from a template, and it writes a complete site you publish in one click. It is unrelated to Google's older page-speed format that shares the same short name. A well-built page still passes through the same work or office filter as any other site.
If you want a page for an AI project live in minutes, amp.pr is a website builder, not a speed protocol borrowing a similar name. This is what it actually does, and how that fits with the fact that a network filter works by category, not by which tool built the page.
Related tools
On this page
What AMP is, and what it is not
amp.pr is an AI website builder called AMP. You describe the site in one sentence, or start from a template such as a restaurant, a law firm, or a portfolio, and it produces a complete modern site in minutes, which you then refine by chatting with it. This AMP is a different product from Google's older page-speed markup format that used the same three letters; the name is a coincidence, and there is no shared code, caching layer, or standard between the two.
Publishing: one click, a free subdomain
Once the draft looks right, you publish in one click. The default address is yourname.amp.pr, with free SSL included. If you already own a domain, you can connect it instead. Building does not require an account; you only need one to publish. amp.pr does not publish page-speed numbers or prices on its own site, so this article does not invent any.
Why a filter does not read the builder's name
A work or office filter matches destinations against category lists bought from a vendor, and the decision is made on the category a site falls into, not on the software behind it. A page built with AMP, one built by hand, and one built with any other tool are judged the same way by that list. Nothing about amp.pr's output changes the category a filter vendor assigns, so publishing here is not a route around a block.
What a separate address is actually good for
The real, narrower benefit: a new project usually needs a page of its own, apart from whatever domain your main tool sits on. A subdomain under amp.pr, or your own domain connected to it, gives that project an address you control within minutes. That is useful for getting something live fast. It is not the same as a guarantee that the page reaches every network it is opened from.
Getting started
Open amp.pr and describe the project in one sentence, or pick a template close to what you need. Refine the layout and copy by chatting with the builder instead of editing code. When it looks right, publish to the free subdomain or point your own domain at it. Treat the result as an ordinary website afterward: reachable wherever nothing blocks its category, and no more resistant to a block than any other page.