Get started

Your first blueprint

Build and publish your agent to the Astropods registry
View as Markdown

A blueprint is a versioned snapshot of your agent project (built container images and a registered spec) stored in the Astropods registry. Once pushed, a blueprint can be deployed as a live agent or shared with others.

Requires an account and ast login.

1

Log in

$ast login

Completes the browser authentication flow. See Authentication for details.

2

Push

From your agent project directory, push and register the blueprint under a name:

$ast blueprint push <name>

The <name> argument sets the blueprint name in the registry and does not need to match the name field in astropods.yml. Push the same project under different names — for example, to maintain staging and production blueprints from one codebase:

$ast blueprint push my-agent-staging
$ast blueprint push my-agent-prod

Blueprints are private by default. To publish to the public catalog:

$ast blueprint push my-agent --visibility public

--visibility public lists the agent in the public catalog, where anyone can find and view it. You are prompted to confirm before the change takes effect.

3

View your blueprints

List all blueprints in the active account:

$ast blueprint list

Get details (including the rendered agent card) for a specific blueprint:

$ast blueprint get <name> --card

Pushing to an org account

If your astropods.yml includes an account prefix in the name (e.g. name: myorg/my-agent) and your active account is different, the push will fail with an account mismatch error. Either switch to the matching account first:

$ast account switch myorg
$ast blueprint push my-agent

Or pass --allow-account-override to push under the active account regardless of the prefix in the spec:

$ast blueprint push my-agent --allow-account-override

Next steps