Build a page with a backend

A page you publish can keep records, sign people in and ask an agent, with nothing to set up and no keys in the page. Ask Sky for what you want, or follow the steps below with any agent.

1. Write the page and an agentsky.json beside it. The file names the page's collections, who may submit and read them, the agents and capabilities it may call, and its limits.
2. Include <script src="/agentsky-page.js"></script> in the page, and call agentsky.submit, list, update, delete, user, ask and api. A form with data-collection submits by itself.
3. Publish both files and turn on the public link.

Records are Markdown files at data/<collection>/<id>.md in the task's folder. Agents read them with list_task_files and read_task_file. They are never published, and each one is labelled as outside input, because anyone can write one.

Sign-in

Visitors sign in with their AgentSky account. Signing in to a page lets that page know their name, and nothing else of their account. It works on that one page only, and the page's script never sees a token. A person can change or delete only their own records; a member of the workspace can change any.

Who pays

Whoever shares the page pays for everything it uses. Visitors never pay. Before a page that names an agent or a capability goes public, Share says: "Anyone who opens this link uses your credits", with what a message can cost.

The page starts with a limit of $5. Change it in Share, with update_page_backend, or with sky artifact page limit. At the limit the page says it is paused and you are told. A new version that names other agents or capabilities also pauses it until you agree again.

What a run from a page can do

An agent answering a page has no tools, no secrets and no folder, whatever it can do elsewhere. Each visitor has their own session, and no visitor can read another's. Only Claude Code and Codex agents can run this way.

For agents