Apollo and ZoomInfo API for agents: what you can call, and per-call options
The Apollo API and the ZoomInfo API for an AI agent: what each lets you call, how each bills credits, and the per-call options through looot.
Walid Boulanouar · , updated · 7 min read
On this page
The Apollo API search for people costs zero credits, and it returns no email address and no phone number. That one line from Apollo's own docs explains most of the Apollo API: search is cheap, contact data is what you pay for. If you want an AI agent to call the Apollo API or the ZoomInfo API, you need to know what each lets you call, how each bills, and which jobs you can run per call instead.
This post reads both vendors' developer docs (read 2026-10-13), puts their endpoints and credit rules side by side, and shows the per-call options in the looot catalog for the same jobs. You will know which calls an agent can make, what they cost in credits, and when paying per call fits better.
What does the Apollo API let an agent call?
The Apollo API covers search, enrichment and the records inside Apollo. An agent can search people and companies, enrich a person or an organization, and manage contacts, deals and sequences. Access depends on your Apollo plan, and you create a key in Settings with the endpoints it may call.
The calls a data agent uses most:
- People API Search finds net-new prospects by filters. It uses 0 credits and returns no emails or phone numbers, and it shows at most 50,000 records, 100 per page (Apollo people API search, read 2026-10-13).
- People enrichment returns a person's data, including a work email, and bills credits when data is found.
- Organization enrichment and organization search return company data.
A key can be scoped to the endpoints you pick, or set as a master key for all of them (create an API key, read 2026-10-13). Rate limits apply per team and per endpoint, by minute, hour and day. On the free plan that is 50 requests a minute and 600 a day per endpoint (Apollo rate limits, read 2026-10-13).
Apollo API pricing: how the credits work
Apollo prices API calls in credits from your plan, not in dollars per call. Endpoints that create, update or list records use 0 credits. Enrichment and organization search use credits when data comes back.
| Apollo API endpoint | Credits, current plans | Source |
|---|---|---|
| People API Search | 0 credits | docs.apollo.io, read 2026-10-13 |
| People enrichment | 1 to 9 credits per person: 1 for demographics or email, 8 more if a mobile phone comes back | API pricing and credits, read 2026-10-13 |
| Organization enrichment | 1 credit per organization | API pricing and credits, read 2026-10-13 |
| Organization search | 1 credit per page, up to 100 results | API pricing and credits, read 2026-10-13 |
Waterfall enrichment inside Apollo can cost more. Apollo's page says an email waterfall typically uses 1 to 4 credits, and some vendors in it bill a lookup even when nothing is found. Legacy plans may bill differently, so check the credit page in your own Apollo account.
What does the ZoomInfo API let an agent call?
The ZoomInfo API covers search and enrichment of companies and contacts, plus audiences and signals. Your ZoomInfo subscription decides which scopes and endpoints you can reach, and every call goes through OAuth 2.0, with a client credentials flow for server-to-server use (ZoomInfo API overview, read 2026-10-13).
Credits work differently from Apollo. ZoomInfo customers buy credits in bulk each year. Searching companies and contacts is free. Enriching a record uses one credit the first time in a rolling 12 months, and that record can then be enriched again for a year without a new credit. The default rate limit is 25 requests per second per tenant (ZoomInfo credit usage and limits, read 2026-10-13).
| Apollo API | ZoomInfo API | |
|---|---|---|
| Who gets access | Depends on the Apollo plan | Depends on the ZoomInfo subscription |
| Auth | API key, scoped or master | OAuth 2.0 |
| Search | 0 credits for people, 1 credit per page for organizations | Free for companies and contacts |
| Enrichment | Credits per person or organization when data is found | 1 credit per record per rolling 12 months |
| Limits | Per team and endpoint, per minute, hour and day | 25 requests per second by default |
Per-call options for the same jobs
If you do not have an Apollo or ZoomInfo plan, the data jobs behind these calls are in the looot catalog, paid per call from one balance. Your agent asks for a job, sees the price, then runs it. The table reads the cheapest live price for each job when the page loads.
The job pages list every provider with its price: the people search API, the email finder API, the mobile number finder and the company enrichment API.
Which one fits depends on volume and on who reads the data. A plan fits when many people search all day inside the app. Per call fits when one agent pulls the data and others read the result.
A prompt to try
Prompt for your agent
Find decision makers without an Apollo plan
Check the five rows by hand before you run the rest.
What it cannot do
- It does not call Apollo's or ZoomInfo's own API for you. An Apollo connection that uses your own Apollo key is listed in the looot catalog as coming soon and cannot run yet.
- No sequences, no dialer, no shared workspace or seats. looot returns data to your agent. It does not send campaigns, make calls or track replies.
- No buyer intent data and no maintained org charts. People search returns lists, not a chart someone keeps current.
- No native CRM sync. Your agent writes to the CRM with its own tools, and you check it.
- Re-pulling a list every week needs scheduled runs, not available yet.
For the wider choice of tools, see Apollo alternatives, ZoomInfo alternatives and the side by side Apollo vs ZoomInfo page.
Last checked 2026-10-13. Apollo and ZoomInfo terms were read that day from the pages linked above. looot prices are read from the live catalog when the page loads.
Questions
Keep reading
Best data enrichment tools: a 2026 buyer's checklist
A checklist for choosing data enrichment tools: coverage, price per row, freshness, verification and output shape, and where an agent with a catalog fits.
Walid Boulanouar · · 6 min read
What 1,000 lookups cost: reading the looot catalog
How to work out the cost of 1,000 lookups from the live looot catalog, and why the cheapest provider is chosen per call instead of once per project.
Luisa · · 4 min read
Waterfall enrichment explained: how it works and where it breaks
Waterfall enrichment tries one data provider, then the next on a miss. How it works, why order matters, a prompt to run it with an agent, and the limits.
Walid Boulanouar · · 5 min read
Try it with the agent you already use
Start your workspace, top up, and paste one prompt into your agent.

