# Apollo API + MCP vs Dievio (slim)

> Apollo scores 63.4 (B) to Dievio's 43 (E) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/apollo-vs-dievio.md (~5,350 tokens) · this version ~3,130 tokens · JSON https://www.anchorterminal.com/compare/apollo-vs-dievio.json · canonical https://www.anchorterminal.com/compare/apollo-vs-dievio
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-10-31
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Apollo API + MCP scores 63.4 (B) on agent readiness against Dievio's 43 (E), and leads in 6 of 7 scored categories. Dievio leads on payments & pricing. Both do lead search.

- Apollo API + MCP: B 63.4, rank #463 of 1245 · https://www.anchorterminal.com/tools/apollo.min.md
- Dievio: E 43, rank #1090 of 1245 · https://www.anchorterminal.com/tools/dievio.min.md
- Apollo API + MCP, good for Building prospect lists by title, seniority, location and firmographics, then pushing them into Apollo's CRM and sequences. Ahead on Reliability, 65 against 28; Schema & documentation, 87 against 50; Maintenance & community, 58 against 28; Transparency & trust, 73 against 27.
- Dievio, good for Agents building small prospect lists by title, seniority, department, location, company size and industry at a low published price per lead, previewing the count for free first, and handing the user a CSV, JSON or JSONL file from a shared list without opening the dashboard. Ahead on Payments & pricing, 35 against 30. Also Free to start without a card.

| Category | Apollo API + MCP | Dievio |
| --- | --- | --- |
| Reliability (16%) | 65 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 50 |
| Agent ergonomics (13%) | 65 | 63 |
| Security & auth (14%) | 60 | 56 |
| Payments & pricing (10%) | 30 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 58 | 28 |
| Transparency & trust (7%) | 73 | 27 |

| Fact (where they differ) | Apollo API + MCP | Dievio |
| --- | --- | --- |
| Vendor | Apollo.io | Dievio |
| Hosted endpoint | `https://api.apollo.io/api/v1` | `https://dievio.com/api/public` |
| Licence | none | Proprietary hosted service under Dievio's Terms of Service (last updated 31 October 2026). No source is published; the only public code is a third-party MIT OpenClaw skill and an n8n template on GitHub |
| Tools exposed | none | 30 |
| MCP registry | `io.github.apolloio/apollo-mcp` | not listed |
| Terms last updated | 2026-08-10 | not read yet |
| Privacy policy last updated | 2026-08-10 | not read yet |
| Customer content may train models | yes | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 25 stars | none |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Transparency & trust, Apollo API + MCP +46: 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 (updated 10 August 2026) 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. 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).); Dievio 27 (Closed service. The terms (last updated 31 October 2026) cover use, credits, connected agents, a 30-day refund and availability in about 300 words but name no legal entity, address, governing law or jurisdiction, so the contracting party is unknown (8 of 30). The privacy policy (31 October 2026) lists the categories processed, the purposes, recipients by category, the agent connection data, and the access periods (authorization requests 10 minutes, codes 5, access tokens an hour, refresh 30 days, export links 15 minutes), says lead search uses Dievio's own contact database without saying where records are collected from, lets people in the database ask for access, correction, deletion or suppression by email, keeps records for as long as needed with no periods, and agrees with the terms and the docs on credits, revocation and link expiry; no DPA was found (14 of 30). No deprecation policy or notices; the terms allow the service to change at any time, and plan allowances and API prices changed between the 20 May and 31 October 2026 copies of the pricing pages with no dated notice (0 of 20). Service providers are named by category only (hosting, databases, authentication, contact processing, analytics, email delivery, payments), with no names, locations or transfer basis (4 of 20). 8+14+0+4 = 26.)
- Reliability, Apollo API + MCP +37: Apollo API + MCP 65 (Status page at status.apollo.io with eight components and incident history (20). The feed lists 15 entries since 7 July 2026. Most are short Background Jobs Latency downtimes of 30 to 49 minutes, but two ran over an hour (1 h 16 min on 3 August, 2 h 49 min on 6 September), and maintenance windows reached 9 h 35 min on 1 August. No component covers the REST API or the MCP server, so API outages wouldn't show (10). Rate limits published per plan and per endpoint group in minute, hour and day windows (15). 429s carry `retry-after`, and `error_details.suggestions` includes `retry_after_seconds`. 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).); Dievio 28 (Hosted reading, for the REST API with the MCP server it shares a database with. No public status page was found. None is linked from the docs or the footer, https://dievio.com/status answers 404 and status.dievio.com does not resolve (0). No readable incident history, so the floor (5). No rate limit is published for the REST API or the MCP tools. The only numbers are the export cap of 10 download starts a minute per connection and 100,000 contacts a file, the OAuth timers and input bounds such as 500 LinkedIn URLs a call, and the privacy policy mentions hashed rate-limit keys without a figure (5 of 15). No 429 or Retry-After is documented, and the REST errors are 401, 402, 500 and 502 with no retry guidance; every MCP mutation takes a request_id UUID replayed when retried with identical arguments, the workflows page says never to repeat a paid lookup with a new ID and to reconcile against the job list first, and a low balance returns fewer rows rather than failing, while a retried REST search has no idempotency key and is charged again (8 of 15). No SLA. The terms (last updated 31 October 2026) say uptime is not guaranteed and the service may change at any time (0). The REST API and the 30-tool MCP server carry no beta label, though the search response documents `search_id` as currently null and `counting` as currently false, and the server is unversioned (10). 0+5+5+8+0+10 = 28.)
- Schema & documentation, Apollo API + MCP +37: Apollo API + MCP 87 (OpenAPI 3.1 file at docs.apollo.io/openapi/apollo-rest-api.json, per the 30 September check (25). llms.txt with 51 links 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 holds a single entry dated 2026-09-18, and the API has no version scheme beyond v1 (10 of 15).); Dievio 50 (API reading, with the MCP server described. No OpenAPI or other machine-readable contract for the REST API; the MCP tool reference says clients discover exact input schemas through tools/list, that unknown fields and unlisted arguments are rejected, and the server publishes a dievio://schema/search-filters JSON resource, but no session was opened to read them (10 of 25). llms.txt and llms-full.txt on docs.dievio.com, generated on each build, plus llms.txt, pricing.md and product.md on dievio.com (10). The MCP reference says what each tool does, which tools are free, which scope each needs, when to prefer export_list_file over export_list and how to retry; the REST pages say what each endpoint returns and little about when to use search against lookup, and the MCP page says a preview does not unlock contacts and a count is not a guaranteed result (12 of 20). Filters are typed as strings, string arrays, booleans and integers with enumerations listed for seniority, department, employee size, business model, salary and email_status, bounds on page, limit, max_results and array length, and UUID ids; industries and locations are examples only, the funding dates are a year over REST and an ISO date over MCP, and the contact object for add_leads_to_list carries a free JSON lead_data field (10 of 15). curl examples with example responses for both REST endpoints, a pagination loop and six MCP worked prompts; errors are four status codes with one line each and no documented body, and the MCP error shape is not shown (8 of 15). No version in the path (/api/public), no changelog or release notes on either host, and plan allowances and API prices changed between the May and October 2026 copies of the pricing pages with no dated notice (0 of 15). 10+10+12+10+8+0 = 50.)
- Maintenance & community, Apollo API + MCP +30: Apollo API + MCP 58 (Newest changelog entry, structured API errors, on 2026-09-18 (30). Only one dated changelog entry in the last 90 days. The MCP plugin repo has commits on 20 July and 16 September, which aren't releases (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 repo has a registry publish workflow (5 of 10).); Dievio 28 (Closed service with no changelog, release notes or version numbers. The latest dated changes on the vendor's pages are the terms and privacy policy of 31 October 2026, which describe the agent integration, token lifetimes and export expiry, and blog posts of 21 and 30 October 2026 on API billing; the MCP server, absent from the February and May 2026 archived copies, carries no date, and the API landing pages say content reviewed May 2026 (20 of 30). No release record, so no three dated entries in 90 days; 84 dated blog posts from 29 March to 30 October 2026 are articles, not releases (0). Support is one address, support@dievio.com, with email support on Starter and priority support on Growth; no public changelog, community channel, forum or issue tracker, and the Fazier launch page's comments are from other makers (3 of 15). Not in the official MCP registry and no official SDKs (0). No packages to judge (5 of 10). 20+0+3+0+5 = 28.)
- Payments & pricing, Dievio +5: Apollo API + MCP 30 (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).); Dievio 35 (No x402, MPP or L402 in the docs, the pricing pages or the terms (0). Prices published without a login as dollars per 1,000 API credits ($4.50 at 5,000 down to $2.92 at 60,000), per plan ($29.99, $79.99 and $149.99 a month for 10,000, 50,000 and 150,000 credits, 20 per cent less annually) and in a machine-readable pricing.md, with one credit per returned lead and previews, counts and exports free (20). Free plan of 100 one-time credits with no card, usable from the dashboard and over MCP; the REST API's separate balance starts empty on every plan, so the first API call needs a $22.50 top-up (15 of 20). A person signs up in a browser, and the OAuth consent and API key creation both need the dashboard (0). 0+20+15+0 = 35.)