What this key has published — as a Page you can open, share, and verify.
You already publish Pages. You forget the URLs.
`my_pages` asks the API what this key has shipped, then turns that list into one more Page — titles, status, dates, links, twins.
Share that inventory URL with a teammate. An agent fetches the twin. The fingerprint on the Page is the proof of this list, frozen at publish time.
Re-run later → new history slug. Pages don’t rewrite themselves.
Below is the shape of a history Page — fake titles, real pattern. Your run uses your publishes.
_Showing newest rows (cap 40). Filter with `status` or `days`._
1. Free key at slickfast.com — put `SLICKFAST_API_KEY` in MCP config.
2. Ask the agent: call `my_pages` (default publishes). Or `my_pages({ publish: false })` for a local HTML peek.
3. Optional: `status: "active"` · `days: 30` · `ttlDays` on free tier (clamps to 7).
4. Open the returned pages. URL. Add `.json` for the twin.
DELETE still hits the API (`DELETE /pages/{slug}`) — human face is `pages.`; revoke stays on `api.`.
1. Inventory is a Page — not a settings screen you can’t share.
2. Frozen on purpose — yesterday’s list stays yesterday’s list; re-run for today.
3. Unguessable ≠ private — anyone with the history URL sees what that key published.
1. Key required — same as `publish_page`. No key → send them to slickfast.com.
2. Default `publish:true` → return url + jsonUrl + specHash. Don’t dump the HTML.
3. History links use `https://pages.slickfast.com/s/{slug}` (+ `.json`). API list/delete stay on `api.`.
4. Cold path: `get_started` → `news` → `my_pages` when they ask what they’ve shipped.
Call `my_pages`. Your publish history becomes a Page — twin included.
Doors: Get started · News · Free key · Archive