Use from AI Agents

​

The Contract

• JSON without asking. When stdout is not a terminal (which is every agent), commands print the exact API response as one JSON line. Errors are JSON envelopes on stderr with stable code fields and a requestId.
• Semantic exit codes. 0 success, 1 API or runtime error, 2 usage error, 3 authentication error, 4 confirmation required. Unknown commands fail hard with no fuzzy “did you mean” to misread.
• Never hangs. Nothing waits on stdin unless it is a real terminal. Missing input is an immediate exit 2 with the fix in the message.
• Stable surface. Commands and flags are additive across releases, and the manifest describes the installed build exactly.

​

The Confirmation Protocol

{
  "confirmationRequired": true,
  "command": "brew-cli emails send",
  "summary": "Send email eml_123 as a REAL campaign to audience aud_9 now. Real recipients receive it; this cannot be undone.",
  "confirmCommand": "brew-cli emails send eml_123 --subject 'Fall sale' --audience aud_9 --domain dom_1 --yes"
}

​

Discovery for Agents

brew-cli docs --agent

​

A Typical Agent Session

brew-cli contacts count --json
brew-cli emails generate --prompt "Welcome email for new signups" --json
brew-cli emails send eml_abc --test --to qa@yourteam.com --subject "Preview"
brew-cli analytics overview --since 2026-08-01T00:00:00Z --json

​

Need Help?