What page data is

HTMLPUT page data is a per-page key–value store for structured JSON. Guests (or your own scripts) write rows; you read them in History. It is a locker for data on a static page—not a place to run Node.js.

Who it's for

• Anyone who needs structured data on a static HTML page (scores, RSVPs, check-ins, polls, custom app state, and more)
• Creators who were about to paste Express / require( into the paste box
• Users comparing “host HTML” with “also keep answers and state”

Steps

1. Know the product name — In the UI this is Page data (the History row action is often labeled Data). It is separate from file storage quota.
2. Start with a hosted page — New here? Create an account and host your first HTML page. Page data attaches to a page you already host.
3. Pick a path — Easiest: try the invitation under Page data (Store data with invitation templates). Custom HTML: use a page write-token (Wire page data into your HTML).
4. Review rows in History — Open the page’s Data dialog to list, export, hide, or rotate the write-token. Invitation deploys land under History → Uploads. Manage pages in History.
5. Watch the account key limit — New keys count toward a lifetime account quota (Free starts at 100). Soft-delete does not free quota.

Gotchas

• Page data does not execute server code. Paste static HTML (or reuse a demo), not Express apps.
• Guest writes need a page write-token, not your Agent API key. Never embed the API key in HTML. See also Agent API.
• Each value must serialize to ≤ 10KB UTF-8.