# Deploy with your AI agent

> Your agent puts a site online as a private preview, from its files or a connected repository, and follows each step until the preview is ready.

## What your agent can do

- Put a static site online as a private preview from its files or a ZIP or tar archive, with no repository.
- Deploy a commit of a GitHub repository connected in the console.
- Run and follow each step (build, scan, preview) until the preview is ready or failed.
- Take a preview offline.
- Read production (plan, usage, domains, served release) and compare the production plans.

## Ask your agent

Paste a request like these in your AI once it is connected. It calls the tools in this order.

| You ask | Your agent calls |
|---|---|
| “Put this site online on Galon and give me the preview link.” | `get_status` → `deploy_archive` → `advance_deploy` |
| “Deploy commit 3f2a… of acme/site to a preview.” | `get_status` → `start_deploy` → `advance_deploy` |
| “Is my last deploy ready? Show me its steps.” | `get_deploy` |
| “Take that preview offline.” | `delete_preview` |
| “What would production on my own domain cost?” | `list_plans` |

## Tools and routes

Every tool is a call to the REST route next to it, with the same permissions, limits and idempotency. `tools/list` shows only the tools your connection can call.

| Tool | What it does | Scope | Same through the REST API |
|---|---|---|---|
| `get_status` | Project, environment, sending mode and the services open to this key. | none | `GET /v1/tools` |
| `deploy_archive` | Deploy a static site to a preview from its files or a ZIP or tar archive. | `deploy:create` | `POST /v1/deploy/archives` |
| `start_deploy` | Start deploying a commit of a connected repository to a preview. | `deploy:create` | `POST /v1/deploy/journeys` |
| `advance_deploy` | Run the next step of a deploy. | `deploy:create` | `POST /v1/deploy/journeys/{journey_id}/resume` |
| `get_deploy` | Read a deploy: steps, status, preview address. | `job:read` | `GET /v1/deploy/journeys/{journey_id}` |
| `delete_preview` | Remove the preview of a deploy: its address stops answering (410). | `deploy:create` | `DELETE /v1/deploy/journeys/{journey_id}/preview` |
| `get_production` | Read this project's production: plan, usage, domains, release. | `job:read` | `GET /v1/deploy/production/status` |
| `list_plans` | List the production plans with what each includes and the overage prices. | `job:read` | `GET /v1/deploy/production/plans` |

## Limits, free tier and pricing

Read from the platform code each time this page is served.

| Limit | Value |
|---|---|
| Free preview deploys per account and UTC day | **10** |
| Free preview builds running at once per account (the next one waits) | **1** |
| Builds running at once on the shared builders (first come, first served) | **2** |
| Dependency install time | **10 min** |
| Build time | **15 min** |
| Total time of a build | **20 min** |
| CPU per build | **2 vCPU** |
| Memory per build | **3 GiB** |
| Workspace per build (counted in memory) | **1,536 MiB** |
| Processes per build | **512** |
| Dependency cache per project (emptied beyond) | **1 GiB** |
| Build log lines kept | **20,000** |
| Archive uploaded | **25 MiB** |
| Files per archive | **512** |
| One file in an archive | **2 MiB** |
| Content of an archive, in total | **10 MiB** |

Preview deploys are free (within the limits above). Production needs a plan, paid from your prepaid balance every 30 days, in USD:

| Plan | Price | Domains | Traffic | Builds |
|---|---|---|---|---|
| `site` | 3.00 USD | 1 | 100 GB | 300 |
| `pro` | 15.00 USD | 10 | 1000 GB | unlimited |

Usage beyond a plan is billed to your balance as you go: 0.11 USD per GB and 0.011 USD per build (USD). Your site stays online; without balance the amount waits.

`GET /v1/deploy/production/plans` returns this same grid.

Your agent reads the current prices with `get_pricing` and the spending limits with `get_limits`.

## Good to know

- Previews are made in a **test** project; a connection to a live project sees no preview.
- A preview is private: it answers only with its `preview_access_token`, shown once (in a browser, give it as the password when the page asks). It ends at `expires_at`, at most 7 days ahead.
- A folder or an archive is served as a static site, with `index.html` at its root.
- Production on your own domain needs a **live** project and a production plan.
- With a sign-in connection, the agent asks you to approve a production plan or a promotion with `request_approval`; you approve it in the console, and the agent follows it with `get_approval`.

## Next

- [Deploy in 1 minute with your AI agent](/cloud/docs/agents/deploy-in-1-minute)
- [Full service documentation](/cloud/docs/services/deploy)
- [Connect your AI](/cloud/docs/ai-assistants)
- [All capabilities](/cloud/docs/agents)
- [API reference](/cloud/docs/api)
