> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brew.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Brew CLI

> brew-cli puts the whole Brew platform in your terminal: one typed command for every Public API operation, built for humans, scripts, CI, and AI agents.

The **Brew CLI** (`brew-cli`) is the command-line surface of Brew. Every operation in the [Public API v1](/api-reference/api/api-introduction) has a typed command: create brands, generate and edit email designs with AI, send and schedule, build automations, manage contacts and audiences, verify domains, and read analytics, all from your terminal.

Like the [MCP server](/api-reference/mcp/overview), it is a thin layer over the same API your dashboard uses: the same validation, permissions, credit metering, and rate limits apply everywhere. Anything you can do in the app, you can script.

## Why It Matters

* **Everything, scriptable**: generate a welcome email, send it to a segment, wire an automation, and pull open rates without leaving your terminal. Every Public API operation is covered, and new platform capabilities arrive as CLI updates.
* **Built for agents**: JSON output turns on automatically when output is piped, exit codes are semantic, destructive commands never hang waiting for input, and `brew-cli docs --agent` prints a machine-readable manifest of every command. See [Use from AI Agents](/api-reference/cli/agents).
* **Scripts and CI**: stable flags, idempotency keys for safe retries, cursor draining with `--all`, and a raw `brew-cli api` escape hatch for anything new before a dedicated command ships.

## Sixty Seconds In

```bash theme={null}
brew install getbrew/tap/brew-cli
brew-cli login                # paste an API key from brew.new/settings/api
brew-cli emails list --limit 5
brew-cli contacts search --filter email:contains:@acme.com --json
```

## What's Next

* [Installation](/api-reference/cli/installation): Homebrew, prebuilt binaries, or npm.
* [Authentication](/api-reference/cli/authentication): API keys, brand scoping, and environments.
* [Commands](/api-reference/cli/commands): what is included and the conventions every command shares.
* [Common Flows](/api-reference/cli/common-flows): worked sequences for launching, automating, and reporting.
* [Use from AI Agents](/api-reference/cli/agents): the output and exit-code contract agents can rely on.

## Need Help?

Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:

<Tabs>
  <Tab title="Self-Service Tools">
    <CardGroup cols="2">
      <Card title="Search Documentation" icon="magnifying-glass" color="#c44925">
        Type in the "Ask any question" search bar at the top left to instantly find relevant documentation pages.
      </Card>

      <Card title="ChatGPT/Claude Integration" icon="robot" color="#c44925">
        Click "Open in ChatGPT" at the top right of any page to explore it further with ChatGPT or Claude.
      </Card>
    </CardGroup>
  </Tab>

  <Tab title="Talk to Our Team">
    <CardGroup cols="2">
      <Card title="Schedule a Call" icon="calendar" color="#c44925" href="https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ1iYoRUG1J792XQpbuQLjSRRDupr7MwraFK-HQRCtTYdBmrQi8nZu2qXfzKQigb8gbKJK3KN3-R">
        Book time with our founders for personalized guidance on strategy, best practices, or complex implementation questions.
      </Card>

      <Card title="Call Us Directly" icon="phone" color="#c44925">
        Need immediate assistance? Reach us at **+1-(332)-203-2145** for urgent issues or time-sensitive questions.
      </Card>

      <Card title="Slack Channel" icon="slack" color="#c44925">
        Our preferred support channel. You'll receive an invite after signup for direct founder support and fast responses.
      </Card>

      <Card title="Email Support" icon="envelope" color="#c44925" href="mailto:support@brew.new">
        Contact us at **[support@brew.new](mailto:support@brew.new)** for detailed inquiries or if you prefer not to use Slack.
      </Card>
    </CardGroup>
  </Tab>
</Tabs>