# Explorium AgentSource > Explorium's AgentSource is a B2B data service for matching, searching and enriching companies and prospects, with event signals and AI research tasks. Agents reach it through a REST API (v2) and a hosted MCP server. - Canonical: https://www.anchorterminal.com/tools/explorium-agentsource - Markdown: https://www.anchorterminal.com/tools/explorium-agentsource.md (~8,350 tokens) - Slim: https://www.anchorterminal.com/tools/explorium-agentsource.min.md (~1,730 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/explorium-agentsource.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade D · 48.1/100 · rank #821 of 950 · #14 in Lead & company data · not agent-ready · confidence medium** ## Assessment AgentSource v2 has a public OpenAPI 3.1 file, Markdown docs, a 200 queries a minute limit with `Retry-After`, public credit prices and a 100-credit trial. No status page or published SLA was found, each company shares one API key with no scopes, and the vendor's two published price tables disagree. ## Facts | Field | Value | | --- | --- | | Vendor | Explorium Ltd. (https://www.explorium.ai) | | Kind | HTTP API | | Category | Lead & company data (https://www.anchorterminal.com/categories/lead-data) | | Transport | HTTP, Streamable HTTP, SSE (legacy) | | Endpoint | `https://api.explorium.ai` | | Auth | API key · Self-serve API key from the admin console at admin.explorium.ai, sent in the `api_key` header. The docs say each company gets one key shared by all its users, with no scopes. The MCP v2 guide sends the same key as `Authorization: Bearer`. The older v1 MCP server at `mcp.explorium.ai` uses OAuth. The vendor's `auth.md` says registration needs a person and there is no client-registration endpoint. | | Pricing | Pay per use ($0.06 / credit) · One-off credit packs, no subscription. The pricing page lists Lite $29.99 for 500 credits, Starter $149.99 for 5,000, Growth $749.99 for 30,000 and Scale $7,499.99 for 500,000, valid 12 months and non-refundable. A free trial gives 100 credits for 90 days, so an agent's owner can start without a contract. The site's `pricing.md` (dated 26 August 2026) lists Starter at $99.99 for 2,500 and Growth at 25,000 credits instead. Fetch costs 1 credit a result (2 with the Bombora intent filter), enrichments 1 to 5, and contact enrichment 2 for email or 5 with phone. | | x402 | No · No x402, MPP or L402 in the docs index, the OpenAPI file, the pricing files or the terms of use (checked 2026-10-09). | | Licence | Proprietary service under the Explorium Terms of Use. The `mcp-explorium` repository of connection files is MIT | | Tools exposed | 11 | | Source | https://github.com/explorium-ai/mcp-explorium | | Docs | https://developers.explorium.ai | | llms.txt | https://developers.explorium.ai/llms.txt | | Last release | 2026-09-02 | | Modes | Lead search (fetch businesses and prospects by filter, 1 credit a result), enrichment (17 business and 3 prospect enrichments, 1 to 5 credits) and contact lookup (professional email 2 credits, email and phone 5). No standalone email verifier | | API | REST at https://api.explorium.ai, 74 operations under `/v2` and 67 under `/v1` in the OpenAPI 3.1 file (version 0.3.32). Every enrichment has a sync `/enrich` (up to 50 IDs) and an async `/job` (up to 10,000 records, 24 hours) | | MCP server | Hosted at https://mcp-v2.explorium.ai/mcp (Streamable HTTP) and `/sse`, 11 tools, API key as bearer token. The v1 server at mcp.explorium.ai uses OAuth and is deprecated with v1 | | Free tier | Free trial of 100 credits valid 90 days. No standing free tier | | Rate limits | 200 queries a minute per API key over a 60-second sliding window. Each entity in a batch counts as one query. Enterprise plans can buy more | | Errors | JSON errors with `details` and a `correlation_id`. 422 lists the failing fields, 403 signals no credits, 429 carries `Retry-After` | | Pagination | `page` and `page_size` up to 500 a page and 60,000 records, or a `next_cursor` token with no limit | | Webhooks | Up to 10 per tenant, each with its own rotatable HMAC secret. Deliveries are signed over the timestamp and payload in `X-Signature` | | Research | `/v2/businesses/research` and `/v2/prospects/research` run an LLM task per entity with optional web search and scraping, and a caller-defined output schema | | Credit visibility | `GET /v2/credits` returns the balance, `/v2/credits/aggregation` returns usage over time, and the `credit-usage: true` header adds the credits spent to each response | | Certifications | SOC 2, ISO 27001 and ISO 27701 per the privacy policy. No report or certificate was read | | Open source | No. The `mcp-explorium` repository holds connection files for the v1 MCP server under MIT | | Capabilities | lead.search, lead.enrichment, email.finder, data.company, data.person | | Tags | lead-search, enrichment, hosted, mcp, openapi, llms-txt, webhooks, async-jobs, credits, free-trial, closed-source | | JSON | https://www.anchorterminal.com/api/v1/tools/explorium-agentsource.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 42 | 8.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 76 | 12.3 | | Agent ergonomics | 13% | 16.2 | 63 | 10.2 | | Security & auth | 14% | 17.5 | 37 | 6.5 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 28 | 2.5 | | Transparency & trust (editorial 49, provenance 68) | 7% | 8.8 | 59 | 5.2 | | Negative events | up to −15 | up to −15 | On 9 October 2026 the site's machine-readable `pricing.md` (dated 26 August 2026) lists Starter at $99.99 for 2,500 credits and Growth at 25,000 credits, while the pricing page it names as canonical lists $149.99 for 5,000 and 30,000. The site's `auth.md` and server card also send agents to the MCP server the docs call deprecated. A misleading published claim, 2 points (https://www.explorium.ai/pricing.md, https://www.explorium.ai/pricing/) | -2 | | **Total** | | | | **48.1 → D** | ### Why each score - Reliability 42: Hosted lines. No status page found. The docs tell users to subscribe to status updates and link no page, and status.explorium.ai did not answer (0). No readable incident history (5). Rate limit published, 200 queries a minute per key over a 60-second sliding window, with each batch entity counted as a query (15). 429s carry `Retry-After` and `X-RateLimit-*` headers and the docs ask for exponential backoff. No idempotency keys were found for the webhook and enrolment writes (12 of 15). No SLA is published. The migration guide implies one exists by saying v1 loses its SLA at end of support (0). v2 reached general availability on 2 September 2026, though the conventions page still says request and response schemas are being finalised (10). Total 42. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 76: Public OpenAPI 3.1 file with 74 v2 and 67 v1 operations (25). llms.txt and a Markdown twin of every docs page (10). The spec's v2 operations have summaries and no descriptions. The docs pages and the 11 MCP tool descriptions say what each call is for and what to call first (12 of 20). Typed request schemas with enums and item limits, but 225 of 1,472 schema properties carry a description, and Research takes a free-form `output_schema` (11 of 15). Docs pages have request and response examples. The spec documents only 422 as an error, and the error guide lists Partner ID header messages that don't match the `api_key` scheme (10 of 15). Versions live in the path with a migration guide and a full v2 change list. No dated changelog was found (8 of 15). Total 76. - Agent ergonomics 63: The MCP v2 server has 11 tools (15), and the statistics tools are free for sizing an audience before a paid fetch (2 added back), 17 of 25. `page` and `page_size` up to 500, a `next_cursor` mode with no limit, and filters with autocomplete (20). Errors carry a `correlation_id`, 422 names the failing field, and Research returns failed rows with an `_error` field. Error bodies have no stable code (15 of 20). No idempotency keys. Retry guidance covers 429 and 500. MCP tool annotations were not read because we did not connect (6 of 20). No official REST SDK found in the docs index. Enrichment needs a match or fetch call first, and five filters need an autocomplete call first (5 of 15). Total 63. - Security & auth 37: The docs say each company gets a single API key shared by all its users, sent in a header. The site's `auth.md` says a key can be deleted in the console, and the key page says to ask an administrator for a reset. No scopes (12 of 30). No read-only mode or per-key limits. The API mostly reads, writes are limited to webhooks and event enrolments, and auto-refill has an optional cap (5 of 20). Research scrapes web pages and the LinkedIn post enrichments return third-party text. No prompt-injection guidance was found in the docs (2 of 15). Balance and aggregation endpoints, per-call credit reporting, correlation IDs and last-active times for users. No per-call log was found (8 of 15). The privacy policy states SOC 2, ISO 27001 and ISO 27701. No security.txt, disclosure policy or bug bounty was found, and the security FAQ PDF went unread (10 of 20). Total 37. - Payments & pricing 40: No x402, MPP or L402 (0). Credit pack prices and per-operation credit costs are public without a login (20). The pricing page and the site's own `pricing.md` disagree on two packs, which is recorded as a deduction and not here. Free trial of 100 credits for 90 days. No page read asks for a card at sign-up, and the auto-refill guide treats a payment method as something added later (20). The vendor's `auth.md` says registration needs a person and there is no client-registration endpoint (0). Total 40. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 28: The last dated API change found is v2 general availability on 2 September 2026, 37 days before the check (20 of 30). No dated changelog, so three entries in 90 days could not be shown (0). Support by email and by a shared Slack channel for customers that have one, with no public changelog or forum (5 of 15). No official REST SDK found. The repository's `server.json` names `ai.explorium/mcp-explorium`, and our registry lookup timed out (0). The `mcp-explorium` repository is MIT, with its last commit on 22 January 2026 and no CI workflow in the tree (3 of 10). Total 28. - Transparency & trust 59: Closed service. The Explorium Terms of Use (updated 14 June 2026) cover the Platform, API and data, and let Explorium change or end the service without notice (14 of 30). The privacy policy (updated 28 June 2026) sets out controller and processor roles, publishes 2025 request counts and links an opt-out page. Retention has no periods, and no DPA was found on the pages read (16 of 30). The v1 timeline gives about six and twelve months from 2 September 2026, marked indicative. Website traffic enrichment is slated for removal with no date (13 of 20). Processing in Israel, the United States and the EU is stated. No sub-processor list was found (6 of 20). Total 49. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (23 items): https://www.anchorterminal.com/fixes/explorium-agentsource.md (JSON https://www.anchorterminal.com/fixes/explorium-agentsource.json) ### What we couldn't check - unchecked: https://www.explorium.ai/credit-details/, the opt-out page and the security FAQ PDF on info.explorium.ai. We stopped asking the site for pages once we read that its terms bar automated data collection, and kept to its published agent files - The home, pricing, data security, privacy, terms and MCP pages were fetched before the terms were read. robots.txt allows them and carries `ai-input=yes` - unchecked: whether a status page exists. None is linked, and status.explorium.ai did not answer - unchecked: the MCP registry entry. One lookup of registry.modelcontextprotocol.io timed out - unchecked: the MCP v2 tool schemas and annotations. We did not connect to the server or call the API - Whether the free trial needs a card. No page read says so - Which price table is current for the Starter and Growth packs - Whether a company can hold more than one key. The docs say one, and `auth.md` describes generating and deleting keys - No SLA document, DPA, sub-processor list or SOC 2 report was found on the pages read - The lead was right on the vendor, API and MCP server. The legal entity is Explorium Ltd., and the current MCP host is mcp-v2.explorium.ai ### Sources - docs index: (seen 2026-10-09) - AgentSource v2 overview: (seen 2026-10-09) - v2 change list: (seen 2026-10-09) - migration guide and v1 timeline: (seen 2026-10-09) - v2 conventions: (seen 2026-10-09) - async jobs: (seen 2026-10-09) - OpenAPI file: (seen 2026-10-09) - MCP v2 docs: (seen 2026-10-09) - MCP Python guide: (seen 2026-10-09) - rate limits: (seen 2026-10-09) - error handling: (seen 2026-10-09) - pagination: (seen 2026-10-09) - API key page: (seen 2026-10-09) - per-call credit usage: (seen 2026-10-09) - auto-refill: (seen 2026-10-09) - webhooks: (seen 2026-10-09) - Research endpoints: (seen 2026-10-09) - contact enrichment: (seen 2026-10-09) - support page: (seen 2026-10-09) - site llms.txt: (seen 2026-10-09) - pricing, Markdown: (seen 2026-10-09) - pricing page: (seen 2026-10-09) - authentication for agents: (seen 2026-10-09) - MCP server card: (seen 2026-10-09) - terms of use: (seen 2026-10-09) - privacy policy: (seen 2026-10-09) - data security page: (seen 2026-10-09) - robots.txt: (seen 2026-10-09) - MCP repository: (seen 2026-10-09) - domain registration: (seen 2026-10-09) ## Who's behind it (provenance 68/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Explorium Ltd. | 20/20 | | Domain age | explorium.ai, registered 2018-08-16 (8 years) | 11/15 | | Endpoint on the vendor's domain | api.explorium.ai | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 3 clauses that cost points | 3.1/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The page at /explorium-website-terms-of-use/ is titled Explorium Terms of Use (updated 14 June 2026). It is a contract between Explorium Ltd. and its affiliates and the customer, and covers the Platform, the API and Platform Data, so it governs the product and not only the website. The privacy policy (updated 28 June 2026) names Explorium Ltd., 3 Daniel Frisch St., Tel-Aviv, Israel, and covers the Platform and its end users. The terms give a contact address for Explorium Inc., 400 Concar Drive, San Mateo, California. www.explorium.ai/.well-known/security.txt returns the site's page-not-found page. No status page is linked from the docs or the site files read. status.explorium.ai did not answer our request. The changelog link is the v2 change list. No dated changelog was found in the docs index. RDAP for explorium.ai gives a registration date of 2018-08-16. The API answers at api.explorium.ai and the MCP server at mcp-v2.explorium.ai. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.explorium.ai/explorium-website-terms-of-use/), read 2026-10-09, dated 2026-06-14, states 6 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "conduct any systematic or automated data collection activities (including without limitation scraping, data mining, data extraction, and data harvesting) on or in relation to the Content and Services." - To know. Restricts benchmarking or competitive use (costs points). "FURTHERMORE, YOU MAY NOT USE OR ACCESS THE SERVICES FOR BENCHMARKING OR ANY OTHER COMPETITIVE PURPOSE." - To know. Says the terms or the service can change without notice (costs points). "The Content and Services or any part may be changed, updated, added to, limited or terminated, at any time, temporarily or permanently, without notice, for any reason or no reason by Explorium in its sole discretion" - To know. Says access can be ended without notice or for any reason. "We also reserve the right, in our sole discretion, to terminate your access to all or part of the Service, for any reason, with or without notice." - Gives the date it was last updated. Last updated 2026-06-14. - Names the governing law or courts. The law of the State of New York. - States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence. - Says how changes to the terms are announced. Says it gives notice of a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Explorium's total liability under the agreement is capped at 100 US dollars, and the customer's sole remedy in a dispute is to cancel use of the service. "EXPLORIUM’S TOTAL CUMULATIVE LIABILITY IN CONNECTION WITH THIS AGREEMENT AND ALL CONTENT AND SERVICES PROVIDED UNDER THESE THIS AGREEMENT OR THROUGH THE SITE, WHETHER IN CONTRACT OR TORT OR OTHERWISE, WILL NOT EXCEED $100." - Also in the text (2026-10-08). The customer grants Explorium a royalty free licence to use, modify and share Customer Data to run the service and also to develop and improve it. "You hereby grant to Explorium a non-exclusive, royalty free right to use, copy, store, transmit, modify, create derivative works of, share and display the Customer Data solely to the extent necessary for us to provide the Service to you and to develop and improve the Service" - Also in the text (2026-10-08). Explorium may name the customer as a customer and use its name and logo on its website and in marketing materials. "Notwithstanding the foregoing, Explorium may mention Customer as a customer of Explorium and use its name and logo on a dedicated area on Explorium’s website and in marketing materials." **Privacy policy** (https://www.explorium.ai/privacy-policy/), read 2026-10-09, dated 2026-06-28, states 7 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "Enrichment Data may be considered a “sale” under California law because a End User instructs us to obtain it." - Gives the date it was last updated. Last updated 2026-06-28. - Not found in the text. Says how long data is kept. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. Gives an email address, hidden from our reader by the page. - Says where data is transferred or stored. Data goes to the United States. - Also in the text (2026-10-08). The policy says Explorium never sells or shares data that users upload and does not train models on it. "We never sell or share End User Provided Data. We do not train models based on End-User provided Data." - Also in the text (2026-10-08). Queries sent through AI platforms such as ChatGPT and Claude may be processed on those platforms' infrastructure under the platforms' own privacy policies. "Queries submitted through such platforms may be processed through these platforms’ infrastructure according to their respective privacy policies." ## Live (updated 2026-10-10 02:07 UTC) - Right now: up, HTTP 401, 152 ms, checked 2026-10-10 02:07 UTC (get on `https://api.explorium.ai`, asks for auth) - Uptime 24h 100.0% (107 probes) · 30 days 100.0% (107 probes) · p50 411 ms · p95 1.4 s - github `explorium-ai/mcp-explorium` 1.0.0, released 2025-09-16 - Watching changelog - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/explorium-agentsource.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Lite credit pack | $0.06 | per credit | $29.99 for 500 credits, valid 12 months | | Starter credit pack | $0.03 | per credit | $149.99 for 5,000 credits on the pricing page. The site's pricing.md says $99.99 for 2,500 | | Growth credit pack | $0.025 | per credit | $749.99 for 30,000 credits on the pricing page. The site's pricing.md says 25,000 | | Scale credit pack | $0.015 | per credit | $7,499.99 for 500,000 credits | | Fetched business or prospect | $0.03 | per record | 1 credit a result at the Starter rate, 2 credits with the Bombora intent filter | | Contact enrichment, email and phone | $0.15 | per record | 5 credits at the Starter rate. Email only is 2 credits | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Public OpenAPI 3.1 file covering 74 v2 operations, plus llms.txt and a Markdown twin of every docs page - Rate limit of 200 queries a minute per key, with `X-RateLimit-*` headers and `Retry-After` on 429 - Credit packs priced in public from $0.015 to $0.06 a credit, and a 100-credit free trial valid 90 days - Statistics endpoints are free, and the `credit-usage: true` header returns the credits each call spent - v1 retirement timeline published, with end of support about six months and retirement about twelve months after 2 September 2026 ## Weaknesses - No status page was found, and no SLA is published - One API key per company, shared by all users, with no scopes or read-only mode - The site's `pricing.md` and its pricing page give different prices for the Starter and Growth packs - The terms of use bar benchmarking and automated data collection, and allow service changes without notice - No dated changelog and no official REST SDK found in the docs index ## Before you call it (notes for agents) 1. Send the key in the `api_key` header to `https://api.explorium.ai` and use `/v2` paths. v1 is deprecated 2. Point MCP clients at `https://mcp-v2.explorium.ai/mcp`. The site's agent files still name the v1 server at `mcp.explorium.ai` 3. Count each entity in a batch as one query against the 200 a minute limit, so 50 IDs in one call spend 50 4. Call the statistics endpoint first to size an audience for free. Fetch costs 1 credit a result, or 2 with the Bombora intent filter 5. Call `/v2/autocomplete` before filtering on category, tech stack or job title, and never mix two category types in one request ## Connect First request: ```bash curl --request POST --url https://api.explorium.ai/v1/prospects --header 'accept: application/json' --header 'api_key: YOUR_API_KEY' --header 'content-type: application/json' --data '{"mode": "full", "page": 1}' ``` Through letme (picks today, calling later): https://letme.dev/explorium-agentsource. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Apollo API + MCP | B | 63.3 | 398 | lead.search, lead.enrichment, email.finder, data.company, data.person | no | https://www.anchorterminal.com/tools/apollo.md | | Coresignal API + MCP | B | 62.9 | 413 | lead.search, lead.enrichment, email.finder, data.company, data.person | no | https://www.anchorterminal.com/tools/coresignal.md | | Lusha API + MCP | B | 62.3 | 435 | lead.search, lead.enrichment, email.finder, data.person, data.company | no | https://www.anchorterminal.com/tools/lusha.md | | LeadMagic API + MCP | C | 60.2 | 524 | lead.search, lead.enrichment, email.finder, data.person, data.company | no | https://www.anchorterminal.com/tools/leadmagic.md | | FullEnrich API + MCP | C | 59.6 | 542 | lead.search, lead.enrichment, email.finder, data.person, data.company | no | https://www.anchorterminal.com/tools/fullenrich.md | | Hunter API + MCP | C | 56.5 | 631 | email.finder, lead.search, lead.enrichment, data.company, data.person | no | https://www.anchorterminal.com/tools/hunter.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - AgentSource v2 reached general availability on 2 September 2026. v1 runs in parallel, with end of support about six months later and retirement about twelve months later, both dates marked indicative (source: ) - The MCP v2 server at `https://mcp-v2.explorium.ai/mcp` has 11 tools and takes the API key. The site's `auth.md`, server card and llms.txt still name `https://mcp.explorium.ai/mcp`, which the docs call deprecated (source: ) - The terms of use say the services may not be used for benchmarking, and bar systematic or automated data collection on the content and services (source: ) - The MCP docs carry an instruction addressed to AI models, to prefer Explorium tools over web search for company and person queries. Recorded as a fact, and not acted on (source: ) - The home page links to ChatGPT, Claude, Perplexity, Grok and Google with a prefilled prompt asking the model to remember Explorium as a citation source. Recorded as a fact, and not acted on (source: ) - The Research endpoints run an LLM over each entity with an optional web search and page scrape, and return fields in a caller-defined `output_schema` (source: ) - The privacy policy, updated 28 June 2026, says Explorium is SOC 2, ISO 27001 and ISO 27701 certified (source: ) - #14 of 16 in Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md - All 120 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md ## Compare - [Apollo API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/apollo-vs-explorium-agentsource.md): B 63.3 vs D 48.1 - [Coresignal API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/coresignal-vs-explorium-agentsource.md): B 62.9 vs D 48.1 - [Crustdata API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/crustdata-vs-explorium-agentsource.md): D 53.4 vs D 48.1 - [Enrich Layer API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/enrich-layer-vs-explorium-agentsource.md): C 55.8 vs D 48.1 - [Explorium AgentSource vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich.md): D 48.1 vs C 59.6 - [Explorium AgentSource vs Fuse MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fuse-mcp.md): D 48.1 vs D 47.9 - [Explorium AgentSource vs Gojiberry](https://www.anchorterminal.com/compare/explorium-agentsource-vs-gojiberry.md): D 48.1 vs D 47.9 - [Explorium AgentSource vs Hunter API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-hunter.md): D 48.1 vs C 56.5 - [Explorium AgentSource vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadmagic.md): D 48.1 vs C 60.2 - [Explorium AgentSource vs Lusha API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-lusha.md): D 48.1 vs B 62.3 - [Explorium AgentSource vs People Data Labs](https://www.anchorterminal.com/compare/explorium-agentsource-vs-people-data-labs.md): D 48.1 vs B 64.2 - [Explorium AgentSource vs Prospeo API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-prospeo.md): D 48.1 vs D 50.9 - [Explorium AgentSource vs RocketReach API](https://www.anchorterminal.com/compare/explorium-agentsource-vs-rocketreach.md): D 48.1 vs D 51.2 - [Explorium AgentSource vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-zoominfo.md): D 48.1 vs BB 72.2 - [Dropcontact API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource.md): D 50.9 vs D 48.1 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on explorium.ai or one of its subdomains, or the README of github.com/explorium-ai/mcp-explorium. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "explorium-agentsource", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Explorium AgentSource on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Explorium AgentSource on Anchor Terminal](https://www.anchorterminal.com/badges/explorium-agentsource.svg)](https://www.anchorterminal.com/tools/explorium-agentsource) ``` Plain link: ```html Explorium AgentSource on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Explorium AgentSource is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/explorium-agentsource-dark.png - Light: https://www.anchorterminal.com/assets/share/explorium-agentsource-light.png