company-research
Verifiedby exa-labs · Updated Apr 16, 2026
Company research using Exa search. Finds company info, competitors, news, financials, LinkedIn profiles, builds company lists. Use when researching companies, doing competitor analysis, market research, or building company lists.
See It In Action
I've read through the full project context — the doany.ai feature scope, vendor seed list, deliverable spec, and research skill definition. The task calls for Exa-powered live web research, but I don't have access to Exa (or any web search tool) in this environment. So I can't do live lookups for today's news.
What I can do: build the brief structure using the seed list and my training knowledge, clearly flag every claim's evidence strength, and mark anything I can't verify as uncertain. That way you have a usable skeleton that someone can spot-check with live sources in minutes.
Let me build it.
The brief is at COMPETITOR_BRIEF.md. Here's the short version:
Direct overlap: Exa and Tavily — both are developer-first retrieval APIs built for agent/RAG workflows, squarely in doany.ai's lane.
Partial overlap: Pinecone (especially if Assistant bundles ingestion+retrieval), Elastic (ESRE), Algolia (NeuralSearch), Weaviate, Brave. These serve adjacent buyers or cover a subset of the feature scope.
Adjacent: Cohere, Jina AI, Qdrant, SerpApi, Firecrawl — component vendors or different value props, but some (Cohere Compass, Jina convergence) could shift toward direct overlap.
Three items I'd flag as highest priority to verify with live sources before this goes to leadership:
- Pinecone Assistant — if it now bundles ingestion + reranking, it's direct overlap, not partial
- Cohere Compass — positioning is fuzzy; could be a hosted retrieval API or just an enterprise connector
- All "recent launch" dates — I couldn't run live Exa searches, so every date and product claim needs a quick spot-check
The brief follows the deliverable spec (Results table, Sources, Notes with uncertainty flags). It's ready to be enriched with live data whenever someone can run the Exa queries.
External Tools
| Tool | Type |
|---|---|
| exa | mcp |
Permissions
| Scope | Description |
|---|---|
| network:outbound |
SKILL.md
Company Research
Tool Restriction (Critical)
ONLY use web_search_advanced_exa. Do NOT use web_search_exa or any other Exa tools.
Token Isolation (Critical)
Never run Exa searches in main context. Always spawn Task agents:
- Agent runs Exa search internally
- Agent processes results using LLM intelligence
- Agent returns only distilled output (compact JSON or brief markdown)
- Main context stays clean regardless of search volume
Dynamic Tuning
No hardcoded numResults. Tune to user intent:
- User says "a few" → 10-20
- User says "comprehensive" → 50-100
- User specifies number → match it
- Ambiguous? Ask: "How many companies would you like?"
Query Variation
Exa returns different results for different phrasings. For coverage:
- Generate 2-3 query variations
- Run in parallel
- Merge and deduplicate
Categories
Use appropriate Exa category depending on what you need:
company→ homepages, rich metadata (headcount, location, funding, revenue)news→ press coverage, announcementspeople→ LinkedIn profiles (public data)- No category (
type: "auto") → general web results, deep dives, broader context
Start with category: "company" for discovery, then use other categories or no category for deeper research.
Category-Specific Filter Restrictions
When using category: "company", these parameters cause 400 errors:
includeDomains/excludeDomainsstartPublishedDate/endPublishedDatestartCrawlDate/endCrawlDate
When searching without a category (or with news), domain and date filters work fine.
Universal restriction: includeText and excludeText only support single-item arrays. Multi-item arrays cause 400 errors across all categories.
Public LinkedIn via Exa: category: "people", no other filters.
Auth-required LinkedIn → use Claude in Chrome browser fallback.
Browser Fallback
Auto-fallback to Claude in Chrome when:
- Exa returns insufficient results
- Content is auth-gated
- Dynamic pages need JavaScript
Examples
Discovery: find companies in a space
web_search_advanced_exa {
"query": "AI infrastructure startups San Francisco",
"category": "company",
"numResults": 20,
"type": "auto"
}
Deep dive: research a specific company
web_search_advanced_exa {
"query": "Anthropic funding rounds valuation 2024",
"type": "deep",
"numResults": 10,
"includeDomains": ["techcrunch.com", "crunchbase.com", "bloomberg.com"]
}
News coverage
web_search_advanced_exa {
"query": "Anthropic AI safety",
"category": "news",
"numResults": 15,
"startPublishedDate": "2024-01-01"
}
LinkedIn profiles
web_search_advanced_exa {
"query": "VP Engineering AI infrastructure",
"category": "people",
"numResults": 20
}
Output Format
Return:
- Results (structured list; one company per row)
- Sources (URLs; 1-line relevance each)
- Notes (uncertainty/conflicts)
FAQ
What does company-research do?
Company research using Exa search. Finds company info, competitors, news, financials, LinkedIn profiles, builds company lists. Use when researching companies, doing competitor analysis, market research, or building company lists.
When should I use company-research?
Use it when you need a repeatable workflow that produces text report.
What does company-research output?
In the evaluated run it produced text report.
How do I install or invoke company-research?
Ask the agent to use this skill when the task matches its documented workflow.
Which agents does company-research support?
Agent support is inferred from the source, but not explicitly declared.
What tools, channels, or permissions does company-research need?
It uses exa; channels commonly include text; permissions include network:outbound.
Is company-research safe to install?
Static analysis marked this skill as low risk; review side effects and permissions before enabling it.
How is company-research different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does company-research outperform not using a skill?
About company-research
When to use company-research
When you need to discover companies in a market segment or geography. When you want competitor analysis, company background, or recent company news. When building targeted company lists or finding public LinkedIn profiles via search.
When company-research is not the right choice
When you need direct CRM enrichment or guaranteed official financial data from private sources. When the task does not require web-based company research or search-driven discovery.
What it produces
Produces text report.