# Install apibuilder-cli with Homebrew

Command-line interface to generate clients for api builder. Version 0.2.4 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:apibuilder-cli
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install apibuilder-cli
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:apibuilder-cli
- **Package manager:** Homebrew
- **Version:** 0.2.4
- **Source summary:** Command-line interface to generate clients for api builder
- **Homepage:** <https://www.apibuilder.io>
- **Repository:** <https://github.com/apicollective/apibuilder-cli>
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- apibuilder (alias)
- create-config (alias)
- read-config (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.2.4
## Project history and usage

apibuilder-cli is the command-line interface for API Builder, a platform for managing API descriptions and invoking code generators. It lets users list organizations and applications, upload API descriptors, generate clients, and update local generated code from project configuration.

### Project history

The public apicollective/apibuilder-cli repository was created in 2015. The README describes a CLI centered on the app.apibuilder.io service: public APIs need no setup, while private APIs use a generated configuration file containing an API token.

The broader API Builder site presents the service as tooling for modern APIs, including management, sharing, version history, native libraries, and code generators. The CLI is the package-manager-facing piece of that ecosystem, exposing generator and upload workflows to scripts.

### Adoption history

The README documents Homebrew installation on macOS and a shell install path for other platforms. The batch input shows Homebrew packaging, which is consistent with a developer workflow tool used from local repositories and CI jobs rather than as a long-running service.

### How it is used

The CLI can list organizations, applications, and versions; invoke a named generator into a target directory; upload an API descriptor with a version; update generated code based on .apibuilder/config; clean API Builder versions not tagged in the source repository; and check or upgrade the CLI itself.

Private API use stores tokens in ~/.apibuilder/config. Project update workflows use a YAML .apibuilder/config file in the current repository to specify organizations, projects, versions, generators, target paths, file patterns, and generator attributes.

### Why package nerds care

apibuilder-cli matters as glue between an API catalog and generated client/server code in a local source tree. For package users, the interesting bits are the split between global credentials and per-project generator config, and the fact that the CLI can be driven from Git hooks or continuous delivery with silent upload and clean modes.

### Timeline

- 2015: Public apicollective/apibuilder-cli repository created.
- 2010s: README documents Homebrew installation and token-backed private API setup.
- 2026: Repository metadata shows continued pushes to the public repository.

### Related projects

- apibuilder-cli is related to the API Builder web service, app.apibuilder.io generators, API descriptor formats, and generated clients such as Play, http4s, Android, Kotlin, and other generator-backed outputs.

### Sources

- <https://api.github.com/repos/apicollective/apibuilder-cli>
- <https://app.apibuilder.io/generators>
- <https://github.com/apicollective/apibuilder-cli#readme>
- <https://www.apibuilder.io/>
- input source_facts.package-manager


## Security Notes

broad file, network, media, or database tool signal.

- **Geiger risk:** blue / medium
- broad file, network, media, or database tool signal


## 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: ~/.apibuilder/config, .apibuilder/config

## Credential files

- Unix: ~/.apibuilder/config

## Combined YAML source

View the package source record on GitHub. [combined/apibuilder-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/apibuilder-cli.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph