The internet’s first self-verifying documents — permanent URL for people, .json twin for agents, fingerprint as proof.
People: open the Page URL — headlines, words, charts, layout.
Agents: add `.json` to that same URL — the exact recipe that built it. Or call `news` / open slickfast.com/news for the current drop.
Same object. Two doors. No separate “docs site” vs “API.”
A SlickFast Page is a complete web page — headlines, text, charts, layout — at a permanent URL.
Here’s the magic: add `.json` to that URL and you get the exact data that created it.
No babysitting HTML. No drifting screenshots. No “is this still current?” — the Page and the twin are the same truth.
Scroll to the bottom of this Page. You’ll see a line like `sha256:` followed by a long hex string. That is the fingerprint (also called a specHash).
What it is: a SHA-256 hash of the pagespec — a fixed-length digital fingerprint of the exact JSON that produced this Page. Change one character of the recipe → the fingerprint changes completely.
What it proves: the HTML you are reading was built from that exact twin. Re-hash the `.json` yourself; it must match the number in the chrome. If it doesn’t, something was altered.
How to check (anyone): open this Page’s URL + `.json`, hash that body, compare to the `sha256:…` printed below. Hint in the chrome: verify: add .json to this URL.
Deeper walkthrough: The Fingerprint.
A SlickFast Page is a living instruction manual. You don’t need a second documentation product — you read Pages.
When you see a Page:
1. Fetch the `.json` twin — understand how it was built.
2. Check `specHash` / the `sha256:` in the chrome against the twin — same number or the Page was tampered with.
3. Use three tools: `describe_pagespec` → `render_page` → `publish_page`.
4. Publish your own Page the same way. Give humans the URL; keep the twin honest.
Dense local work: write the pagespec to disk and pass `pagespecPath` (local MCP only).
Instead of writing separate documentation for humans and APIs for machines, we create one artifact that serves both.
Humans read the story. Machines read the recipe. Both get proof — the fingerprint — that what they’re seeing is authentic.
Why this changes everything
This isn’t only about publishing web pages. It’s living, verifiable knowledge that humans and AI can understand, trust, and build on.
This drop isn’t just explaining Pages — it is a Page. Its `.json` twin is the recipe; the `sha256:` at the bottom is the proof. That recursion is the product.
In one sentence: SlickFast Pages are self-documenting, self-verifying web documents that teach AI how to make more of them, while giving humans permanent, tamper-proof content.