Publish from your own agent with one HTTP call
Your agent makes files every day. POST them to cloud71 with a token and get back a live, shareable https link — from any language, or any tool that can make an HTTP request.
https://app.cloud71.host/api/cli/deploy$ curl -X POST https://app.cloud71.host/api/cli/deploy
-H "x-c71-filename: digest.html"
-H "x-c71-site: daily-digest"
--data-binary @digest.html
✓ "url": "https://daily-digest.cloud71.site"
Agents and scheduled jobs generate output that nobody sees: HTML reports, daily digests, generated landing pages, PDFs. Putting it in a storage bucket means setting up public access, content types, and a domain yourself. cloud71 turns it into one request — send the bytes, name the file, and the response contains the public URL.
If your agent framework speaks MCP, point it at https://mcp.cloud71.host/mcp and it gets deploy_files, list_sites, read_site, and manage_site as tools. If it doesn't, the REST API does the same work — deploy, list, read, and manage — authenticated with a token from your dashboard. Either way, every site gets the global edge, SSL, analytics, and controls like passwords and expiring links.
- 1
Create a token
Generate one at app.cloud71.host/dashboard/tokens. It's shown once, so store it as a secret.
- 2
POST your output
Send the raw bytes to /api/cli/deploy with an x-c71-filename header. Add x-c71-site to update the same site on every run.
- 3
Use the URL
The JSON response includes the live url. Post it to a chat, an email, or the next step of your workflow.
Publish a page (and update it on every run)
curl -X POST https://app.cloud71.host/api/cli/deploy \
-H "Authorization: Bearer $C71_TOKEN" \
-H "Content-Type: application/octet-stream" \
-H "x-c71-filename: index.html" \
-H "x-c71-site: daily-digest" \
--data-binary @index.htmlA password-protected link that expires in 7 days (Starter+)
curl -X POST https://app.cloud71.host/api/cli/deploy \
-H "Authorization: Bearer $C71_TOKEN" \
-H "Content-Type: application/octet-stream" \
-H "x-c71-filename: report.html" \
-H "x-c71-title: Q3 client report" \
-H "x-c71-password: $REPORT_PASSWORD" \
-H "x-c71-ttl: 604800" \
--data-binary @report.htmlEverything the link needs
One call, one link
A single POST publishes an HTML page, a PDF, or a zipped site and returns its URL.
Update in place
Send x-c71-site and each run replaces that site's content — the same link every time.
Expiring links
Set x-c71-ttl to seconds from now or an ISO date, and the link expires after it.
Passwords in the same call
x-c71-password puts the site behind a password as it publishes (Starter and up).
Organized at volume
Title and tag each deploy, then list everything back from /api/cli/sites.
MCP or REST
Agents that speak MCP get four tools; everything else uses plain HTTPS.
Common questions
Send them to the cloud71 API. One POST with the file's bytes and a filename header returns a public https URL — no bucket policies, content types, or DNS to manage.
POST the file to https://app.cloud71.host/api/cli/deploy with an Authorization: Bearer header and x-c71-filename: index.html. The JSON response includes the live url. ZIP a folder to publish a whole site.
Yes. Add x-c71-ttl with seconds from now (86400 is one day) or an ISO 8601 date, and the link expires after that time. Expired sites are removed by a scheduled sweep, not at the exact second.
If it can send an HTTP POST with custom headers and a binary body, yes. There's no SDK to install.
Static content: a single HTML page, a zipped site, a PDF, images, video, or Office documents. ZIPs are unpacked and served as a site; other single files get a built-in viewer page. There's no server-side runtime.
Free: 1 site, which it can update as often as it likes. Starter: 5. Pro and Business: unlimited — Pro at $19/mo is the plan for agents that publish all day.
Use MCP when a model decides when to publish — Claude, ChatGPT, or an agent framework with MCP support. Use the REST API from scripts, cron jobs, and CI, where your code makes the call.
Store it as a secret in your agent's environment, never in a prompt or a repository. You can revoke any token from your dashboard at any time.