# Company Deep Research — AI Agent Dossier API (`logiover/company-deep-research-scraper`) Actor
One-call company intelligence dossier for AI agents: website meta, tech stack, socials, contacts, SEO basics, news signals, competitors and blog/RSS from a company name or domain. No API key, no browser.
- **URL**: https://apify.com/logiover/company-deep-research-scraper.md
- **Developed by:** [Logiover](https://apify.com/logiover) (community)
- **Categories:** Developer tools, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet
## Pricing
from $15.00 / 1,000 results
This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.
Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event
## What's an Apify Actor?
Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".
## How to integrate an Actor?
If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.
- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).
For usage examples, see the [API](#api) section below.
For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).
# README
## Company Deep Research Scraper — AI Company Intelligence & Enrichment API (No API Key)
    
Turn a **company name or domain into a complete, structured intelligence dossier** in one Actor run. Give it `stripe.com` (or just `"Stripe"`) and get back a clean JSON record with **website meta, tech stack, social profiles, contact emails & phones, SEO basics, recent news signals, competitor domains, JSON-LD firmographics (founded year, employee range, industry, HQ) and RSS/blog feeds** — aggregated from the site itself plus keyless public sources. **Batch up to 500 companies per run. No API key, no login, no headless browser.**
> ### 🏆 Why this company research scraper?
>
> **~40 fields per company** · **hundreds of dossiers per run** · direct HTTP + lightweight HTML parsing (no browser) · name→domain resolution · export to JSON / CSV / Excel. The unofficial **company enrichment API alternative** for AI agents, sales/rev-tech, CRM enrichment and market mapping — one call replaces five separate scrapers.
***
### ✨ What this Actor does / Key features
- 🧠 **Company identity** — name, description, logo, favicon, Open Graph / Twitter Card metadata, detected `languages`, `ogType`, canonical website URL.
- 🛠️ **Tech-stack fingerprinting** — 40+ technologies detected from HTML, script/stylesheet paths and HTTP headers: Next.js, React, Vue, Angular, Svelte, WordPress, Shopify, Webflow, Wix, Cloudflare, Vercel, Netlify, Google Analytics, GTM, HubSpot, Intercom, Segment, Stripe, Sentry, Datadog, Algolia, Tailwind and more.
- 🔗 **Social profiles** — LinkedIn, X/Twitter, GitHub, Facebook, Instagram, YouTube, TikTok, Discord and Telegram, from homepage links + `schema.org` `sameAs`.
- ✉️ **Contact channels** — emails (from `mailto:` + text regex, junk filtered) and phone numbers (from `tel:` + international regex).
- 📈 **SEO basics** — title tag, meta description, H1/H2 headings, plus `robots.txt` parsed for discovered `sitemapUrls`.
- 📰 **News signals** — recent company news (last ~30 days) via Google News RSS, each with title, URL, publish date and source.
- ⚔️ **Competitor discovery** — alternative/competitor domains mined from public search result pages, with junk domains (Wikipedia, social, etc.) filtered out.
- 🏢 **Firmographics from JSON-LD** — `schema.org` `Organization`/`Corporation` blocks parsed for `foundedYear`, `employeesRange`, `industry`, `country` and `city`.
- 📡 **RSS / blog feeds** — `` feed tags, blog links and common feed-path guesses (`/feed`, `/rss`, `/blog/feed`).
- ⚡ **Direct HTTP + JSON extraction** — pure fetch + HTML parsing on a small Node 20 container; no Playwright to keep warm, no GraphQL token.
- 🛡️ **Proxy support** — Apify datacenter proxy by default (avoids per-IP rate limits); optional `RESIDENTIAL` for bot-walled targets.
### 🚀 Quick start (3 steps)
1. **Configure** — pick a `mode` (`domain`, `name` or `single`) and paste your targets: a list of domains, a list of company names, or a single domain. Trim `sections` if you only need part of the dossier.
2. **Run** — click **Start**. The Actor resolves each company, enriches it in parallel and streams one dossier per company into your dataset.
3. **Get your data** — open the **Output** tab and export to **JSON, CSV, Excel or XML**, or pull it via the Apify API. Feed it straight into an LLM prompt, a vector DB or your CRM.
### 📥 Input
Pick a `mode`, then provide targets for that mode (`domains` / `domain` / `companyNames`). Everything else is optional.
#### Example — enrich a batch of domains (highest volume)
```json
{
"mode": "domain",
"domains": ["stripe.com", "linear.app", "figma.com", "notion.so", "vercel.com"],
"sections": ["meta", "techStack", "socials", "contacts", "seo"],
"concurrency": 5,
"useApifyProxy": true
}
```
#### Example — resolve company names → website → dossier (messy lead lists)
```json
{
"mode": "name",
"companyNames": ["Notion", "Figma", "Linear", "Vercel", "Supabase"],
"sections": ["meta", "techStack", "socials", "contacts", "news", "competitors"],
"concurrency": 4
}
```
#### Example — deep single dossier (all sections, max depth)
```json
{
"mode": "single",
"domain": "openai.com",
"maxNews": 15,
"maxCompetitors": 10
}
```
| Field | Type | Description |
|-------|------|-------------|
| `mode` | string | `domain` (batch enrich), `name` (resolve names → website → enrich), or `single` (one deep dossier). **Required.** |
| `domains` | array | Domains/URLs for `domain` mode, e.g. `stripe.com`, `https://openai.com`. Normalized automatically (protocol + `www` stripped). |
| `domain` | string | Single domain or URL for `single` mode. |
| `companyNames` | array | Free-text company names for `name` mode, e.g. `Notion`, `Figma`. Resolved to a website first. |
| `sections` | array | Dossier sections to collect: `meta`, `techStack`, `socials`, `contacts`, `seo`, `news`, `competitors`, `rss`. Fewer = faster & cheaper per company. |
| `maxNews` | integer | Max news items per company (0–50). |
| `maxCompetitors` | integer | Max competitor domains per company (0–30). |
| `concurrency` | integer | Parallel companies in batch modes (1–20). Lower for fragile targets. |
| `useApifyProxy` | boolean | Route requests through Apify datacenter proxy (AUTO). Recommended — avoids per-IP rate limits. |
| `proxyGroups` | array | Override proxy group, e.g. `["RESIDENTIAL"]` for bot-walled targets. Leave empty for datacenter. |
> **Which mode?** Use `domain` when you already have websites (fastest, batch up to 500). Use `name` when you only have messy company names from a form or CRM. Use `single` for one company you want fully enriched at maximum depth. The **output schema is identical** across all three.
### 📤 Output
One row per company — a complete **~40-field intelligence dossier**, exportable to JSON, CSV, Excel or XML. Here is a trimmed sample record:
```json
{
"input": "stripe.com",
"resolvedDomain": "stripe.com",
"websiteUrl": "https://stripe.com/",
"companyName": "Stripe",
"title": "Stripe | Financial Infrastructure to Grow Your Revenue",
"description": "Stripe is a suite of APIs powering online payment processing...",
"logo": "https://stripe.com/img/v3/home/social.png",
"favicon": "https://www.google.com/s2/favicons?domain=stripe.com&sz=64",
"languages": ["en-US"],
"ogType": "website",
"techStack": ["Next.js", "React", "Cloudflare", "Stripe", "Google Analytics", "Segment", "Sentry"],
"socials": [
{ "platform": "twitter", "url": "https://twitter.com/stripe" },
{ "platform": "linkedin", "url": "https://www.linkedin.com/company/stripe" },
{ "platform": "github", "url": "https://github.com/stripe" }
],
"emails": ["support@stripe.com"],
"phones": [],
"linkedinUrl": "https://www.linkedin.com/company/stripe",
"twitterUrl": "https://twitter.com/stripe",
"githubUrl": "https://github.com/stripe",
"youtubeUrl": "https://www.youtube.com/stripe",
"employeesRange": "5001-10000",
"foundedYear": 2010,
"industry": "Fintech",
"country": "US",
"city": "South San Francisco",
"seoTitleTag": "Stripe | Financial Infrastructure to Grow Your Revenue",
"seoMetaDescription": "Millions of businesses of all sizes use Stripe...",
"seoHeadings": ["Payments", "Online payments", "In-person payments"],
"sitemapUrls": ["https://stripe.com/sitemap.xml"],
"news": [
{ "title": "Stripe announces new product...", "url": "https://...", "publishedAt": "2026-06-28", "source": "TechCrunch" }
],
"competitors": ["paypal.com", "adyen.com", "braintreepayments.com", "square.com"],
"rssFeeds": ["https://stripe.com/blog/feed"],
"blogUrl": "https://stripe.com/blog",
"httpsValid": true,
"scrapedAt": "2026-07-06T12:00:00.000Z"
}
```
📋 Full field reference (click to expand)
| Field | Description |
|-------|-------------|
| `input` | The original name/domain you passed |
| `resolvedDomain` / `websiteUrl` | Canonical domain and final website URL (after redirects) |
| `companyName` / `title` / `description` | Company name, page title, meta/OG description |
| `logo` / `favicon` | Logo image URL and favicon URL |
| `languages` / `ogType` | Detected page languages; Open Graph type |
| `techStack` / `categories` | Detected technologies and tech categories |
| `socials` | Array of `{ platform, url }` social profile objects |
| `emails` / `phones` | Contact emails and phone numbers (junk filtered) |
| `linkedinUrl` / `twitterUrl` / `githubUrl` | Direct social URLs (flattened for easy filtering) |
| `facebookUrl` / `instagramUrl` / `youtubeUrl` | Direct social URLs |
| `employeesRange` / `foundedYear` | Employee-count range and founding year (from JSON-LD) |
| `industry` / `country` / `city` | Firmographics from `schema.org` `Organization` |
| `seoTitleTag` / `seoMetaDescription` / `seoHeadings` | SEO title, meta description, H1/H2 headings |
| `robotsTxt` / `sitemapUrls` | Raw `robots.txt` and discovered sitemaps |
| `news` | Array of `{ title, url, publishedAt, source }` recent news items |
| `competitors` | Competitor/alternative domains |
| `rssFeeds` / `blogUrl` | Discovered feed URLs and blog URL |
| `httpsValid` / `redirectChain` | HTTPS validity flag; URL redirect chain |
| `scrapedAt` | Scrape timestamp (ISO 8601) |
Tip: use the **Overview** dataset view to scan many companies at a glance, the **Social & contact** view for outreach lists, and the **News signals** view for monitoring.
### 💡 Use cases
- **CRM / lead enrichment** — feed a column of domains or company names and enrich each with industry, employee range, tech stack, LinkedIn and contact channels.
- **AI-agent grounding (RAG)** — give agents current, structured company facts instead of stale training-set knowledge; embed each dossier into a vector DB.
- **Sales & account research** — qualify accounts by stack, size and news momentum, then build a competitor set before outreach.
- **Market mapping** — build a landscape of hundreds of companies in a niche and cluster, filter and rank them as structured rows.
- **Vendor / tool evaluation** — compare candidate SaaS vendors by website, tech stack, docs and recent news in one pass.
- **Competitive & news monitoring** — schedule recurring runs over a watchlist and diff datasets to track tech, news and competitor movement.
### 👥 Who uses it
AI-agent & LLM-app builders (Claude, ChatGPT, Cursor, LangGraph, CrewAI, AutoGen tools) · sales & rev-tech / GTM teams enriching lead lists · growth and demand-gen agencies · market researchers & data journalists building company landscapes · investors & analysts doing lightweight due diligence · developers building an internal company database or MCP tool.
### 💰 Pricing
This Actor runs on a simple **pay-per-result** model — you're charged one `result` event per company dossier produced, with no separate Apify platform fees to calculate. Runs that yield zero companies (bad input, blocked target) are not billed. Try it on the **free tier** first, then scale up. See the **Pricing** tab on this page for the current rate.
### ❓ Frequently Asked Questions
**Is this a company enrichment / research API alternative?**
Yes. Instead of paying for a closed enrichment API, this Actor aggregates a company's own public homepage plus keyless public sources into one structured dossier — an unofficial **company enrichment API alternative** that returns machine-readable JSON with no API key.
**Does this Actor need an API key or a login?**
No. It uses only keyless public endpoints (public search for name→domain resolution, Google News RSS) and direct HTTP fetches of company websites. You just need an Apify account — no company logins, no third-party API keys.
**How do I export the data to CSV or JSON?**
Run the Actor, then export the resulting dataset as **CSV, JSON, Excel or XML** from the Apify console or via the Apify API. Each row is one company dossier.
**Is it legal to use this Actor?**
It fetches only publicly available web pages and keyless public APIs — it does not authenticate, bypass access controls or scrape behind logins. You are responsible for using the data in compliance with each website's Terms of Service and applicable laws such as GDPR.
**How much data can I get / how many companies per run?**
Practically unlimited — the Actor streams results and charges per dossier. `domain` mode accepts batches up to 500; concurrency is capped at 20 to stay polite. A few hundred companies per run is comfortable; for thousands, split into batches.
**How do I research a company when I only have its name, not the website?**
Use `name` mode. Pass free-text names like `"Figma"` or `"Linear"` and the Actor resolves each to its website first (via public search + favicon lookup), then enriches — perfect for messy CRM or form data.
**How accurate is the tech-stack detection?**
The fingerprint library covers 40+ of the most common technologies from client-side signals (script paths, framework markers) and server headers. It will miss server-only tech (databases, backend languages) and deeply bundled apps, but for vendor reconnaissance and quick triage it's reliable. For exhaustive Wappalyzer-grade detection, pair it with a dedicated tech-stack detector.
**Will it work on sites behind Cloudflare or a login wall?**
Homepages rarely block. If a target returns 403/503, the dossier is still produced with whatever fields could be collected and the domain recorded. For systematically walled targets, set `proxyGroups: ["RESIDENTIAL"]`.
**Does it find personal emails of employees?**
No. It collects contact emails published on the company homepage (support, info, press). For employee/person emails, use a dedicated LinkedIn or person-email Actor.
**Can AI agents call this directly?**
Yes — this is the primary design target. Expose it through an MCP server or an Apify tool integration; the agent passes a company name/domain and gets structured JSON back, with no browsing or HTML parsing on the agent side.
### 🔗 More AI & research scrapers by logiover
Building an AI research or company-intelligence pipeline? Pair this Actor with the rest of the ai-research-intel suite:
| Actor | What it does |
|---|---|
| [AI Deep Research](https://apify.com/logiover/ai-deep-research) | Multi-source, agentic deep-research reports on any topic |
| [AI Web Extract](https://apify.com/logiover/ai-web-extract) | LLM-powered structured extraction from any web page |
| [AI Web Search](https://apify.com/logiover/ai-web-search) | Programmatic web search results for agents & RAG |
| [News Intelligence Scraper](https://apify.com/logiover/news-intelligence-scraper) | Topic-level multi-source news + signals |
| [Google News Scraper](https://apify.com/logiover/google-news-scraper) | Google News articles by keyword, with dates & sources |
| [Competitor Ad Intelligence](https://apify.com/logiover/competitor-ad-intelligence) | Track competitors' ad creatives & spend signals |
| [GitHub Repository Scraper](https://apify.com/logiover/github-repository-scraper) | Repo metadata, activity and stats for a company's OSS |
| [npm Package Intelligence](https://apify.com/logiover/npm-package-intelligence-scraper) | npm package stats, deps and maintainer signals |
| [arXiv Paper Scraper](https://apify.com/logiover/arxiv-paper-scraper) | Academic papers, authors and abstracts for research |
| [SERP Keyword Research](https://apify.com/logiover/serp-keyword-research) | Search-engine result pages & keyword data |
| [CVE Security Advisory Monitor](https://apify.com/logiover/cve-security-advisory-monitor) | Track CVEs & security advisories for a vendor |
👉 Browse all **[logiover scrapers on Apify Store](https://apify.com/logiover)** — 180+ actors across real estate, jobs, crypto, social media & B2B data.
### ⭐ Support & feedback
Found a bug or need an extra field? Open an issue on the **Issues** tab — response is usually fast. If this Actor saves you time, a **★★★★★ review** on the Store page genuinely helps and is hugely appreciated. 🙏
### ⚖️ Legal
This Actor fetches only publicly available web pages and keyless public APIs. It does not authenticate, bypass access controls or scrape behind logins. It is intended for legitimate research, sales intelligence and AI-agent grounding on data that is already public. You are responsible for complying with each website's Terms of Service, `robots.txt`, GDPR and any applicable local laws.
***
### 📝 Changelog
#### 2026-08-01
- Completed the August 2026 full health check: verified empty/programmatic default, Console UI default, and two source-informed alternative inputs on Apify.
- Confirmed successful live execution, non-empty structured output, dataset-field/type integrity, and logical sample quality within the 5-minute quality window.
#### 2026-07-06
- ✨ README overhaul: badge row, ready-to-run example scenarios per mode, trimmed real-schema output sample with a collapsible full field reference, keyword-gap FAQ, and the ai-research-intel cross-promo grid.
#### 2026-07-02 — v1.0
- Initial release.
- 3 modes: `domain` (batch), `name` (resolve → enrich), `single` (deep).
- 8 dossier sections: meta, techStack, socials, contacts, seo, news, competitors, rss.
- 40+ tech-stack fingerprints.
- `schema.org` `Organization` JSON-LD parsing.
- Apify datacenter proxy by default, residential opt-in.
- Pay-per-result (`result` event per dossier).
# Actor input Schema
## `mode` (type: `string`):
How to read the targets. Leave everything empty to get a full sample dossier for a popular default company (stripe.com).
• **domain** — enrich one or many domains/websites (highest volume: batch up to 500)
• **name** — resolve a free-text company name to its website, then enrich
• **single** — deep dossier for one domain (all sections, maximum depth)
## `domains` (type: `array`):
Array of domains or URLs for **domain** mode, e.g. `stripe.com`, `https://openai.com`. Normalized automatically (protocol stripped, www stripped).
## `domain` (type: `string`):
One domain or URL for the deep **single** dossier mode.
## `companyNames` (type: `array`):
Array of free-text company names for **name** mode, e.g. `Notion`, `Figma`. The actor resolves each to a website first.
## `sections` (type: `array`):
Which dossier sections to collect. Each adds HTTP calls. Defaults to all. Uncheck to speed up batch runs.
## `maxNews` (type: `integer`):
Cap on news results per company (news section).
## `maxCompetitors` (type: `integer`):
Cap on competitor domains returned (competitors section).
## `concurrency` (type: `integer`):
Parallel companies in domain/name modes. Lower for fragile targets.
## `useApifyProxy` (type: `boolean`):
Route requests through the Apify proxy (AUTO group — Apify picks the best pool). Recommended — avoids per-IP rate limits. The actor also falls back to a direct connection on the final retry, so public APIs still work. Turn off only if you want direct connections everywhere.
## `proxyGroups` (type: `array`):
Override the proxy group, e.g. `RESIDENTIAL` for bot-walled targets. Leave empty for AUTO (recommended).
## Actor input object example
```json
{
"mode": "domain",
"domains": [
"stripe.com"
],
"domain": "linear.app",
"companyNames": [
"Notion"
],
"sections": [
"meta",
"techStack",
"socials",
"contacts",
"seo"
],
"maxNews": 5,
"maxCompetitors": 5,
"concurrency": 3,
"useApifyProxy": true,
"proxyGroups": []
}
```
# Actor output Schema
## `results` (type: `string`):
Full dataset of company intelligence records. One row = one company dossier.
# API
You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.
## JavaScript example
```javascript
import { ApifyClient } from 'apify-client';
// Initialize the ApifyClient with your Apify API token
// Replace the '' with your token
const client = new ApifyClient({
token: '',
});
// Prepare Actor input
const input = {
"mode": "domain",
"domains": [
"stripe.com"
],
"domain": "linear.app",
"companyNames": [
"Notion"
],
"sections": [
"meta",
"techStack",
"socials",
"contacts",
"seo"
],
"maxNews": 5,
"maxCompetitors": 5,
"concurrency": 3,
"useApifyProxy": true
};
// Run the Actor and wait for it to finish
const run = await client.actor("logiover/company-deep-research-scraper").call(input);
// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
console.dir(item);
});
// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs
```
## Python example
```python
from apify_client import ApifyClient
# Initialize the ApifyClient with your Apify API token
# Replace '' with your token.
client = ApifyClient("")
# Prepare the Actor input
run_input = {
"mode": "domain",
"domains": ["stripe.com"],
"domain": "linear.app",
"companyNames": ["Notion"],
"sections": [
"meta",
"techStack",
"socials",
"contacts",
"seo",
],
"maxNews": 5,
"maxCompetitors": 5,
"concurrency": 3,
"useApifyProxy": True,
}
# Run the Actor and wait for it to finish
run = client.actor("logiover/company-deep-research-scraper").call(run_input=run_input)
# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)
# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start
```
## CLI example
```bash
echo '{
"mode": "domain",
"domains": [
"stripe.com"
],
"domain": "linear.app",
"companyNames": [
"Notion"
],
"sections": [
"meta",
"techStack",
"socials",
"contacts",
"seo"
],
"maxNews": 5,
"maxCompetitors": 5,
"concurrency": 3,
"useApifyProxy": true
}' |
apify call logiover/company-deep-research-scraper --silent --output-dataset
```
## MCP server setup
```json
{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/?tools=logiover/company-deep-research-scraper",
"--header",
"Authorization: Bearer "
]
}
}
}
```
## OpenAPI specification
Download the OpenAPI definition: https://api.apify.com/v2/acts/eVE6D2e2JRHP2anZQ/builds/y6QJCMiCLCEd4QSGL/openapi.json