Agent API: Give Your AI a Way to Publish
A key that lets an agent publish, list, and manage hosted HTML pages directly — no browser, no copy-paste, no Turnstile.

Your AI writes HTML. Then what? You copy it out of the chat, paste it into a form, click publish, copy the link back. For one page, that is fine. For an agent that builds ten pages before lunch, it is a bottleneck.
The Agent API is HTMLPUT's answer: a key that lets an agent publish, list, and manage pages directly. No browser, no copy-paste, no Turnstile. Your agent calls the API, gets a share link back, and moves on.
What an agent can do with it
1. Publish a page from a string. POST your HTML to /api/v1/hosting/pages and get back a shareUrl and a pageId. One call, one live link. That is the whole flow.
2. Ship a multi-file site. POST a zip to /api/v1/hosting/bundle and the whole folder goes live as one site. Re-upload the same bundle later to update it in place. The link does not change.
3. Manage what is already live. List your pages, read one back, edit it, or delete it. The same key also manages Page Data on your own pages: enable storage, rotate the write token, review guest submissions.
How to turn it on
Get a key. Open Account and click Create. The full hp_live_… key shows once, so copy it then. Afterwards you only see a prefix. Revoke and Create again to replace it.
Call it. Send Authorization: Bearer hp_live_… to https://www.htmlput.com. No Turnstile. About 30 requests a minute. The full spec is at /openapi.json.
A minimal publish, with curl:
` curl -X POST https://www.htmlput.com/api/v1/hosting/pages \ -H "Authorization: Bearer hp_live_…" \ -H "Content-Type: application/json" \ -d '{"html": "<h1>Hello</h1>", "title": "Hello"}' `
The response carries data.shareUrl and data.pageId. Hand the share URL to whoever asked for the page.
What your plan allows
The API follows your plan, not a separate API tier. Free can paste, list, and read. Plus adds editing and deleting pasted pages. Pro and Ultra add zip and folder upload, re-upload, and deleting uploaded sites. Ultra raises the limits further and allows video in zips. Ask for something above your plan and you get a 403 with API_PLAN_REQUIRED and the plan you need.
The honest limits (read before you build)
- The key cannot touch billing, account deletion, or admin. It only manages your pages.
- Never put
hp_live_…in front-end HTML. Guest writes to Page Data use a page write token, not this key. The key stays on your server or in your agent. - The rate cap is about 30 requests a minute. If you are polling, back off instead of hammering it.
- Quota, size limits, and content review still apply. The API skips the browser, not the rules.
Page Data gave a static page a memory. The Agent API gives an agent a way to publish. Together they are the two halves of the same idea: a page that can both remember what visitors do and be created by the thing that wrote it. If your agent already writes HTML, give it a key and stop being the copy-paste step.


