Deploy your first agent
Deploying takes a blueprint from the registry and runs it as a live agent on Astro AI. 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
<name> is the blueprint name (as shown in ast blueprint list). By default the agent is accessible through a web interface with authentication enabled.
Give the deployment a custom display name:
Supply required variables
Most agents require API keys or credentials at deploy time. Pass them inline:
The @SECRET_NAME syntax references a value from your account vault. You can also pass a literal value:
Or load from a file:
Use --dry-run to validate inputs without deploying:
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.
web and insecure-web are mutually exclusive. slack can be combined with either.
insecure-web disables authentication, so anyone with the endpoint URL can access your agent. Use it only in trusted environments.
Frontend agents
Agents that declare agent.interfaces.frontend: true in their spec serve their own web UI. Deploy them the same way:
The deployed agent receives a dedicated hostname and is immediately accessible in a browser. The --adapter flag has no effect for frontend agents.
Next steps
- Managing your agents: inspect, update, and control a running agent
- Monitor your agents: add tracing and metrics to a deployed agent