📊 12 leads this week — https://pages.example.com/…Open it and you get a real page: sortable table, chart, readable on a phone.
Turning it on
Agent pages are only available if your ClawUp deployment has them configured — an operator sets the storage bucket and the domain pages are served from. If they are not configured, the endpoint returns503.
Self-hosting? See PAGES_* in .env.example.
From an agent
The agent needs a skill that renders and publishes pages — the reference one isrich-view.
Install it and the agent decides when a result deserves a page: roughly, more
than ~8 rows, or when you ask for “a table”, “a report”, or “a chart”. It will
not publish a page for a two-line answer.
So you do not trigger this directly. You ask the agent a question, and it
chooses the better format.
From the API
You can also publish a page yourself:pages:write scope — see Public API. It is a
separate scope on purpose: a key you hand to a reporting script can publish
pages without also being able to stop or delete your agents.
Send one complete HTML document. Anything the page needs — styles, scripts,
data — should be inside it.
Limits
Exceeding the rate returns
429; an oversized page returns 413.