> ## Documentation Index
> Fetch the complete documentation index at: https://docs.miraday.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Where Candidates Come From

> The public talent sources, professional index, and your own contacts Mira can search, plus coverage and profile freshness.

Mira draws on several kinds of professional data about people and companies and evaluates what it finds against your criteria. Alongside public sources, you can ask it to search your own saved or imported contacts. Here's where that data comes from.

***

## What Mira draws on

| Source | What it covers |
| - | - |
| **Public talent data** | Aggregated from public platforms such as LinkedIn, X, GitHub, and Hugging Face, plus academic papers and company information, and from data providers such as Exa, Apollo, and RocketReach. |
| **MiraDay's own index** | A continuously updated index of public professional profiles and job postings. |
| **Your own contacts** | People you've saved or imported into [Contacts](https://docs.miraday.ai/en/docs/tools-and-teamwork/contacts.md), searched when you ask in a channel you own. Private contact records remain separate from public candidates. |
| **Mira Browser Extension** | For sites behind a sign-in or not in the index, [the extension](https://docs.miraday.ai/en/docs/tools-and-teamwork/mira-browser-extension.md) navigates them in your own browser, on demand. |

Mira reasons across all of these together, so a candidate can surface from evidence spread over more than one source, not just whoever happens to match a single database.

## How broad the coverage is

Coverage is global, across industries, regions, and seniority levels, from early-career to executive. MiraDay's index spans 4.5 billion public records. For any one search, what matters is whether the people who fit your criteria are in the data, not the raw size.

## How current the data is

Public data ages: people change jobs, and profiles aren't always updated the day they do. When you open a search step in the conversation, each person in that step's results shows a **freshness badge** marking when their data was last updated, for example "Updated · 3w ago", with the exact date on hover. When an update date isn't available, no badge is shown rather than a guess, and profiles updated within the last day don't show one either.

Use it as a signal: a very fresh profile is more likely to reflect someone's current role, while an older one is worth a second look or a quick confirmation before you reach out.

## What this means for your search

Because Mira reasons over evidence rather than pulling from one list, two things follow. If a search returns fewer people than you asked for, it's because fewer people in the available data met your must-have requirements, not because of a hidden cap. Loosen a requirement and you'll usually see more. And accuracy tracks how complete the public data is: the more a profile actually says, the more precisely Mira can assess it. For how that assessment works, see [How MiraDay Matches Candidates](https://docs.miraday.ai/en/docs/match-quality-and-trust/understanding-ai-matching.md).

## What's next

* [How MiraDay Matches Candidates](https://docs.miraday.ai/en/docs/match-quality-and-trust/understanding-ai-matching.md): how Mira reasons over this data to score each candidate.
* [Inside a Candidate Profile](https://docs.miraday.ai/en/docs/sourcing/candidate-profile.md): what each field on a candidate means.
* [Mira Browser Extension](https://docs.miraday.ai/en/docs/tools-and-teamwork/mira-browser-extension.md): reach sites and sign-ins that aren't in the index.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.