Build a website with AI, and know when you have outgrown one
Build a website with AI whenever the content is written once and stays true; the moment a page has to show something that changes while a visitor is reading it, it has stopped being a website and needs a live data source rather than a better layout.
Building a website with AI works well and gets better every few months. Describe the pages, the model writes them, and you have something presentable in an afternoon.
Start from a working app
HyperBoard: Crypto Market Dashboard
prices, funding rates, open interest and liquidity across crypto perpetual markets, in three live tabs.
Open the template
What a website builder is genuinely good at
Structure, copy, layout and images, which together are most of what a marketing site, a portfolio or a documentation front page needs. Getting all four to a decent standard used to take a designer and a week. It now takes a description and an afternoon, and the result is usually better than what a non-designer would have produced by hand.
The line, stated plainly
Content that was true when written stays on a website. Content that has to be true right now belongs in an app. A pricing page is a website. A page showing the current price of something is an app wearing a website's clothes, and it will behave like one the first time the source is unreachable.
Why the failure is quiet
Nothing errors. The page renders, the number appears, and it is simply old. There is no visual difference between a figure read four seconds ago and one baked in four weeks ago, so nobody notices until somebody acts on it. That is the entire reason this distinction is worth drawing before you build rather than after.
What to do if you are on the wrong side of it
You do not need to abandon the site. You need one part of it to read a source at request time, and to say what it does when that source is down. That is a small amount of work and it is the difference between a page people can trust and a page that is right most of the time.
Live, right now, on this page
| Market | Price | Funding | 24h volume |
|---|---|---|---|
| BTC | $83,548.50 | 0.0013% | $130,669,154 |
| ETH | $2,531.55 | 0.0013% | $117,840,506 |
| SOL | $111.02 | 0.0013% | $32,810,205 |
| HYPE | $86.07 | 0.0013% | $1,200,748 |
Read from a live market as this page rendered, through a public endpoint that needs no key. Read at 2026-10-11 21:09 UTC; accurate as of that time and not afterwards.
Start from a working app
Open, change it, publish your own
HyperViz
seven live views of Hyperliquid markets, from a liquidity heatmap to liquidation zones and a funding radar.
Open the template
Working templates built around what this page covers. Open one, change it, and publish your own.
- HyperBoard: Crypto Market Dashboard
prices, funding rates, open interest and liquidity across crypto perpetual markets, in three live tabs.
- OddsBoard
a live visualiser of Polymarket and Kalshi prediction markets, in six views.
- HyperViz
seven live views of Hyperliquid markets, from a liquidity heatmap to liquidation zones and a funding radar.
Common questions
What is an AI website builder genuinely good at?
Structure, copy, layout and images, which together are most of what a marketing site, a portfolio or a documentation front page needs. Getting all four to a decent standard now takes a description and an afternoon.
What belongs on a website and what belongs in an app?
Content that was true when written stays on a website. Content that has to be true right now belongs in an app. A pricing page is a website, while a page showing the current price of something is an app wearing a website's clothes.
Do I have to rebuild my site to show live data?
No. One part of it needs to read a source at request time and say what it does when that source is down. That is a small amount of work, and it is the difference between a page people can trust and one that is right most of the time.
Related reading
All guides · Live market pages · Components · Make Mithril a preferred source in Google