Audienti CLI

Purpose

The Audienti CLI and app-hosted MCP endpoint are the supported agent surfaces for operators and coding agents who need to work against the Audienti API. Use them to inspect accounts, select the right workspace context, review supported workflows, and run account-scoped actions without inventing a parallel wrapper.

An Audienti account and API token are required before authenticated commands will work.

Install

The CLI requires Node.js 20 or newer.

After install, run audienti --help to confirm the command is available.

Authenticate safely

1. Run audienti auth login from a local shell.
2. Open the printed Audienti URL and finish authentication in the browser.
3. Check the current auth state with audienti auth status.

Use audienti auth token <token> only when you already have a token from the app. Never paste a real token into docs, prompts, tickets, or shared logs.

Select your account and default user

audienti accounts list
audienti accounts select <acct_id>
audienti users list
audienti users select me

Keep the selected account visible in your workflow. Use --account when a command must run against a different account than your local default.

Start with read-only commands

• audienti config list shows local CLI configuration.
• audienti motions list confirms the account's motion surface.
• audienti prospects list --json gives agent-friendly prospect data.
• audienti tasks list shows the current user's open reminders.
• audienti help agent-workflows lists the supported local-agent paths.
• audienti-mcp starts a local stdio bridge to the app-hosted /mcp endpoint for hosts that support MCP tools.

Use MCP tools

Audienti serves MCP from the app at /mcp. Most local MCP hosts should use the packaged audienti-mcp bridge after the CLI is authenticated and an account is selected.

audienti auth login
audienti accounts select <acct_id>
audienti users select me
audienti-mcp

The bridge reads ~/.config/audienti/config.json, forwards MCP JSON-RPC to the app, and supplies the selected account when a tool call omits account_id. Direct HTTP clients can call POST /mcp with the same bearer token used by the API.

curl https://app.audienti.com/mcp \
  -H "Authorization: Bearer $AUDIENTI_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

• auth.me confirms the token identity.
• accounts.list shows accessible accounts.
• setup.play_preflight returns connected-account readiness plus setup or mapping URLs.
• offers.create, icps.create, and motions.create set up a motion.
• analytics.stages returns stage conversion cohorts and stage aging.
• analytics.cohort_lists.create materializes event cohorts as reusable lists.

Common supported workflows

• Import prospects with audienti prospects import or audienti prospects import-batch --file prospects.csv.
• Manage person-level suppression with audienti dnc list, audienti dnc add, and audienti dnc import --file dnc.csv.
• Manage company-level policy with audienti company-rules list, audienti company-rules create, and audienti company-rules apply --all.
• Manage reminders with audienti tasks list, audienti tasks add, and audienti tasks complete.
• Inspect analytics with audienti analytics prospects --json or the narrower analytics subcommands.

Build cohort lists for analytics

When a cohort is based on an event, materialize it as a list first. The analytics commands and in-app analytics filters can then reuse the same list instead of redefining the event window by hand.

audienti analytics cohorts create-list --name "Connection requests 2026-07-01 to 2026-07-07" --event connection_request_sent --start 2026-07-01 --end 2026-07-07
audienti analytics dashboard --list <list_id>
audienti analytics prospects --list <list_id> --window 30d
audienti analytics users --user me --list <list_id> --start 2026-07-01 --end 2026-07-31

Use --cohort-start and --cohort-end for entry-based cohorts. Use analytics cohorts create-list followed by --list when the cohort is event-based, such as people who received connection requests, blank-note requests, replies, accepted connections, or meeting requests during a date range.

Safety boundaries

• Inspect current state before create, update, attach, delete, or outcome writeback commands.
• Prefer --json when another tool or agent will parse the result.
• Do not use undocumented API calls when the CLI already has a supported command.

Agent contract

• Use: choose supported CLI commands or MCP tools for account-scoped inspection, imports, suppression, company rules, tasks, analytics, operator queue work, and local agent workflows.
• Inputs: selected account, API token, default user, target record id, file path, date window, and whether the command is read-only or mutating.
• Commands: start with audienti auth login, audienti auth status, audienti accounts list, audienti accounts select <acct_id>, audienti users select me, and audienti help agent-workflows.
• Verify: use --json for machine parsing, confirm the account id in the result, and run a read-only listing command before mutating account data.
• Never: paste tokens into shared context, invent undocumented API wrappers, or perform write commands when the user only asked for inspection.