Developers
Overview
The Frontpage CLI lets you sync site files, drive the editor agent, manage content, and observe analytics, with staging on your subdomain before publish.
What this is
Frontpage sites are Astro projects managed by the platform. The public CLI
(frontpage-host on npm, binary frontpage) is the supported way to automate them without
a GitHub remote or cross-tenant access. The public CLI and People CRM are included on
Scale (and Enterprise). Site-scoped commands return 403 on lower tiers.
frontpage sites still lists sites the key owner belongs to. Site targeting is always by
subdomain (for example asimov-press), never by custom domain.
What you can do
| Capability | Commands | Guide |
|---|---|---|
| Authenticate & link a site | login, whoami, sites, use, doctor | Authentication |
| Sync allowlisted files | pull, push, diff, ls, cat, search | File sync |
| Build pages correctly | Astro contract via file sync + help site-building | Site building |
| Editor agent runs | prompt, runs, deploy wait | Agent runs |
| Content APIs | seo, redirects, articles, media, inbox, fonts, tokens, modules, extensions, settings, edit | Content & settings |
| People CRM | people list|get|add|set|note|rm-note|follow-up|hide|unhide | People CRM |
| Store | shop items|variants|categories|settings|orders|payments|connect|status|disconnect | Store |
| Modules | modules <key>, list, docs, request-setup, enable, config; form destinations; Google reviews; typed get/set; Stripe/Square connect | Modules |
| Observe | analytics, usage, pages | Analytics & usage |
| History | history, revert | History & revert |
| Publish | publish, unpublish | Staging vs production |
| Limits & errors | HTTP 429 / exit 2, envelopes | Rate limits, Errors |
Where to start
Quickstart
Install, login, first pull
Agent quickstart
Paste-ready agent brief
Staging vs production
Subdomain preview vs publish
Isolation & keys
Site fence and key scope
Rate limits
Classes, windows, Retry-After
Authentication
API keys and env vars
File sync
Pull, push, CAS, allowlist
Site building
Astro contract, tokens, modules
The one rule that prevents outages
https://<subdomain>.frontpage.host is staging.
Push, prompt, and edit update staging. Production (your custom domain) only changes when someone runs
frontpage publish.
Coding agents must not publish or unpublish unless the customer explicitly asks, or the customer built a workflow that requires autonomous publishing. Default: finish on staging and ask the human to review.
Package vs binary
| Thing | Value |
|---|---|
| npm package | frontpage-host |
| Binary / command | frontpage |
| Wrong package | Do not install npm frontpage (unrelated) |
| Node | ≥ 20 |
| Agent manual in the package | AGENTS.md, llms.txt |
In-product entry point
In the Frontpage editor, open the profile menu → Developers to create API keys and copy a short agent prompt. Key creation is limited to 5 per user per 24 hours (RL-MINT). That panel links here for the full guide.
Introspection
The CLI is self-describing. Prefer these over guessing:
frontpage help
frontpage help --json
frontpage help sync
frontpage help agent
frontpage help content
frontpage help people
frontpage help store
frontpage help exit-codes
frontpage push --help