Download a built page as files
export_pageUses no credits. Packages a finished page as a zip that runs on any static host: index.html with every image it uses pulled into assets/, plus a README and metadata.json. Returns a download link. This is the one for a user who wants the files. share_page is the one for a user who wants something to look at. It also returns implementation_prompt: step by step instructions for putting this page live on the user's own site. Postclick hosts a built page only for a live test, which the user starts in the app, so this is how a page goes live for good. If you have access to their site, you can carry those steps out yourself; otherwise hand the prompt to whoever does. Pass platform when you know where the site lives, because the steps for WordPress and for Webflow are genuinely different. Ask if you do not know. The builder variants stop at a draft and never publish without the user confirming.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"build_run_id": "<build_run_id>"
},
"name": "export_page"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| platform | No | Where the page goes live. "host" is the simplest for any site: the page on its own subdomain (go.example.com) at a web host such as Hostinger, Netlify or Vercel, and the zip's CLAUDE.md holds every step. Omit if unknown and the instructions will assume nothing. | |
| build_run_id | Yes |