Works with the tools your team already uses.

What does Headhunt.AI’s CSV export include for every candidate?

For every candidate, Headhunt.AI provides: candidate name, public profile URL, current and prior employer, title, tenure, full career history, education history, skill/industry/seniority indicators, ESAI Score (0–100), a written fit summary in your preferred language, every social media profile link we have on file (LinkedIn, X, GitHub, Facebook, Instagram), and a personalized bilingual draft scout mail. For Enterprise customers with their ATS integrated into Headhunt.AI through a database-level engagement, the export also carries every field your ATS records contained — email addresses, phone numbers, custom fields, internal notes — alongside the candidate intelligence we add.

Does Headhunt.AI’s own candidate database contain email addresses or phone numbers?

No. Headhunt.AI’s 4M+ Japan-focused profile database does not contain candidate email addresses or phone numbers, and we do not enrich, scrape, or look up contact information. We do provide every public-web social media profile link we have on file for each candidate (LinkedIn, X, GitHub, Facebook, Instagram), which is how recruiters typically initiate contact.

Can I have Headhunt.AI score my existing ATS records too?

Yes, as an Enterprise engagement — it is not a self-serve CSV upload. Integrating customer ATS data into Headhunt.AI requires database-level integration and preprocessing: we need to map your schema, normalize encoding and field types, handle deduplication against our 4M+ profile database, and stand up the pipeline that flows your records through scored searches. This is scoped per customer as part of an Enterprise engagement. Once the integration is in place, your records are scored against the same role criteria as the public-data pool, the candidate intelligence we have is added to your records, and the original fields you brought in — including email addresses, phone numbers, custom fields, and internal notes — remain preserved in the export. If you’re considering this for your team, please contact our team to scope the work.

Which social media profile links does Headhunt.AI provide?

For each candidate, Headhunt.AI provides every public-web social media profile link we have on file: LinkedIn (the majority of profiles), X (formerly Twitter), GitHub, Facebook, and Instagram. Coverage by source varies by candidate — engineers tend to have GitHub profiles, public-thinking professionals tend to have X, consumer-facing professionals tend to have Instagram. Where a link exists in our data, it is included in the CSV export.

Are direct API integrations available?

Direct integrations to leading ATS, CRM, and workflow tools are on our roadmap. Today, the universal CSV export works with any ATS, CRM, or workflow tool that can import a CSV file — which is effectively all of them. We’ll announce each direct integration as it ships. If your team has a specific tool you’d like us to prioritize, please get in touch.

Does Headhunt.AI send scout emails on my behalf?

No. Headhunt.AI generates draft scout email content for your team to review and use at your discretion. When you communicate with candidates — by email, by phone, by message, by any channel — you are the sender, and you are responsible for compliance with applicable laws including the Act on Regulation of Transmission of Specified Electronic Mail (特定電子メール法), the Act on the Protection of Personal Information (個人情報保護法), and the Employment Security Act (職業安定法).

If my ATS is integrated with Headhunt.AI, is my data isolated from other customers?

Yes. For Enterprise customers with their ATS integrated through a database-level engagement, your records are processed in your workspace only and are never pooled with other customers’ data or with our 4M+ Japan-focused profile database. Customer workspaces are isolated at the tenant level: your integrated records, your searches, your candidate shortlists, and your Screening Guidance settings are visible only to your team. They are never shared across customers, never used to train AI models for anyone else, and never disclosed to third parties without your written instruction.

For Enterprise ATS integration, is the data handling compliant with Japan’s APPI?

Yes, with the appropriate legal structure on both sides. When you integrate your ATS with Headhunt.AI through an Enterprise engagement, you remain the personal information handling business operator (個人情報取扱事業者) under Japan’s Act on the Protection of Personal Information (APPI / 個人情報保護法), and Headhunt.AI processes the data as your consigned party (委託先). This consignment relationship is exempt from APPI third-party transfer restrictions and is documented in our standard Data Processing Agreement (provided as part of the Enterprise engagement). The underlying platform operates from AWS Tokyo region — no cross-border data transfer — and Headhunt.AI is filed with Japan’s Ministry of Health, Labour and Welfare as a 第4号特定募集情報等提供事業者 under the amended Employment Security Act. The Article 30 buyer’s confirmation duty under the APPI applies when personal data flows from Headhunt.AI to you (e.g., from our 4M+ profile database); our regulatory filing is designed to satisfy that confirmation requirement.

As part of Enterprise ATS integration, are Japanese characters in custom fields handled correctly?

Yes. The standard data layer is UTF-8, so Japanese characters in any field — candidate names, company names, role titles, custom fields, internal notes, and free-text columns — pass through correctly without garbling. If your ATS exports in Shift-JIS or another legacy encoding (a common pattern with older Japanese HR systems), encoding conversion is handled as part of the integration preprocessing. Bilingual records (mixed Japanese and English in the same field) are also handled cleanly, including 全角/半角 character normalization where it matters for downstream matching.

Does CSV export consume credits, or is it included in my Headhunt.AI plan?

CSV export itself is included in every Headhunt.AI plan — there is no additional charge for exporting your results, and you can re-export the same workspace any number of times at no cost. Credits are consumed only by the candidate research itself: 1 credit = 1 ranked candidate who both passes your search criteria and scores 50 or higher on the ESAI Score. Candidates that fall below the score threshold do not consume credits and are not returned. For Enterprise customers with their ATS integrated, the enrichment of your records is included in the same credit-per-candidate cost; there is no separate enrichment fee.