One keep is a file on your machine. The other is a URL in the world.
You asked for a Page. The agent drew one. Then you said save it — and two different jobs got treated as one.
Making is free. Keeping a public URL is the keyed step. The recipe is the JSON. The HTML is a snapshot of that recipe, frozen once.
Say: make a Page and save it so I can open it.
The agent drafts a pagespec, then calls `render_page` with a file path.
You get: an `.html` file you can open in a browser.
Also keep: the pagespec JSON next to it. That file is the Page. Without it you only have a frozen HTML snapshot — you cannot republish the same picture on purpose.
Nothing public. Nothing in My Pages.
Say: publish this Page / give me a public URL.
The agent calls `publish_page`.
You get:
You do: bookmark or share the URL. Later, call `my_pages` to find it again (News #9).
Free key: up to 5 alive, 7-day TTL, watermark. Paid: more slots, it stays. Unguessable is not private — anyone with the link sees the Page and the twin.
No key yet? Why take a free key — email, no card, 250/mo.
This lab Page is already in the world — URL, twin, hash on the page:
That is keep #2. The JSON in the twin is how you would keep #1 on disk.
1. “Save it” is two jobs. File on disk, or URL in the world. Say which.
2. Keep the JSON. The HTML is a snapshot. The JSON is the recipe.
3. A public URL needs a free key. Drawing on the machine does not.
1. Local `render_chart` / `render_page` need no key. Don’t nag for one before the first picture.
2. If they want a file they can open: `render_page` + `outputPath`, and write the pagespec JSON beside it.
3. If they want a URL: `publish_page`. Return url + jsonUrl + specHash. Don’t dump HTML.
4. To find it later: `my_pages`. Pages don’t rewrite — a new publish is a new URL.
5. Cold path: `get_started` → `news` → one render → key only when they ask to keep it in the world.
Draft on disk. Publish for a URL. Twin at .json.
Doors: Get started · News · Free key · Archive