ZoomInfo's Exa Integration Gives Agents One Connection and Two Contracts
ZoomInfo's records have been reachable inside Exa's agent search since June. The October 23 integration adds Exa search inside ZoomInfo's own tools, and Exa's provider page still lists ZoomInfo as "on request."
TL;DR
- ZoomInfo announced a native Exa integration on October 23; its data had been inside Exa Connect since June 24.
- Research agents get web search and ZoomInfo records in one call, but two contracts and two meters stay separate.
- Watch whether Exa publishes a per-call ZoomInfo price; its own agent already sells email lookups at $0.02 each.
On October 23, ZoomInfo announced a native integration with Exa, the search API built for AI agents, in a product post on its Pipeline blog. Mutual customers can add ZoomInfo company and contact data to agent runs inside Exa, and developers can pull the same records through the GTM.AI API and MCP server. ZoomInfo's integration page adds that customers can enrich GTM Studio audiences "using their Exa license."
Half of that isn't new. ZoomInfo was a launch data partner when Exa Connect went live on June 24, which already let an agent query ZoomInfo through a single Exa request. October adds the reverse direction (Exa's search inside ZoomInfo's own products) and a ZoomInfo-branded wrapper around the June arrangement. ZoomInfo launched GTM.AI as a "headless" layer in June, and Exa is the latest connector it has shipped through it. The others include Claude and Zapier this summer, and ClickUp and n8n in October.
ZoomInfo is counting on the connectors to grow again. Its second-quarter results showed revenue of $310.4 million, up 1.2% from a year earlier, with net revenue retention at 89%. It guided third-quarter revenue to $298 million to $301 million, below the second quarter. It also cut its full-year range to $1.185 billion to $1.205 billion from $1.207 billion to $1.217 billion. With growth stalled, ZoomInfo is moving its records to wherever agents run. We believe more of its buyers will be agents making calls rather than reps opening an app. Exa, which passed $100 million in annualized revenue in October, gets a premium data source to sell alongside its own search.
One Exa request reaches ZoomInfo, but the contracts and meters stay separate
In Exa's Connect documentation, a run lists its data sources in one field. Exa's agent then decides at each step whether to search the web or query a partner, and returns structured output with sources attached. Exa handles the partner authentication, retries and ranking. CROfirst's write-up gives the use case. An agent finds fast-growing AI startups that recently announced SOC 2 compliance, by description rather than by industry code, and attaches ZoomInfo’s company and contact records to the results.
ZoomInfo's own post says Exa is a separate product with its own licensing and billing, and tells readers to check terms with both companies. Exa's Connect page marks ZoomInfo "on request," while other providers on it are self-serve. Exa's pricing page lists per-call fees for partners such as Fiber.ai but none for ZoomInfo. On the other side, GTM.AI's documentation says the customer's subscription decides which endpoints it can call, with rate limits set by package. One agent run therefore bills against two meters (Exa's per-request agent pricing and ZoomInfo's credits). Neither company publishes what the combined call costs. Exa's docs name four providers eligible for its zero-data-retention runs. ZoomInfo isn't one, though its access is arranged through Exa's sales team, so its terms may differ.
Exa sells its own contact lookups, which makes it a rival as well as a channel
Exa's pricing page makes the best case against paying for both. Exa's agent bills $0.02 for each email address it finds and $0.07 for each phone number, with no subscription and no minimum. Fiber.ai's contact data sits in the same Connect menu on self-serve terms. A team without a ZoomInfo contract can build a working research agent on Exa alone.
ZoomInfo's reply, in its company post, is that agents can already search the web and "the hard part is knowing which company is which." ZoomInfo is making a fair point about identity resolution. Matching a subsidiary or a rebranded company to the right record is reference work a RevOps team won't rebuild. Neither company has published match or bounce rates, so for now the claim is ZoomInfo's.
What this means for RevOps teams building research agents
If you already pay for both, get two answers in writing before an agent runs in production. Ask your ZoomInfo rep whether calls routed through Exa draw down your existing credits or need a new entitlement, and ask Exa what it charges per ZoomInfo call. Then price the agent per researched account, counting the Exa run plus every ZoomInfo lookup it triggers. Track that number monthly, the way engineering tracks compute per customer.
Test the identity claim on your own list before you renew. Run the same 100 target accounts through Exa's own lookups and through Exa plus ZoomInfo, and compare how many contacts match the right company and how many emails bounce. The second contract has to pay for that gap.
Neither connection carries your deal history or what your reps know about a champion. That part still lives in your CRM and your team's files, where our piece on the GTM context layer argued it should stay.
