Key Terms

Here's what the key terms mean when you see them in Mira. No jargon, just what you need to know.

---

Agent

Mira's AI that executes tasks on your behalf. When you describe what you need, the Agent takes over: understanding requirements, searching, evaluating, and delivering results. Mira works independently on execution and involves you at key decision points.

Agent Team

A group of team members that work on one task together, in parallel, for a hard or long-running search. Mira can assemble a team on its own, or you can turn it on. See Agent Team.

Team member

A member of an Agent Team. Mira is the team lead; team members are the agents Mira brings in, each owning part of a task, such as sourcing, screening, or outreach.

Task

A conversation with the Agent. Most often it's a sourcing request: you describe a role and the Agent delivers candidates. But a Task can be any request you give Mira. Tasks are saved in the sidebar, so you can come back anytime, pick up where you left off, ask for more candidates, or adjust your criteria.

Skill

A reusable workflow. Type / in the task input to invoke a Skill instead of describing the same requirements from scratch; the Skill name appears as a chip in your message. Mira ships with built-in Skills, and you can create your own through conversation with skill-creator, import them as files, or manage them in your Skills settings.

Ideal Candidate Profile

A structured summary of your search that Mira proposes before searching, in three lists: Must-Have Requirements, Nice-to-Have, and Avoid. You review and edit it, and the search runs against it once you confirm.

Candidate pool

What you get back from a search: a curated pool of candidates who match your requirements. Each person comes with a name, current role, work experience, education, a Qualifications assessment of why they're relevant, and contact details.

In classic recruiting, a shortlist means the vetted final list of roughly 3 to 6 candidates left after outreach and screening. Mira's output is the broader, reasoned, sourced set, so we call it a candidate pool, not a shortlist.

Qualifications

Mira's per-candidate assessment for your search: it checks the candidate against your must-haves one by one, showing where they meet, partly meet, or fall short, with the evidence behind each, plus an overall fit label. It's specific to your search, not a generic bio.

MRE (Mira Reasoning Embedding)

MRE is the reasoning-based retrieval model behind Mira's sourcing. Most search tools match on surface similarity: they can tell that two profiles look related, but not why. MRE reasons first. When MRE reads your requirement, it works out what you're really asking for and which underlying signals to look for, then searches on that reasoning rather than on keywords or look-alikes. That's why you can describe a role in plain language:

• "5 years of experience": read from the actual career timeline, not a profile tag.
• "0-to-1 experience": understood as early-stage company building.
• "high-growth company background": inferred from company size, funding history, and growth trajectory.

Learn more in How Mira Matches Candidates.

Mira Browser Extension

A Chrome extension that browses the web on your behalf. It can log into LinkedIn, company websites, your ATS, and other platforms to search for candidates and gather information. Useful when you need data that's not in Mira's built-in sources. See Browser Extension.

Credit

The unit you "spend" when using Mira. Searches and contact reveals consume credits. You can see how many a task used in its task detail.