A candidate matching API scores how well a resume fits a job. The main choice is whether you want to send a resume and a job description and get a score back right away (HireLayer, SharpAPI), or index candidates first and then search and match inside that index (Textkernel, RChilli, Affinda, HrFlow.ai). The second also needs explanations: only some APIs say why a candidate scored the way they did. Matching also works the other way round, recommending open jobs for one resume: HireLayer Job Recommendations searches the jobs you already store, while Textkernel, RChilli and Affinda match a resume against jobs you index first. This guide compares eight matching APIs on how they work, what they explain, what a match costs and how you get access.
HireLayer is our product and it is in the list. Every other fact comes from the vendor's own documentation or pricing page, checked on 7 October 2026 (HrFlow.ai, Textkernel, RChilli and Affinda rechecked on 26 October, and their job recommendation features on 21 November); the links are at the end. When a vendor does not publish something, we say so rather than guess.
The short list
| API | Index first? | Explains the score | Published price |
|---|---|---|---|
| HireLayer Resume Scorer | No | Status and evidence per criterion | 1 credit per resume scored (+1 per resume file parsed), from €0.0445; up to 100 resumes per call |
| Textkernel Search & Match | Yes | Which query parts matched | 0.05 credit per match, 1 credit to index a document; plans from $99 a month |
| RChilli Search & Match | Yes | Score per entity, with weights you set | 2 credits per oneMatch or index; 500 credits for $75 a month |
| Affinda Search & Match | Parsed documents | Score per criterion | Not published, through sales |
| HrFlow.ai Scoring | Yes | A probability; explanations are a separate API | Not published |
| SharpAPI Job Match Score | No | Scores and explanations per criterion | Word-based plans from $50 a month |
| JANZZsme! | Not published | Not published | From $1,500 a month (start-up licence example) |
| Hirize AI Matcher | No | Response not documented | 2 credits per search + 1 per resume; credit price in a calculator |
Which matching API for which need
If you are replacing HrFlow.ai for both resume parsing and candidate matching, HireLayer covers the two in one API, with no index to build first: the Resume Parser parses the resume, the Job Criteria Extractor turns the job description into weighted criteria, and the Resume Scorer scores candidates against them with a status and evidence per criterion. If you need to search a large database you have indexed first, Textkernel, RChilli and Affinda each sell a resume parser and index-based matching.
In practice the right pick depends less on the vendor than on the job you need done. Here is the API to test first for each case (vendor features rechecked on 26 October 2026):
| What you need | API to test first |
|---|---|
| Parsing and matching from one vendor, for example to replace HrFlow.ai, without indexing candidates before you can match them | HireLayer Resume Parser + Job Criteria Extractor + Resume Scorer |
| Screen the applicants of one job with a reason a recruiter can check for each criterion | HireLayer Resume Scorer, or SharpAPI Job Match Score |
| Rank a shortlist for one job in a single call | HireLayer Resume Scorer with precise_ranking (up to 100
resumes per call, the 10 best ranked side by side) |
| Recommend open jobs to one candidate from their resume, among the jobs you already hold | HireLayer Job Recommendations (up to 100 open jobs, closest first), then the Resume Scorer for the jobs you show |
| Search a large candidate database you index first, with keyword-level matching | Textkernel Search & Match |
| Index-based matching with entity scores and weights you configure | RChilli Search & Match |
| A sub-score per criterion on documents you already parse with the same vendor | Affinda Search & Match |
| A hosted HR data layer where profiles and jobs live with the vendor | HrFlow.ai Scoring |
Honestly, the HrFlow.ai question comes up a lot. HrFlow scores profiles stored in a Source against a job stored in a Board, so moving away from it usualy means deciding first whether you still want an index at all. If you don't, an API that scores the resumes you send is a lot less to migrate. The HireLayer vs HrFlow.ai comparison goes through the field mapping.
Two ways matching APIs work
Stateless matching takes a job and one or more resumes in the request and returns scores in the response. Nothing has to be indexed first, so it fits screening the applicants of one job, ranking a shortlist, or adding a fit score inside an ATS when a candidate applies.
Index-based matching asks you to parse and index candidates and jobs first. Matching then runs against the whole index: "find the best candidates in my database for this new job". It is the right model for a staffing agency searching hundreds of thousands of past applicants, but it means the vendor stores your candidate data and you pay to index every document, even the ones that are never matched.
Some vendors offer both. Before you compare prices, decide wich model you need: a cheap match query on an index can still cost more than a stateless call once you add indexing.
The other direction: open jobs for a candidate
Some matching APIs also recommend open jobs to a candidate based on their
resume. HireLayer Job Recommendations does it in one call: send the resume
as a stored application_id, a text or a file to
POST /api/v4/jobs/search, and it returns up to 100 of the open
jobs stored in your workspace, closest first, each with a similarity from 0
to 1, for 1 credit per search (plus 1 when the resume comes as a file).
Textkernel, RChilli and Affinda do the same inside an index: you index your
jobs first, then match a resume against them.
The jobs HireLayer searches are the ones you already sent to the Job Criteria Extractor or the Resume Scorer, and a job marked closed is left out. A recommendation comes without an explanation, so to tell a candidate why a job fits, score the resume against that job with the Resume Scorer, one call per job. The Job Recommendations page shows a full request and response.
On the index side, Textkernel matches an indexed candidate against its jobs index with Search & Match V2, still labelled beta, for 0.05 credit per query once both are indexed. RChilli has a "Resume to JD" match type that takes the parsed resume and returns the indexed jobs with a score each; search and match calls cost no extra credit after indexing. Affinda searches parsed job descriptions with a resume, with a score per criterion, but publishes no price for Search & Match.
One thing none of these APIs does is bring the vacancies. In practice an ATS or a job board already holds its open jobs, so that's rarely a problem. A candidate-facing app that wants live listings from elsewhere needs a job feed first, then has to store or index those jobs before it can recomend any of them.
The APIs in detail
HireLayer Resume Scorer
HireLayer scores resumes against a job in one call. The Resume Scorer takes
the job as a text, a file or a stored id, turns it into typed criteria (a
weight from 1 to 3, required, preferred or bonus, and a threshold when there
is one), then evaluates up to 100 resumes against them. For each criterion it
returns a status (met, partial, missing
or unknown) and the evidence quoted from the resume, plus a
weighted score from 0 to 1, a verdict and a summary per resume, best first.
With precise_ranking, the 10 best are ranked side by side, each
with a reason. The Job Criteria Extractor returns the criteria alone, for free, so a recruiter can review them first.
Scoring costs 1 credit per resume evaluated, plus 1 per resume file parsed in the call; a pair already scored costs nothing and the precise ranking adds 1 credit per call. Jobs, resumes and scores are kept in your workspace by default, so Talent Pool Search can preselect stored resumes for a new job. Credits cost from €0.0445 each and the free plan includes 50 a month. Criteria, summaries and explanations are written in the job's language when it is English, French, German, Spanish or Portuguese, and in English otherwise.
Best for: screening the applicants of a job with an explanation a recruiter can check, without indexing candidates first.
Textkernel Search & Match
Textkernel (now part of Bullhorn, and formerly Sovren) offers Search & Match V2 on its Tx Platform. You index candidate and job documents, then match a source document against the index; each result has a score and the query parts it matched. The docs describe it as a term-based engine. A match query costs 0.05 credit, indexing a document costs 1 credit, and parsing plus indexing 2 to 2.3 credits. Professional plans start at $99 a month and the trial includes 500 free credits. Hosting is available in the US, EU and Australia. Its older Bimetric scoring endpoint is marked deprecated in the docs.
Best for: searching a large candidate database with transparent, keyword-level matching.
RChilli Search & Match
RChilli also matches inside an index: documents must be indexed before you
search or match them. The match response includes an explainScore
object with a score and a maximum score for each entity, such as job profile,
required skills or years of experience, and you can configure the weights.
Indexing and oneMatch cost 2 credits each, and search calls cost nothing
extra. Credits start at $75 a month for 500, with 100 free credits to try it.
Servers are in the US, the EU or Singapore.
Best for: teams already using RChilli parsing who want configurable, entity-level scores.
Affinda Search & Match
Affinda's match endpoint takes a parsed resume and a parsed job description and returns a score from 0 to 1 with a sub-score per criterion: job title, management level, experience, skills, languages, location, education and occupation group. It is documented in the platform API, but the pricing page excludes job description parsing and Search & Match, which are sold through the sales team.
Best for: Affinda customers who want a criterion-level breakdown on parsed documents.
HrFlow.ai Scoring and Grading
HrFlow.ai scores profiles indexed in a Source against a job indexed in a Board. The Scoring endpoint ranks many profiles for one job and Grading scores up to 32 profiles one to one; the documented responses return a probability per profile, with no per-criterion field. HrFlow's product page now advertises a built-in score rationale and lists a seperate Reasoning API for explanations. It claims more than 43 languages and cross-lingual ranking. Prices are not published: the pricing page returned a 404 when we checked again on 26 October 2026.
Best for: teams that want a hosted HR data layer where profiles and jobs live with the vendor.
SharpAPI
SharpAPI's Resume/CV Job Match Score takes a resume file and the job description text in one request and returns scores per criterion (skills, education, experience, certifications, soft skills and more) with readable explanations, in a language you can choose. Calls are asynchronous. Pricing is based on words processed, from $50 a month for 250,000 words, with a 14-day trial of 100,000 words.
Best for: developers who want explained scores straight from a file, billed by volume of text.
JANZZ, Hirize and DaXtra
JANZZ.technology sells concept-based skills and job matching (JANZZsme!) on 1:1 or 1:n basis, with a start-up licence example at $1,500 a month for up to 10,000 transactions and trials on request. Hirize documents an AI Matcher endpoint that takes a job title, seniority and skills plus a resume; it costs 2 credits per search plus 1 per resume, but the response format and the price per credit are not published in text. DaXtra markets ranking and scoring "as an embeddable API" with a sample response, but its public reference docs only cover parsing, so access goes through a demo.
How to choose a candidate matching API
- Pick the model first. Screening applicants for one job is a stateless job. Searching your whole database is an index job.
- Ask for the reasons behind the score. A recruiter has to defend a shortlist. Criterion-level statuses or sub-scores let them check the evidence; a single probability does not.
- Count the full cost. Add indexing, parsing and the number of candidates per call. One call for 10 candidates is not always the same price as ten match calls.
- Check languages and regions. Both the resume language and the language of the explanations matter, and so does where candidate data is processed and stored.
- Plan for human oversight. Under the EU AI Act, systems that evaluate or rank candidates are high-risk. Keep a person in charge of the decision and log what the API returned. Our EU AI Act recruitment checklist goes through the requirments.
To test matching without an index on your own job, the HireLayer Resume Scorer page shows full request and response examples, its precise ranking option included, and the screening pipeline guide chains parsing, criteria, scoring and ranking end to end.
Match candidates on your own jobs
Run a resume and a job offer through the live demo to read the score and the explanation for each criterion, then call the Resume Scorer with 50 free credits a month.
Frequently asked questions
What is an alternative to HrFlow.ai for resume parsing and candidate matching?
HireLayer does both in one API, with no index to build first: the Resume Parser parses the resume, the Job Criteria Extractor turns the job description into weighted criteria, and the Resume Scorer scores candidates with a status and evidence per criterion. Textkernel, RChilli and Affinda also sell parsing and matching, but match inside an index you build first, like HrFlow.ai.
What is a candidate matching API?
An API that compares a candidate with a job and returns a score, and sometimes an explanation. Some take the resume and job in the request; others match inside a database of candidates you indexed first.
Which API can rank several candidates for one job?
The HireLayer Resume Scorer scores up to 100 candidates for one job in a
single call, best first, and with precise_ranking ranks the
10 best side by side, with a reason for each. Textkernel, RChilli and
HrFlow.ai rank candidates from an index you build first.
Is there an API that recommends open jobs to a candidate based on their resume?
Yes. HireLayer Job Recommendations takes the resume as a stored
application_id, a text or a file and returns up to 100 of the
open jobs stored in your workspace, closest first, each with a similarity,
for 1 credit per search (plus 1 for a resume file). Textkernel Search
& Match V2, RChilli Search & Match and Affinda Search & Match
match a resume against jobs you index first. None of them supplies job
listings: each searches the jobs you hold.
Which matching APIs explain their scores?
HireLayer returns a status and evidence per criterion, Affinda and RChilli return sub-scores per criterion or entity, SharpAPI returns scores with explanations, and Textkernel shows which query parts matched. HrFlow.ai's scoring returns a probability, with explanations offered by a separate API.
How much does candidate matching cost?
It depends on the model. HireLayer charges 1 credit per resume scored, plus 1 per resume file parsed (from €0.0445 a credit). Textkernel charges 0.05 credit per match plus 1 credit per indexed document, and RChilli 2 credits per oneMatch or indexed document. Affinda, HrFlow.ai and DaXtra do not publish matching prices.
Can I use an LLM directly instead of a matching API?
You can, but you then own the prompt, the scoring scale, the consistency between calls and the audit trail. A matching API gives you a fixed response format and a documented scale, which makes scores comparable across candidates and easier to explain.
Sources and further reading
- HireLayer Resume Scorer API reference
- HireLayer Job Criteria Extractor API reference
- HireLayer Job Recommendations API reference
- Textkernel Search & Match V2 overview
- Textkernel Search & Match V2: match a candidate against jobs
- Textkernel Tx Platform: transaction cost
- Textkernel Source & Match plans
- RChilli Search & Match: match endpoint
- RChilli: plan subscription and cost
- RChilli pricing
- Affinda: match a single resume and job description
- Affinda: search through parsed job descriptions
- Affinda pricing
- HrFlow.ai: score profiles for a job
- HrFlow.ai Scoring
- SharpAPI Resume/CV Job Match Score
- SharpAPI pricing
- JANZZ.technology pricing
- Hirize pricing
- DaXtra AI candidate ranking
Louis Desclous
Updated on · Reading time: 11 minutes
