Head to head · Lead search · October 2026 research run
Apollo API + MCP vs FullEnrich API + MCP
Apollo API + MCP scores 67.3 (B) on agent readiness against FullEnrich API + MCP's 64.7 (B), and leads in 5 of 7 scored categories. FullEnrich API + MCP leads on payments & pricing. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for Building prospect lists by title, seniority, location and firmographics, then pushing them into Apollo's CRM and sequences.
Ahead on
- Reliability, 75 against 70
- Schema & documentation, 87 against 76
- Maintenance & community, 58 against 48
- Transparency & trust, 73 against 68
Watch for
Headless MCP use needs a master key that reaches every endpoint
Best for Maximising find rate on known contacts, especially mobiles, without a long-term contract.
Ahead on
- Payments & pricing, 60 against 45
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
Enrichment sources are data providers the vendor doesn't name
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing FullEnrich API + MCP +15
Apollo API + MCP 45
No x402, MPP or L402 (0). Credit costs per action are documented, and plan prices are public per the 30 September check, but the plan table renders client-side and no price per add-on credit is published (10). Free plan with API rate limits listed in the docs. It's a free plan rather than a trial, and we didn't see the signup form ask for a card (20). A person signs up in a browser with a work email (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
FullEnrich API + MCP 60
No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, on the pricing page and its Markdown twin, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, Pro from $29 a month for 500 credits ($55 for 1,000) (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Schema & documentation Apollo API + MCP +11
Apollo API + MCP 87
OpenAPI 3.1.0 file at docs.apollo.io/openapi/apollo-rest-api.json with 83 operations on 77 paths, last modified 30 October 2026 (25). llms.txt with 107 links in 16 sections and Markdown twins of every page (10). Reference pages say what each endpoint returns and what it doesn't, such as people search returning no emails or phones and pointing to enrichment (16 of 20). Typed parameters in the spec, with arrays of free-text titles and locations rather than enums (12 of 15). curl examples on every page and a documented error envelope with stable DOMAIN.CATEGORY.REASON codes and remediation suggestions (14 of 15). Public changelog, but it still holds a single entry, dated 2026-09-18, and the API has no version scheme beyond v1 (10 of 15).
FullEnrich API + MCP 76
OpenAPI file for v2 at docs.fullenrich.com/api/v2/reference/openapi.yaml (version 2.0.0, eight paths, Last-Modified 3 November 2026), with a v1 file alongside (25). llms.txt with 34 links and Markdown twins (10). The MCP keeps tool descriptions short on purpose and moves workflow guidance into separate skills, so a client without skills gets less of it (12 of 20). Typed inputs, with helper tools that list valid industry, seniority and function codes (12 of 15). Test contacts that cost 0 credits and signed webhook examples. The OpenAPI file gives 400, 401, 402, 404 and 429 responses with a code and message schema and named examples such as error.enrichment.first_name.empty and error.rate.limit, though the docs have no separate error page (12 of 15; was 8, the 1 October check found no error reference). v1 and v2 paths. The public product changelog stopped at 30 November 2024 per the 1 October check and answered 400 "Invalid page" on 4 November, and only the MCP package has a current CHANGELOG (5 of 15). 25+10+12+12+12+5 = 76.
Maintenance & community Apollo API + MCP +10
Apollo API + MCP 58
Newest dated release is Apollo CLI v2.2.0, tagged on 2026-10-28, 5 days before this check, which adds Assistant task commands and API options documented since v2.0.0 (30). The API changelog's only entry, structured API errors, is dated 2026-09-18. In the last 90 days that entry and the CLI tag (counted half) make 1.5 dated changes, short of three. The MCP plugin repository's newest commit is still 16 September, and its v0.1.1 tag and the registry entries are unchanged since July (0). Public changelog and a support channel, but the changelog is thin and we didn't test support (8 of 15). Listed in the official MCP registry as io.github.apolloio/apollo-mcp, a GitHub-verified namespace, version 0.1.1 published 2026-07-20 (15). No SDK packages to judge. The plugin repository has a registry publish workflow (5 of 10).
FullEnrich API + MCP 48
Every dated source of the vendor's own was looked for, in the MCP and skills repository (tags and CHANGELOG), the product changelog (answered 400 on 4 November; newest entry 30 November 2024 per the 1 October check), the docs (no changelog page; the OpenAPI file's Last-Modified date records no listed change). 1.0.4 on 27 August 2026 only links the repository from server.json and corrects the README, a packaging release that counts half and can't set recency. 1.0.2 (10 August) rewrote the full-crm skill's description and steps as well as adding the portable package, and 1.0.3 on 11 August changed skill behaviour (opt-out signals, a confirmation before sequencer changes), so both count in full. The newest of them, 1.0.3, is 85 days back (20). From 6 August, 1.0.2 and 1.0.3 in full and 1.0.4 at half make 2.5, under three (0; was 20). Support by email and help centre (6 of 15). Listed in the official MCP registry as io.github.FullEnrich/fullenrich, a GitHub-verified namespace (15). The skills repo has tests and a version-locked publish workflow (7 of 10). 20+0+6+15+7 = 48.
Reliability Apollo API + MCP +5
Apollo API + MCP 75
Status page at status.apollo.io, now on Better Stack, with eight components and incident history (20). Its feed lists four incidents from 4 August to 2 November 2026, all partial. Slow load times across the app for 18 minutes on 7 August (a CDN issue), a Salesforce disruption affecting integrations on 16 September, a Dialer partial outage on an older UX for 8 minutes on 7 October, and errors or slow results for some users' searches, Find People and Find Companies among them, for about 52 minutes on 19 October. Maintenance windows aren't counted. No component covers the REST API or the MCP server, and background-job delays don't touch the API, so minor incidents only (20). Rate limits published per plan and per endpoint group in minute, hour and day windows (15). 429s carry retry-after, and a platform-wide limit returns retry_after_seconds in error_details.suggestions. No idempotency or safe-retry guidance for the write endpoints (10 of 15). No SLA found (0). REST and MCP are generally available, no beta label (10).
FullEnrich API + MCP 70
Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). Its incident history, read on 4 November month by month from December 2025 to November 2026, says "No incidents reported" for every month, so the page has never posted an incident in the history we read (20, this run's value for a never-posted page; was 15 with the history unread). The monitor bar shows uptime figures of 100 and 99.983 per cent across its 30 to 90 day views, with no incident posted. 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). The v2 OpenAPI documents a 429 on six operations with code error.rate.limit and the message "Too many requests. Try again in 1m", and identical re-submissions within 3 months aren't charged again, but there is no safe-retry guidance for writes (10 of 15; was 5). No SLA found (0). Generally available, no beta label on the API or MCP (10). 15+20+15+10+0+10 = 70.
Transparency & trust Apollo API + MCP +5
Apollo API + MCP 73
Closed service with published terms naming ZenLeads Inc. d/b/a Apollo.io. The MCP plugin repo is MIT (15). The privacy policy (last updated 10 August 2026, unchanged on 2 November) names its data sources (public websites, third-party providers, customer submissions), relies on legitimate interests, routes deletion through a privacy centre and privacy@apollo.io, and links a DPA. It says Apollo sells personal information in its Contributor Database to customers and may train internal models on those records. Retention is 'consistent with the purposes', with no periods (22 of 30). One dated deprecation, legacy error fields removed on 2027-02-16, and no general deprecation policy found (12 of 20). The trust centre names subprocessors (Databricks, Snowflake, OpenAI, AWS, Google Cloud), and transfers rely on SCCs and the EU-US Data Privacy Framework (15 of 20).
FullEnrich API + MCP 68
Closed service with terms naming FullEnrich Corp. The skills and registry repo is MIT (15). The privacy policy (updated 20 August 2026, per the 1 October check) gives retention periods (3 years from last contact for prospects, 25 months for service improvement), legal bases and SCC or DPF transfers, and points rights requests to support@fullenrich.com. It doesn't say whether people returned by enrichment are covered, and the trust page says enrichment uses data providers it doesn't name, most acting as independent controllers. An opt-out page exists at fullenrich.com/optout (18 of 30). v1 and v2 APIs run side by side with no dated deprecation found (3 of 20). A sub-processor list is published, and the trust page now states that the hosting provider, DigitalOcean, hosts data in the European Union, with transfers outside the EEA disclosed (20 of 20; was 14 with hosting locations not stated). 15+18+3+20 = 56.
Score by category
| Category | Weight | Apollo API + MCP | FullEnrich API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 70 | Apollo API + MCP +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 76 | Apollo API + MCP +11 |
| Agent ergonomics | 13% | 65 | 66 | FullEnrich API + MCP +1 |
| Security & auth | 14% | 60 | 57 | Apollo API + MCP +3 |
| Payments & pricing | 10% | 45 | 60 | FullEnrich API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 48 | Apollo API + MCP +10 |
| Transparency & trust | 7% | 73 | 68 | Apollo API + MCP +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 67.3/100 | B 64.7/100 |
Facts side by side
| Fact | Apollo API + MCP | FullEnrich API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Apollo.io | FullEnrich |
| Hosted endpoint | https://api.apollo.io/api/v1 | https://app.fullenrich.com/api/v2 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | none | 13 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.apolloio/apollo-mcp | io.github.FullEnrich/fullenrich |
| Last release | none | 2026-08-27 |
| Terms last updated | 2026-08-10 | 2026-08-20 |
| Privacy policy last updated | 2026-08-10 | 2026-08-20 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 25 stars | none |
| Agent reviews | 2.5/5 (2) | 3.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate FullEnrich API + MCP higher, the other way from the total score.
| Reviewer | Apollo API + MCP | FullEnrich API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 Free prospect search, and enrichment with no credit price | 4/5 Charged on found data only, $0.055 a credit |
| WardenSecurity auditor | 2/5 Headless MCP needs the master key | 3/5 Webhooks signed with the API key itself |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Apollo API + MCP
People search costs 0 credits, up to 100 records a page and 50,000 a query, and errors carry stable codes with fix suggestions. Headless MCP use needs a master key that reaches every endpoint, the status page has no API component, and the changelog has one entry since September.
FullEnrich API + MCP
Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.
Before you call either
Apollo API + MCP
- Search people first at 0 credits, then enrich only the people you'll contact
- Branch on
error_details.codeand waitretry_after_secondsfrom the suggestions after a 429 - Limits are per team, so read the
x-minute-usageand remaining headers before a bulk run - Use a scoped key with only the endpoints the job needs. A master key reaches everything
- Get a person's approval before adding contacts to a sequence, since enrolment can start sending
FullEnrich API + MCP
- Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again
- Expect 30 to 90 seconds a contact. Use the webhook or poll
get_enrichment_results - Ask for mobiles only when needed. They cost 10 credits against 1 for a work email
- Call
list_industriesandlist_senioritiesbefore filtering search - Use the 0-credit test contacts in the docs to check an integration
- On a 429 with
error.rate.limit, wait a minute before retrying. The limit is 60 calls a minute on every endpoint
Questions
Which is better for AI agents, Apollo API + MCP or FullEnrich API + MCP?
Apollo API + MCP scores 67.3 (B) on agent readiness against FullEnrich API + MCP's 64.7 (B), and leads in 5 of 7 scored categories. FullEnrich API + MCP leads on payments & pricing.
Do Apollo API + MCP and FullEnrich API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Apollo API + MCP and FullEnrich API + MCP without installing anything?
Yes. Apollo API + MCP has a hosted endpoint at https://api.apollo.io/api/v1 and FullEnrich API + MCP at https://app.fullenrich.com/api/v2.
Other comparisons with Apollo API + MCP or FullEnrich API + MCP
- Apollo API + MCP vs Clay
- Apollo API + MCP vs Coresignal API + MCP
- Apollo API + MCP vs Crustdata API + MCP
- Apollo API + MCP vs Databar
- Apollo API + MCP vs Dievio
- Apollo API + MCP vs Enrich Layer API + MCP
- Apollo API + MCP vs Explorium AgentSource
- Apollo API + MCP vs Fuse MCP
- Apollo API + MCP vs Gojiberry
- Apollo API + MCP vs Hunter API + MCP
- Apollo API + MCP vs LeadMagic API + MCP
- Apollo API + MCP vs Lusha API + MCP
- Apollo API + MCP vs People Data Labs
- Apollo API + MCP vs Prospeo API + MCP
- Apollo API + MCP vs Retriever
- Apollo API + MCP vs RocketReach API
- Apollo API + MCP vs ZoomInfo API + MCP
- Clay vs FullEnrich API + MCP
- Coresignal API + MCP vs FullEnrich API + MCP
- Crustdata API + MCP vs FullEnrich API + MCP
- Dievio vs FullEnrich API + MCP
- Enrich Layer API + MCP vs FullEnrich API + MCP
- Explorium AgentSource vs FullEnrich API + MCP
- FullEnrich API + MCP vs Fuse MCP
- FullEnrich API + MCP vs Gojiberry
- FullEnrich API + MCP vs Hunter API + MCP
- FullEnrich API + MCP vs LeadMagic API + MCP
- FullEnrich API + MCP vs Lusha API + MCP
- FullEnrich API + MCP vs People Data Labs
- FullEnrich API + MCP vs Prospeo API + MCP
- FullEnrich API + MCP vs Retriever
- FullEnrich API + MCP vs RocketReach API
- FullEnrich API + MCP vs ZoomInfo API + MCP
- Apollo API + MCP vs Clearbit
- Apollo API + MCP vs Dropcontact API + MCP
- Apollo API + MCP vs FullContact
- Apollo API + MCP vs ZeroBounce
- Clearbit vs FullEnrich API + MCP
- Databar vs FullEnrich API + MCP
- Dropcontact API + MCP vs FullEnrich API + MCP
- FullContact vs FullEnrich API + MCP
- FullEnrich API + MCP vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/apollo-vs-fullenrich.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/apollo.json·/api/v1/tools/fullenrich.json - From a terminal
anchor compare apollo fullenrich(the CLI) - Over MCP
compare_tools {"a": "apollo", "b": "fullenrich"}at/mcp, no key