Enriching B2B data has lived in two places, a web app you click through or an API you build against. The command line is the third, and it is where a growing share of go-to-market data work now runs. CLI data enrichment brings the same lookups to your terminal, so one command turns thin, aging records into complete, current ones, ready to pipe into a script, a schedule, or an AI agent.
This guide covers what CLI data enrichment is, how it works, what to look for in a tool, and how ZoomInfo does it from the terminal.
What Is CLI Data Enrichment?
CLI data enrichment is the process of filling in and refreshing your records with external data through a command-line interface, a tool you run by typing commands in a terminal. You feed in the records you have, the tool matches each one against a data provider, and it returns them with new and updated fields, as structured output you can pipe into whatever runs next.
What it does is close the gap between the incomplete, aging records teams often work from and the complete picture they need to act on. A CRM row might be little more than a company name and a website. Enrichment turns that into revenue, headcount, industry, and the right contacts, and it refreshes the fields that drift out of date as people change jobs and companies grow. What you can append usually falls into three buckets:
Data type | Examples |
Firmographics | Revenue, employee count, industry, location, ownership |
Contact detail | Job title, seniority, verified email, direct phone |
Signals | Buying intent, funding, hiring, leadership changes |
What makes the CLI version distinct is that the enriched data comes back as machine-readable output, so it feeds the next step on its own. That turns enrichment into a repeatable part of a workflow rather than a one-off file you download and forget.
How CLI Data Enrichment Works
The flow is the same across tools, even when the commands differ. It comes down to three steps:
Start with an identifier. You begin with something you already hold, a company domain, an email address, or a CRM record ID. This is the key the tool matches on, so the cleaner it is, the better the match.
Run the enrich command. The tool looks up each identifier against its dataset, resolves the matching company or person, and appends the fields you asked for. Many tools let you choose which fields come back, so you pull only what you need.
Pipe the output onward. Results return as JSON, CSV, or another structured format, ready to load into your CRM, write to a warehouse, or feed the next command.
Two things shape how well this works. Match quality decides everything, since a tool can only enrich a record it can confidently identify, which is why clean identifiers matter. And enrichment usually draws on credits, so the fields and volume you request translate straight into cost.
Why Teams Enrich From the Command Line
Running enrichment from the terminal, rather than a dashboard, changes what you can do with it:
Automation. A command drops into a cron job or a scheduled task, so a list refreshes on its own without anyone exporting anything.
Pipelines. Structured output pipes straight into the next step, so enrichment slots between a search and a CRM load without manual hand-offs.
Determinism. A CLI returns the same result for the same input every time, with no model deciding what to fetch, which matters when the output feeds automated decisions.
Version control. Because the step is code, it lives in Git with the rest of your workflow, so changes are reviewed and repeatable.
Agent-readiness. Machine-readable results and clean exit codes let an AI agent run enrichment and act on what comes back, which is why more agent workflows enrich this way.
Common Use Cases for CLI Data Enrichment
The interface matters because of what it lets you automate. These are the workflows CLI data enrichment tends to show up in:
Refresh a stale CRM segment. Point the CLI at the account or contact IDs you already hold and re-enrich them on a schedule, so a territory or ICP list stays current without anyone exporting and re-importing it.
Enrich inbound leads on arrival. Slot enrichment into the flow that catches new form fills, so a bare email becomes a lead with company size, industry, and title attached before it reaches a rep or a routing rule.
Build a target account list. Start from a set of domains, a campaign export, or a search, enrich each account with firmographics and its buying committee, and hand off a list that is ready to work.
Clean records before a CRM import. Standardize and complete rows in a script before they load, so you are not pushing thin or duplicate data into the system of record.
Feed a scoring or routing model. Append the fields a model depends on, headcount, industry, seniority, intent, as a scheduled step, so lead scoring and routing run on current inputs.
Give an AI agent live data. Expose enrichment as a command an agent can call mid-task, so it can pull what it needs to prioritize accounts or personalize outreach.
What to Look For in a CLI Enrichment Tool
CLI tools are easy to compare on syntax and hard to compare on what actually matters. A few things to weigh:
Data coverage and accuracy. A clean command that returns stale or thin records helps no one, so check how deep and how current a provider's data is before you judge the syntax.
Identifier and field flexibility. Look for a tool that matches on whatever you have, a domain, an email, a name, or an ID, and lets you request only the fields you need.
Output formats. JSON, JSONL, CSV, and table each suit a different downstream step, so range here keeps the tool usable across pipelines.
Pricing and credit model. Understand what counts as a charge, and whether re-enriching a record you already hold costs again.
Match and duplicate handling. Good tools resolve the right record and avoid creating duplicates, which protects the CRM you are feeding.
Agent and pipeline fit. A tool that runs unattended, with no interactive prompts and a clear exit code when something fails, is one a scheduled job or an agent can rely on.
How ZoomInfo Does CLI Data Enrichment
ZoomInfo offers CLI data enrichment through its GTM CLI, a single command-line client for ZoomInfo's go-to-market data. It enriches companies and contacts from the terminal on the same hosted endpoint as ZoomInfo's MCP server and API, so the data and credits match the tools you already use.
In the demo below, ZoomInfo's chief product officer runs a full enrichment job from a coding agent, pulling a prioritized account list, enriching each company, and generating briefs on a couple hundred tokens.
Here is how it works in practice:
Enrich from any identifier you hold. For a company, that can be a domain, a name, a ticker, or a ZoomInfo ID. For a contact, a person ID, an email, a phone number, or a name paired with a company.
Choose the fields you want back. Append revenue, employee count, and industry for an account, or job title, seniority, and a verified email for a person, rather than pulling everything.
Enrich a list in one command. Pass a file of records and enrich them in a single pass instead of one at a time.
Pay only for what you enrich. Search and lookup are free, enrichment draws down bulk credits, and a record already under management is not charged again.
Get structured output. Results come back as JSON, JSONL, CSV, YAML, or a table, so they drop into a script, a CRM upload, or a warehouse without reshaping.
Run it wherever the work happens. The CLI is deterministic, with no model deciding what to fetch, and shares a backend with ZoomInfo's MCP server and API, so the same enrichment works from a script, an AI agent, or an application. Sign-in is a single browser step over OAuth.
Enrich From Your Terminal With ZoomInfo
CLI data enrichment turns a manual, repetitive task into a command you can script, schedule, and hand to an agent. ZoomInfo's GTM CLI brings that to enterprise-grade go-to-market data, enriching companies and contacts from the terminal on the same backend as its MCP server and API, with search and lookup free and enrichment metered by credit.
Explore the GTM CLI to get started. Install it, sign in over OAuth, and enrich your first record before wiring it into a pipeline.
Frequently Asked Questions
Is CLI data enrichment the same as a data enrichment API?
Not quite, though they often sit on the same data. A CLI is a finished tool you run and script from the terminal, with commands, output formats, and sign-in handled for you. An API is a lower-level interface you build an application against, writing your own requests, retries, and caching. Many providers offer both, so you can prototype with the CLI and move to the API when you are building software.
Do you need to be a developer to use CLI data enrichment?
Not to run it. If you are comfortable opening a terminal and typing a command, you can enrich a record or a file. Writing the surrounding automation, scheduled jobs, pipelines, and error handling, is where engineering help pays off, but the enrichment step itself is a single command.
Is CLI data enrichment secure?
It depends on the tool, so it is worth checking how a CLI signs in. The safer pattern is a browser-based login that stores a token locally with restricted permissions, rather than pasting a long-lived key into your shell history. It is also worth confirming where output is written, since enriched files can contain personal data.
How often should you re-run CLI data enrichment?
Often enough to stay ahead of data decay. B2B data ages quickly as people change roles and companies grow, so a record enriched a year ago is likely stale. Scheduling enrichment to re-run on a cadence, monthly or quarterly for an active list, keeps the data current without anyone remembering to do it by hand.
