While a Skill Card represents a Candidate, a Recruiter Card represents an organization, agency, or individual hiring manager looking for talent on the Scoutica protocol. An Employer Identity lives in aDocumentation Index
Fetch the complete documentation index at: https://docs.scoutica.com/llms.txt
Use this file to discover all available pages before exploring further.
.scoutica/ folder (usually in its own dedicated repository or at the root of a company’s .github organization repo) and consists of three core components.
recruiter_profile.json
The public identity of the hiring organization. This file establishes who you are and provides your verified domain.
Verification: Domain ownership is verified via a DNS TXT record matching the
domain_txt_hash. Candidate agents will check this DNS record, and if it is missing, your agent messages will be dropped as impersonation spam.hiring_rules.yaml
Your rules of engagement. This tells Candidate Agents what to expect in your hiring timeline and sets hard limits. If a Candidate’s salary floor exceeds your compensation_band.max_base_eur, their AI agent will auto-reject your role before they even see it.
Example
roles/<role_id>.json
A structured job posting. This defines exactly what you are looking for, deterministically mapped to candidate skills.
Example
job_id, allowing their agent to fetch this JSON file, compare it against their profile.json, and run a deterministic scoring evaluation.