# Install apify-cli with Homebrew Apify command-line interface. Version 1.7.0 via Homebrew; verified 2026-07-02. ## Install ```sh sudo av install brew:apify-cli ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install apify-cli ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:apify-cli - **Package manager:** Homebrew - **Package manager page:** - **Version:** 1.7.0 - **Source summary:** Apify command-line interface - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-07-02T13:49:24Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - actor (cli) - apify (cli) - apify-cli (cli) - actor (alias) - apify (alias) - apify-cli (alias) ## Dependencies - node ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 1.7.0 - Package-manager updated: 2026-07-02 - Local data: ok - Upstream repository: https://docs.apify.com/cli/ - info: Release/tag comparison is only available for GitHub repositories. ## Project history and usage Apify CLI is the command-line tool for creating, developing, running, and deploying Apify Actors and for managing Apify cloud resources from a terminal. It turns the Apify platform into a local developer workflow for web scraping, automation, data processing, Actor runs, storage, and account configuration. ### Project history The public apify/apify-cli repository was created in 2018. The current README and docs describe a CLI for Actor creation, local runs, cloud deployment, datasets, key-value stores, request queues, secrets, builds, and runs. The documentation has evolved with the Apify platform. Current docs identify versioned CLI documentation, a command reference, a changelog, and an Actor definition format based on .actor/actor.json. Recent changelog entries show active 2025-2026 development, including auth commands, Actor type generation, build and run improvements, .actorignore support, an apify api command, improved AI/human help output, and schema validation changes. ### Adoption history Apify distributes the CLI through a recommended macOS/Linux install script, Windows PowerShell install script, npm, and Homebrew. The README also documents npx usage, making it available both as a persistent local binary and as a one-off Node-based command. The batch input's Homebrew package is one of several distribution channels. That matters because Apify CLI often sits in local project setup, CI deployment, and automation scripts where predictable installation and upgrade behavior are important. ### How it is used The quick-start path is apify login, apify create, apify run, and apify push. The command reference expands this into account authentication, Actor development, Actor management, builds, runs, storage operations, API calls, secrets, telemetry controls, and upgrade checks. Actor project metadata is stored in .actor/actor.json at the root of the Actor directory. Authentication stores the saved API token in ~/.apify/auth.json according to the command reference, while Actor definitions may reference Dockerfiles, input and output schemas, storage schemas, changelogs, and environment variables. ### Why package nerds care Apify CLI is a good example of a cloud-platform CLI that is also a project-format tool. Package nerds care about its config files, Node runtime requirements, release cadence, shell installers, Homebrew formula, npm package, and command aliases because the same binary is used for local development, cloud deployment, and CI automation. ### Timeline - 2018: Public apify/apify-cli repository created. - 2025: 0.21 series added and refined Actor/build/run workflows. - 2025: Version 1.1 introduced upgrade and install-command work and breaking CLI behavior changes. - 2026: Version 1.3 added auth commands and Actor type generation. - 2026: Version 1.4 added .actorignore support and Actor search. - 2026: Version 1.5 added apify api and improved help output. - 2026: Version 1.6 added schema-generation and validation improvements. ### Related projects - Apify CLI is closely tied to Apify Actors, Apify SDK, Crawlee, Apify API, Actor definition files, and the Apify platform's datasets, key-value stores, request queues, builds, runs, and secrets. ### Sources - - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: .actor/actor.json ## Credential files - Unix: ~/.apify/auth.json ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** apify-cli - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Related links - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [node](https://www.automicvault.com/pkg/brew/node/) - Runtime dependency declared by Homebrew. - [ahoy](https://www.automicvault.com/pkg/brew/ahoy/) - Shares av.db curated category or tags: automation, cli, developer-tools. - [all-repos](https://www.automicvault.com/pkg/brew/all-repos/) - Shares av.db curated category or tags: automation, cli, developer-tools. - [appium](https://www.automicvault.com/pkg/brew/appium/) - Shares av.db curated category or tags: automation, cli, developer-tools. - [atomist-cli](https://www.automicvault.com/pkg/brew/atomist-cli/) - Shares av.db curated category or tags: automation, cli, developer-tools. - [bitrise](https://www.automicvault.com/pkg/brew/bitrise/) - Shares av.db curated category or tags: automation, cli, developer-tools. - [boot-clj](https://www.automicvault.com/pkg/brew/boot-clj/) - Shares av.db curated category or tags: automation, cli, developer-tools. - [buildozer](https://www.automicvault.com/pkg/brew/buildozer/) - Shares av.db curated category or tags: automation, cli, developer-tools. - [claude-hooks](https://www.automicvault.com/pkg/brew/claude-hooks/) - Shares av.db curated category or tags: automation, cli, developer-tools. - [gatsby-cli](https://www.automicvault.com/pkg/brew/gatsby-cli/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, command-line, developer, developer-tools, interface. - [ovsx](https://www.automicvault.com/pkg/brew/ovsx/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, command-line, developer, developer-tools, interface. ## Combined YAML source View the package source record on GitHub. [combined/apify-cli.yml](https://github.com/automic-vault/db/blob/main/combined/apify-cli.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - cross-ecosystem install command graph