Agent HTTP & CLI instructions · OpenAPI · Agent discovery

Documentation

Publish a
static project.

Use your coding agent or the standalone CLI to publish static files. Temporary projects do not require an account.

Publish your first project

With a coding agent

Give your agent these instructions. It must be able to read URLs and run shell commands.

Read https://agivo.app/skill.md. Build the static output for this project, check for secrets, and publish it to Agivo. Return the live URL and the exact claim URL.

From your terminal

Requires Node.js 20 or later. Download the CLI, then point it at your static output folder. No npm package installation is required.

curl -fsSL https://agivo.app/agivo.mjs -o /tmp/agivo.mjs
node /tmp/agivo.mjs publish ./dist

Replace ./dist with your output directory. Next.js static exports commonly use ./out. Build your project first: Agivo serves files; it does not run your build or backend.

Add --slug my-project to request a project name, or --spa for client-side routing. If there is no index.html, Agivo can display a file viewer.

Claim your project

Temporary projects expire after 24 hours. The CLI returns a public URL and a private claim URL. Open the full claim URL, log in or create an account, then claim the project.

Keep the claim link private. Anyone with the link can claim the project. Share only the public project URL.

Publish directly to your account

Create a named API token in the dashboard. Store it in your agent’s environment as AGIVO_TOKEN. The CLI reads it automatically. Never include an API token in a public prompt or repository.

export AGIVO_URL="https://agivo.app"
# Set AGIVO_TOKEN through your environment or secret manager.
node /tmp/agivo.mjs publish ./dist --slug my-project

Update or restore a deployment

Publish with the same slug and your account token. The project URL stays the same. Each completed publish creates a saved deployment.

node /tmp/agivo.mjs publish ./dist --slug my-project

In the dashboard, open Deployment history and select Restore deployment. Restoring changes what visitors see immediately without deleting other deployments.

node /tmp/agivo.mjs rollback --slug my-project --deployment DEPLOYMENT_ID

Rollback requires AGIVO_TOKEN. Copy the deployment ID from your project’s version history.

API reference

The CLI uses the staged publishing API. See the public agent skill and CLI source for working request examples.

POST /api/v1/publish

Create a manifest. Returns upload URLs, a finalize capability, and anonymous claim details where applicable.

PUT [returned upload URL]

Upload each requested file as bytes with its content type. Use only URLs returned by the API.

POST /api/v1/publish/:slug/finalize

Send {"versionId":"…"} and the returned capability in x-agivo-finalize. Authenticated requests also need the creator’s bearer token.

GET /api/projects

List the authenticated account’s accessible projects.

GET /api/projects/:slug/deployments

List saved deployments and identify the active deployment.

POST /api/rollback/:slug

Send {"deploymentId":"…"} to restore a deployment. Requires edit access.

Limits and safety

Default upload limit: 20 MB decoded content and 1,000 files per deployment. Static files only: HTML, CSS, browser JavaScript, and prebuilt static exports. Build your project before uploading. Agivo does not run Node.js or Python servers, server-side rendering, API backends, databases, or background jobs. Browser code may call your separately hosted APIs; never put server secrets in uploaded files.

Review the output folder before publishing. Exclude secrets, credentials, private keys, databases, and source maps containing sensitive information. Anonymous sites are public unless you explicitly configure password access.

Published projects use an Agivo subdomain, such as my-project.agivo.app.