Publish your agent

Publish a validated source tree as a new chain or a new version.

Choose publish or evolve

New agent identity? ──yes──▶ Publish a new genesis
          │ no
          ▼
Existing chain? ───────────▶ Evolve: download, edit, publish next version

Use a genesis reference for a process that must follow later active versions. Use an exact version only when the process must remain pinned.

Preflight

Confirm the active workspace, account, source directory, validation result, and intended chain.

Prompt your AI agent

Recommended

Use the `dino-ping` skill to publish this validated agent.
Determine whether this is a new chain or an evolution.
Verify the active workspace, account authority, agent source, and live history.
Show the exact target chain and publication effect.
Wait for my approval before one publication attempt.
Return the genesis ID, version ID, and idempotency key.

Use the Dino CLI directly

dino workspace current
dino workspace check
dino account get
dino agent validate --agent-dir <absolute-agent-dir>

# New chain, after exact approval:
dino agent publish --agent-dir <absolute-agent-dir> \
  --confirm-mutation agent.publish

# Existing chain: download the live chain, edit, validate, then publish the
# next version. `publish` detects the downloaded agent. After exact approval:
dino agent download --agent-id <genesis-id> --folder <local-name> \
  --confirm-mutation agent.download

dino agent publish --agent-dir <absolute-agent-dir> \
  --confirm-mutation agent.publish

Verify the result

dino agent get --agent-id <agent-id>
dino agent history --genesis-id <genesis-id>

Gotchas

• The first publisher becomes the immutable chain owner.
• Visibility does not prove ownership.
• Do not evolve a stale download over a newer live version.
• Keep integration IDs stable across evolves.
• Retry the same request only with its original idempotency key.
• Publishing does not create a campaign or place a call.

Next

Use Test your agent before you create a repeatable call workflow.