DemoPage

Use this when the user wants to rerun readiness on already-approved pages. It starts a private check job and does not approve or publish candidates. Read the result later with demopage_status.

demopage_check_pages

Use this when the user asks for their existing demo link or embed snippet. This does not create or publish a demo.

demopage_get_link

Use this after mapping pages from a repository or documentation and the user wants to add them as unpublished candidates, up to 100 per call. Each page needs a canonical query-free https address on the product's domain, visible proof text, and a description. Re-importing changed fields corrects the candidate and holds it for approval again. This never publishes a page.

demopage_import_pages

Use this when the user wants to review their product pages, approval state, or readiness failures. This does not change any page.

demopage_list_pages

Use this only after showing the candidate list and receiving the user's explicit choice of page ids. Approving publishes those pages to the user's public demo (and turns the link on before first publication); holding removes them from demos. Readiness checks still keep failed pages out.

demopage_approve_pages

Use this when the signed-in user asks about the last 30 days of their demo performance, buyer questions, readiness failures, or latest leads. Lead data stays scoped to this connected account.

demopage_results

Use this when the user wants their DemoPage setup status, page counts, readiness result, demo link, or next setup step.

demopage_status

Use this before first publication when the user asks DemoPage to reread their public product website. It starts a site-reading job and does not publish pages.

demopage_read_site