Skip to content

Deploy to the agent hub

These are the terminal twins of the agent hub screens — care deploy, care deployments, and care metrics mirror the TUI’s /deploy, /deployments, and /metrics. A deployed chain is served as an HTTP agent on the hub, with its own Swagger UI.

Deploy a saved chain to the agent hub as an HTTP agent. The command mints an api_key; the hub then fetches the chain by entity_id on the given channel and validates that it loads (a rejection surfaces here).

Terminal window
care deploy weather-risk --name weather-risk --channel stable
FlagDefaultPurpose
chain_id—Memory entity_id of the chain to deploy.
--name NAMEslug of chain_idAgent name on the hub.
--channel CstableChannel to deploy — production ships the released version, not the dev tip.

On success it prints the deployed agent’s name, its URL, and a link to its /docs (Swagger) page. There is no --json for this command.

List the agents currently on the hub — a readiness badge, URL, version, and run count per deployment.

Terminal window
care deployments
care deployments --json
FlagDefaultPurpose
--jsonoffEmit JSON instead of the badge list.

Usage / cost metrics. Pass an agent name to read that agent’s /metrics; omit it to summarise run counts across all deployments.

Terminal window
care metrics weather-risk # one agent's metrics
care metrics # run-count summary across the hub
care metrics --json
FlagDefaultPurpose
name—Agent name (omit to summarise all deployments).
--jsonoffEmit JSON.

Deploy a chain on the stable channel, confirm it landed, then read its metrics:

Terminal window
# 1. Deploy the chain (hub must already be running)
care deploy weather-risk --channel stable
# → deployed: weather-risk → http://127.0.0.1:8080/agents/weather-risk (docs: …/docs)
# 2. List what's on the hub
care deployments
# → ● weather-risk http://127.0.0.1:8080/agents/weather-risk v1 runs=0
# 3. Read its usage metrics
care metrics weather-risk