Connect your agent to publish a report, guide, or supported app. You control who can open each page.
pagesend publishes finished static content. Build with your usual tools first; the hosting service does not run package installs, customer servers, or arbitrary build commands.
Choose your publishing workflow
- Connect ChatGPT or Claude Code to publish from your agent.
- Share an AI-generated report with the right audience.
- Publish an HTML page in your browser from a finished file or static output folder.
- Review search visibility before making a public page discoverable.
Compatible bundles
Include index.html and relative local assets. Nested static pages use clean URLs. A supported SPA declares its routes and uses the pagesend memory-router adapter in the isolated frame.
Upload a finished HTML file, a ZIP, or a folder. Include index.html at the root. The service accepts up to 16 MiB of uploaded bytes, 32 MiB after extraction, 256 files, and 4 MiB per file. It checks actual bytes during transfer and extraction. Links, secrets, dependency files and server projects are rejected.
Publish in the browser
- Open your workspace and start a new page.
- Select finished files, review routing, and upload for validation.
- Preview the ready files. A ready draft is still unpublished.
- Confirm the audience and publish. Public access needs an explicit confirmation.
An update keeps the page’s link. If someone else publishes or changes permissions while you are working, refresh the current state and review the change before publishing again. A conflict keeps the current live publication in place.
Private by default
New pages are private. Publishing files and changing the audience are separate actions. Team membership does not grant access to another person’s private page.
Saved data
Collections belong to a stable page identity. Updating files or rolling back a revision keeps records intact. Viewer collections are specific to the signed-in viewer; submission collections do not expose other responses.
Content isolation
Uploaded code runs in a sandbox on a separate content origin. A page can read data you explicitly grant to that page’s code. Previously downloaded public content cannot be recalled by making a page private.
Interactive pages
Page code runs in a scripts-only sandbox. Native form submission, popups, top-level navigation, cross-origin requests, service workers, and browser History API routing are unavailable. Use explicit button click handlers with the pagesend bridge for saved data. An Enter-key handler can call the same save function. Declared SPA routes use pagesend.navigate and pagesend.subscribe.
await pagesend.ready;
// Use the current ETag to update an existing record.
const saved = await pagesend.data.put(
"notes", "draft", { text: "Hello" }, null, 1
);
await pagesend.setSaveStatus(false);
await pagesend.setReloadReadiness(true);The collection must already allow this action and schema. Use the ETag returned by a read or save for subsequent updates. Keep your local draft when a save conflicts. Mark reload readiness only after your page is ready to restore its saved state safely.
Use the API
The web application and connected agents use the same publishing and permission services. The OpenAPI description documents available endpoints, request formats, and error responses. Use the app and MCP origins configured by your service operator; deployment addresses are configured separately.
Agent access requires a registered OAuth client and an approved workspace connection. Keep account cookies and access tokens out of published files. For a supported publishing workflow, start with the connection instructions below.
Connections
Open Agents, choose Claude Code or ChatGPT, and follow the short connection steps. You can also give your agent the Markdown connection guide to follow. It contains this deployment’s configured server address and troubleshooting instructions.
Your client starts the connection. Sign in with pagesend in your browser, choose a workspace, and review the permissions before approving. Return to the client and confirm a tool call succeeds. Automatic registration depends on deployment configuration. Review or disconnect existing clients from Agents; reconnect from the client when you need new consent.
A local folder or file path requires the supported local byte-transfer helper (Python 3.12+, macOS or Linux). A remote server cannot read that path. Unverified remote download links fail closed. Build your app locally, then publish the finished static output. Never upload keys or configuration secrets.
Files, recovery and limits
Versions lets the page owner review removal of unused file bytes under the configured retention policy. Removal preserves records and version history. Live files and referenced revisions remain protected. Deleted pages lose access immediately; eligible recovery creates a private page. Once physical removal starts, recovery is unavailable.
Usage shows actual workspace capacity to its owner and administrators. Unfinished or uncertain transfers can keep capacity reserved. Refresh their status before retrying. If a limit or unresolved storage operation persists, contact your service operator; retrying cannot increase the configured allowance.
Manage connections · Workspace usage · Data and privacy · Licenses & notices
Open your pages