Create a scoped personal token
Create an Agent API token from the dashboard settings and keep it in your local environment or secret manager. Never put it in HTML, a repository, a post plan, or a model prompt.
SaveKit use case
A coding agent can generate a page, run local checks, and hand you a real preview URL through SaveKit's Agent API. The useful boundary is explicit: the agent can publish into your account, while you still review the content and decide where it should be shared.
A good fit for: AI coding workflows, repeatable demo generation, launch experiments, content prototypes, and teams that want a URL after each build.
Create an Agent API token from the dashboard settings and keep it in your local environment or secret manager. Never put it in HTML, a repository, a post plan, or a model prompt.
Have the agent send the reviewed HTML to POST /api/v1/publish with an Idempotency-Key. The API validates the content, applies your account limits, and returns the published URL and expiry.
Generate UTM links and channel-specific drafts from the returned URL. Review the title, claims, target community, and final link before using a platform's publish action.
Before you publish
These checks prevent the most common surprises after a folder becomes a public URL.
Common questions
Sign in, open Dashboard → Settings, and create a personal Agent API token. The full secret is shown once and can be revoked later.
No. It publishes the page to SaveKit. A distribution pack can prepare tracked links and drafts, but external posting should remain a deliberate, human-reviewed action.
Reuse the same Idempotency-Key when retrying the same logical publish. A different key represents a new publish and may create another page.
Upload the HTML or ZIP build, preview it, and get a link you can send to the next person who needs to see it.
Start publishing