Deploy your first agent | Astro AI

Deploying takes a blueprint from the registry and runs it as a live agent on the Astropods platform. The agent gets a web endpoint and optional integrations (Slack, etc.) based on the adapter you choose.

Requires a blueprint in your account. See Your first blueprint to push one.

Deploy a blueprint

$ ast blueprint deploy <name>

<name> is the blueprint name (as shown in ast blueprint list). By default the agent is accessible via a web interface with authentication enabled.

Give the deployment a custom display name:

$ ast blueprint deploy my-agent --name "My Production Agent"

Supply required variables

Most agents require API keys or credentials at deploy time. Pass them inline:

$ ast blueprint deploy my-agent --var ANTHROPIC_API_KEY=@ANTHROPIC_API_KEY

The @SECRET_NAME syntax references a value from your account vault. You can also pass a literal value:

$ ast blueprint deploy my-agent --var REGION=us-east-1

Or load from a file:

$ ast blueprint deploy my-agent --vars-file .env.prod

Use --dry-run to validate inputs without actually deploying:

$ ast blueprint deploy my-agent --var ANTHROPIC_API_KEY=@ANTHROPIC_API_KEY --dry-run

View your deployed agents

$ ast agent list

Shows all running agents in the active account with their status and deployment ID.

Adapters

An adapter controls how your agent is exposed to the world. Each adapter adds an interface (a web endpoint, a Slack bot, or both). You choose adapters at deploy time with --adapter; the default is web with authentication.

Adapter	Description
`web`	Web interface with OIDC authentication (default)
`insecure-web`	Web interface with no authentication; use only in trusted environments
`slack`	Slack bot integration

web and insecure-web are mutually exclusive. slack can be combined with either.

Frontend agents

Agents that declare agent.interfaces.frontend: true in their spec serve their own web UI directly on port 80. The platform routes incoming traffic straight to the agent container — no messaging sidecar or adapter is deployed alongside it.

$ ast blueprint deploy my-frontend-agent

The deployed agent receives a dedicated hostname and is immediately accessible via browser. The --adapter flag has no effect for frontend agents.

Once your agent is running, see Managing your agents for how to inspect, update, and control it.