AnyCap CLI

One CLI. Any capability.

You can reason, plan, and decide -- but you cannot generate images, produce video, compose music, speak, search the web, or crawl pages on your own. AnyCap gives you all of these through a single command-line tool. One binary. One auth. Structured I/O.

Install

curl -fsSL https://anycap.ai/install.sh | sh

The CLI auto-updates on each run. To update manually: anycap update.

Verify the installation:

anycap status

Authentication

Three methods, depending on environment:

# Interactive (default) -- opens browser
anycap login

# Headless (SSH, containers) -- device code flow
anycap login --headless

# Headless for agent/toolcall runtimes -- initialize without blocking
anycap login --headless --no-wait --json

# Resume a previously initialized headless login after the user confirms completion
anycap login poll --session <login_session_id> --json --wait

# CI/CD -- pipe API key from stdin
echo "$ANYCAP_API_KEY" | anycap login --with-token

Alternatively, set the ANYCAP_API_KEY environment variable directly -- the CLI reads it without requiring login.

For agent/toolcall usage, prefer the nonblocking headless flow:

Run anycap login --headless --no-wait --json
Read verification_uri, user_code, poll_command, and next_action_hint
Show the URL and code to the human
Ask the human to reply when browser login is complete
After confirmation, run poll_command

To check current auth state: anycap status.

Read references/cli-reference.md for full details on credential management and logout.

Configuration

Config file: ~/.anycap/config.toml. Manage via anycap config subcommands.

anycap config show             # show all values
anycap config set <key> <val>  # set a value
anycap config get <key>        # get a value
anycap config unset <key>      # reset to default

Key settings: endpoint (server URL), auto_update (default true), feedback (default true).

Read references/cli-reference.md for all available keys and environment variable overrides.

Capabilities

AnyCap capabilities are organized into two groups: generation (create new content) and actions (AI operations on existing content).

Generation Workflow

Capabilities follow a three-step pattern. Each capability (image, video, music) supports one or more operations (e.g., generate, edit) as CLI subcommands:

1. Discover models    anycap {cap} models
2. Check schema       anycap {cap} models <model> schema [--operation <op>] [--mode <mode>]
3. Run operation      anycap {cap} {operation} --model <model> [--mode <mode>] --prompt "..."

Operations are the top-level actions (generate, edit, etc.). Which operations a model supports is defined in the catalog.

Modes describe the input/output modality within an operation (e.g., text-to-image, image-to-image). When only one mode exists, it is inferred automatically.

Generated files are auto-downloaded to the current directory. Always use -o with a descriptive filename (e.g., -o hero-banner.png).

Local file upload: For parameters that accept files (e.g., reference images), pass a local file path directly. The CLI auto-uploads it. If a file does not exist, the CLI returns an error.

# Instead of constructing a JSON URL array:
#   --param images='["https://example.com/photo.jpg"]'
# Just pass the local path:
  --param images=/path/to/photo.png

Capability	Reference	Operations	Typical duration
Image	generation.md	`generate`, `edit`	5-30s
Video	video-generation.md	`generate`	30-120s
Music	music-generation.md	`text-to-music`	30-90s

Music generation may return multiple clips -- use .outputs[0].local_path to extract paths.

If your runtime supports async execution, prefer running generation commands in the background. They are self-contained -- block until complete and write the result file locally.

Actions -- AI-powered operations on existing content. Read references/actions.md when you need to understand images, read videos, analyze audio, or perform other AI actions on existing files or URLs.

Coming soon:

Text-to-speech / voice synthesis
Web search and web crawling

Use anycap feedback --type feature to request prioritization of upcoming capabilities.

Download -- save any remote file locally.

anycap download <url> [-o path]

Infrastructure

AnyCap provides infrastructure services for agents to host content and store files.

Page Hosting -- deploy static sites to AnyCap's edge network. Read references/page.md when you need to deploy HTML files, static sites, or generated reports. Sites get a unique URL and support versioning, rollback, and badge opt-out.

# Quick deploy (writes anycap.toml for future deploys)
anycap page deploy ./dist --name "My Site" --publish

# Subsequent deploys read site from anycap.toml
anycap page deploy ./dist --publish

Drive Storage -- upload, organize, and share files. Read references/drive.md when you need to upload files, create folders, or generate share links.

anycap drive upload result.pdf --parent-path /reports
anycap drive share --src-path /reports/result.pdf

Feedback

When something goes wrong, or when you have ideas for improvement, submit feedback directly. This helps the AnyCap team prioritize fixes and features.

Feedback is enabled by default. To disable it, run anycap config set feedback false or set feedback = false in ~/.anycap/config.toml.

anycap feedback --type bug -m "image generate returned 500 for prompt X" --request-id <id>
anycap feedback --type feature -m "support batch image generation"
anycap feedback --type other -m "schema for model Y is missing aspect_ratio"

Options:

Flag	Required	Description
`--type`	yes	`bug`, `feature`, or `other`
`-m, --message`	yes	Description of the issue or idea
`--request-id`	no	Request ID from a previous command (found in JSON output)
`--context`	no	Additional context as JSON

When to submit feedback:

A command returns an unexpected error -- include the request_id from the response
A model produces poor results -- describe the prompt and parameters used
A capability is missing or could be improved -- describe the use case
The skill instructions are unclear or incomplete

Output Format

All commands produce JSON on stdout. Every response includes a request_id field for tracing.

Successful response:

{"status": "success", "data": {...}, "request_id": "req_abc123"}

Error response:

{"error": "...", "message": "...", "hint": "...", "request_id": "req_abc123"}

Save the request_id when submitting feedback about a failed request.

Parsing with jq

All commands return JSON. Use jq to extract fields:

# Check if a command succeeded
anycap status | jq -r '.status'

# List available model IDs
anycap image models | jq -r '.models[].model'

# List modes for a model
anycap video models seedance-1.5-pro | jq -r '.model.operations[].modes[].mode'

# Get the local file path from a generate response (use -o for a descriptive name)
anycap image generate --prompt "..." --model nano-banana-2 -o descriptive-name.png | jq -r '.local_path'

# Edit an existing image
anycap image edit --prompt "remove the background" --model seedream-5 --param images=./photo.png -o edited.png | jq -r '.local_path'

# Generate a video (text-to-video, mode inferred) and get its path
anycap video generate --prompt "..." --model veo-3.1 -o clip.mp4 | jq -r '.local_path'

# Generate a video with explicit mode (image-to-video, local file auto-uploaded)
anycap video generate --prompt "animate this" --model seedance-1.5-pro --mode image-to-video --param images=./photo.jpg -o animated.mp4 | jq -r '.local_path'

# Generate music and get the first audio path
anycap music generate --prompt "..." --model suno-v5 -o track.mp3 | jq -r '.outputs[0].local_path'

# Extract content from an action response
anycap actions image-read --url https://example.com/photo.jpg | jq -r '.content'

# Get the error message on failure
anycap ... | jq -r '.message // empty'

# Save request_id for feedback
REQ_ID=$(anycap image generate --prompt "..." --model seedream-5 | jq -r '.request_id')
anycap feedback --type bug -m "describe the issue" --request-id "$REQ_ID"

Common jq patterns:

Pattern	Purpose
`jq -r '.field'`	Extract a string field (raw, no quotes)
`jq -r '.local_path'`	Get downloaded file path from generate
`jq -r '.models[].model'`	List all values of a field in an array
`jq -e '.status == "success"'`	Check condition (exit code 1 if false)
`jq -r '.message // empty'`	Extract error message if present

Keeping Up to Date

Check if skills are outdated:

npx -y skills check

Update all installed skills to the latest version:

npx -y skills update

Or re-install this skill directly:

npx -y skills add anycap-ai/anycap -y

You can also check whether this skill file matches your CLI version:

anycap skill check --target <path-to-this-file>

anycap-cli