Sources
Where candidate data comes from.
Sources
Where Beesla Gets Candidate and Company Data
This page explains where Beesla sources candidate and company data from and how those sources are used. Understanding data sources helps teams evaluate coverage, reliability, and how results are generated.
Beesla is designed to retrieve professional data intentionally and transparently.
Types of Data Sources Beesla Uses
Beesla works with multiple categories of professional data sources.
These include:
- Publicly available professional profiles
- Public company information
- Role-relevant career and experience signals
Sources are chosen to support recruiting use cases, not mass data collection.
How Sources Are Used During Searches
When you run a search:
- Beesla agents query relevant sources based on your role description
- Candidate data is evaluated in context of the role
- Only relevant profiles are returned as results
Data is retrieved on demand, not preloaded or cached indiscriminately.
Each retrieval event corresponds to token usage.
Candidate Data Sources
Candidate information is based on:
- Public professional presence
- Career history and role information
- Experience signals relevant to hiring
Beesla does not require candidates to submit resumes or applications to be included in search results.
Company Data Sources
Company details are retrieved when you request them.
Company information may include:
- Company name and industry
- Size or stage indicators
- Public business context
Company data retrieval is separate from candidate searches and costs tokens only when requested.
Source Selection and Relevance
Beesla does not treat all sources equally.
Sources are evaluated for:
- Relevance to recruiting
- Data quality
- Signal strength
- Contextual usefulness
This helps reduce low-quality or misleading results.
What Beesla Does Not Do With Sources
Beesla does not:
- Aggregate personal data unrelated to professional context
- Continuously scrape data without user action
- Combine workspace data across customers
All sourcing activity is tied to explicit searches or requests.
Source Coverage Expectations
No sourcing tool has perfect coverage.
Beesla works best when:
- You are sourcing for professional roles
- You value signal over volume
- You want curated results rather than exhaustive lists
If coverage feels off, refining the role description often improves source selection.
Transparency and Control
Because sources are queried dynamically:
- You control when data is retrieved
- Usage is visible through token consumption
- Results reflect current role intent
This keeps sourcing activity intentional and auditable.
What’s Next
To understand how data is protected: