Recruitment data infrastructure (parsing, taxonomy, matching)
Primary sources checkedRChilli
APIs that turn a CV into structured, normalised fields and then match those fields to jobs, sold to the teams building recruitment software rather than to the recruiters using it.
The short answer
- Best for
- ATS vendors, job boards and enterprise HR teams that need structured candidate data inside a system they already own
- Not ideal for
- Recruiters looking for something to log into. There is no recruiter interface here, only endpoints
- Price
- No public rate card. Priced on parsing volume, quote only
- Closest alternative
- None selected yet
At a glance
- Recruitment fitStrong
- Ease of useUnknown
- ImplementationWeak
- Price transparencyWeak
- Value for moneyUnknown
- ScalabilityFair
Why these assessments
- Recruitment fitStrong
- Everything it does is recruitment-shaped: CV fields, skill taxonomies, job-to-candidate matching. It is infrastructure, but it is not general-purpose infrastructure.
- Ease of useUnknown
- There is no recruiter UI to judge, and SourcrLab has not built against the API. Developer experience is the thing to evaluate here, and we have not.
- ImplementationWeak
- This is a build, not a subscription. Somebody has to call the endpoints, map 140+ returned fields onto your own model, handle failures and own the result. Weak here means effort, not quality.
- Price transparencyWeak
- No rate card is published. Cost scales with parsing volume, which is exactly the number a buyer cannot estimate before seeing per-transaction pricing and minimums.
- Value for moneyUnknown
- Parsing accuracy on your own document mix is the only thing that decides this, and neither that nor the price is public. Both come out of a paid pilot, not a website.
- ScalabilityFair
- A transaction-metered API scales technically without a licensing renegotiation, but the same meter means a step change in applicant volume is a step change in cost.
Our reading of the evidence on this page. No score, no formula.
Where it sits
- Apply
- Data layer
- ATS
- Decision
The SourcrLab bottom line
A long-standing specialist in the least glamorous and most load-bearing part of a recruitment stack. The compliance posture is unusually well documented for this layer, the language and field coverage is broad, and the buying question is entirely about your own volume: parsing is metered per transaction and no rate card is published, so cost cannot be modelled without a conversation. Judge it on accuracy against your own document mix, not on the field count.
Best fit
You are building or operating recruitment software and need CVs turned into consistent fields, skills normalised against a taxonomy, and candidates matched to jobs, without writing and maintaining that yourself in thirty languages.
Think twice if
If nobody on your side owns an integration, this is the wrong shape of purchase. Buy an application that already has parsing inside it. RChilli gives you the engine, not the car.
SourcrLab assessment
Everything on this page comes from the vendor's own pages, checked on the dates below. SourcrLab has not used this product in real recruitment work, so you will not find a first-hand opinion here.
Why choose RChilli?
Parsing you would otherwise have to build
The documentation describes extraction into more than 140 structured fields across more than 30 languages. A team that has tried to write its own CV parser knows that the first 80 percent takes a fortnight and the remaining 20 percent never ends.
Taxonomy and matching on top of the same data
Parsing, a recruitment taxonomy and search-and-match are sold as parts of one family, so normalised skills feed the matching rather than being reconciled afterwards. That is the difference between structured data and merely extracted data.
The compliance answers already exist
The documentation states ISO 27001:2022, SOC 2 Type II, GDPR and HIPAA alignment and NYC AEDT compliance. For a supplier processing candidate documents that list is not marketing, it is the questionnaire your security team was going to send anyway.
Documented for the people who will integrate it
Public API documentation with code samples in Python, Java, C#, Ruby, PHP and Node.js means an engineer can size the work before procurement starts. Infrastructure vendors that hide their docs behind a sales call cost you a week finding that out.
Main trade-offs
There is no product here, only endpoints
Nobody logs in. Integration, error handling, field mapping, monitoring and everything the recruiter actually sees remain yours to build and keep working. Budget engineering time, not just licence cost.
The price is the volume, and the volume is unknown
Cost is metered on parsing transactions and no rate card is published. Before you can compare, you need per-transaction tiers, the minimum commitment, what happens on overage, and whether re-parsing an updated CV counts again.
Field count is not accuracy
140 fields and 30 languages describe coverage, not correctness. The number that matters is how the parser performs on the documents you actually receive, including the badly formatted PDFs and the two-column designer CVs. Test with your own corpus, not the vendor's samples.
Matching output is a hiring decision input
The moment a match score orders candidates, it shapes who gets seen. The NYC AEDT reference shows the vendor knows this, but the obligation to explain, audit and bias-test the outcome sits with you as the deployer, not with the API.
Pricing and buying reality
No public rate card. Metered on parsing volume, quote only
- RChilli documents its APIs publicly but does not publish an end-user price list on the reviewed product pages
- The commercial meter is parsing volume, so cost tracks applicant flow rather than recruiter headcount
- Third-party software directories quote figures for RChilli, but they are resellers' summaries rather than the vendor's own terms and should not be used as a benchmark
What we do not know
- Per-transaction rates and the volume tiers they step at
- Minimum annual commitment and what happens when you exceed it
- Whether taxonomy and matching are priced separately from parsing
- Pricing difference between cloud API and any on-premise deployment
Checked August 2026. We do not list a price we have not verified ourselves.
How it fits your stack
Works with
- An ATS or CRM you build or operate yourself
- Job boards and career sites that ingest applications
- HR technology products that need normalised candidate data
Likely replaces
- An in-house CV parser and the maintenance behind it
- Manual re-keying of candidate details from attachments
May overlap with
- Parsing already bundled inside a commercial ATS
- General-purpose document extraction services
Check before buying
- Accuracy on your own document mix, in your own languages
- Per-transaction pricing, tiers, minimums and overage behaviour
- Who owns explainability and bias testing once a match score orders candidates
- Where documents are processed and stored, and for how long
Used RChilli?
Tell other recruiters what worked, what did not, and who it suits. Positive, mixed or critical — all useful.
Evidence
- The product family covers resume parsing, recruitment taxonomy and search-and-match rather than an end-user application — checked against a primary source: RChilli solutions overview
- The parser is documented as extracting more than 140 fields across more than 30 languages — vendor claim, not independently verified: RChilli resume parser documentation
- ISO 27001:2022, SOC 2 Type II, GDPR, HIPAA and NYC AEDT compliance are stated in the product documentation — vendor claim, not independently verified: RChilli resume parser documentation
- API documentation with code samples in six programming languages is public — checked against a primary source: RChilli resume parser documentation
- No end-user rate card is published on the reviewed pages — checked against a primary source: RChilli solutions overview
- Parsing accuracy on a real-world European document mix — not enough evidence
- SourcrLab has not used this product in real recruitment work. — not enough evidence
Last reviewed: August 2026. How SourcrLab verifies information
Work at RChilli?
Email us to verify this profile or suggest a factual update.