CLI

Read and publish prompts from your terminal

The CLI ships in the same package as the SDK.

npx

npx anpord list

Authentication comes from the environment:

export ANPORD_API_KEY="anp_..."

Commands

get

anpord get <id> [--json] [--channel <name>] [--at <version>]

Prints the prompt’s content to stdout, which makes it pipeable:

anpord get support-reply > prompt.txt
anpord get support-reply | pbcopy

--json prints the whole prompt instead, including its version and channel. --channel and --at select which version to resolve, following the same rules as the API.

The flag to pin a version is --at. --version prints the CLI’s own version.

list

anpord list [--json]

One prompt per line as id, latest version, and name. Returns up to 100 prompts.

versions

anpord versions <id>

The prompt’s history as JSON. Takes no flags.

push

anpord push <id> <content> [-m <message>]

Appends a version. Pass - to read the content from stdin:

cat prompts/support-reply.md | anpord push support-reply - -m "Rewrite"

Pushing does not change what production serves. Promote when you are ready.

promote

anpord promote <id> --to <channel> --at <version>

Points a channel at a version. Both flags are required.

anpord promote support-reply --to production --at 5

Scripting

Content goes to stdout and everything else to stderr, so redirecting a prompt to a file captures the prompt and nothing else. A failure exits non-zero with a single line and no stack trace:

if ! anpord get support-reply > prompt.txt; then
  echo "could not resolve the prompt" >&2
  exit 1
fi

Completions

anpord --completions zsh

Also available for bash and fish.

Configuration

Variable	Purpose
ANPORD_API_KEY	Required. The key the CLI authenticates with.
ANPORD_BASE_URL	Optional. Defaults to https://api.anpord.com.

ANPORD_BASE_URL is read by the CLI and the MCP server. The SDK constructor does not read it — pass { baseUrl } to point the client elsewhere.