HireAbility resume parser (ALEX): what it does, and what it costs

Published 17 September 2026

The HireAbility resume parser is called ALEX — Automated Linguistic EXpert — and it is one of the oldest products in this category still being sold directly: HireAbility's own about page says the company was founded in 1999 in Londonderry, New Hampshire, and has been "dedicated to parsing the world's resumes, CVs and jobs for over two decades". ALEX takes a CV in almost any document format and returns HR-XML or JSON, with optional skills and job-title taxonomies layered on top. What it does not have is a published price: HireAbility's pricing page explains its philosophy in detail and states no number, so every purchase starts with a form and a conversation.

That is the short answer. The rest of this article is for the developer or product lead who searched hireability resume parser while choosing one: what ALEX actually returns, what the pricing page does and does not tell you, who should stay with HireAbility, and when a smaller API with a published per-parse price is the better-fitting choice.

We build ResumeJSON, a self-serve resume parsing API, so read this as written by an interested party. Every claim about HireAbility below was read from HireAbility's own pages as of September 2026 — its home page, its ALEX product pages, its integration documentation page, its about page, its trial page and its pricing page. Their pages are theirs to change, so check anything you are about to sign on.

HireAbility resume parser at a glance

HireAbility figures read from hireability.com as of September 2026. ResumeJSON plans are sold and metered through RapidAPI.

What ALEX actually extracts

ALEX is described on HireAbility's own product page as a grammar-based parser, not a statistical one:

"ALEX is a grammar-based parser using proprietary semantic parsing algorithms to understand and properly tag meaningful data in even the most unconventional and complicated resumes."

The inputs are wide. HireAbility lists Microsoft Word, PDF, Open Office, Microsoft Excel, HTML, RTF and plain text, plus social media profiles — the page names LinkedIn, Facebook and Twitter profiles specifically. Documents arrive either through the real-time web service or in bulk by email or FTP, including resumes sent as email attachments or pasted into the email body, which is a genuinely useful shape if your inbound CVs arrive as mail rather than as uploads.

The output is where ALEX differs most from a small JSON API. HireAbility publishes both an HR-XML schema (described as a superset of HR-XML, with Candidate in version 3.2 and Resume in version 2.5) and a JSON schema, and states that both are "fully customizable and new tags and extensions can be added if so desired", with any subset of tags returnable on request. Their home page claims 200+ data points extracted, and their integration page lists ready-made code samples for VB.NET, C#, PHP, Java, Ruby on Rails, Python and plain HTML POST, with new ones written on request.

The taxonomy is the part a plain parser does not have

ALEX's optional Intelligence module standardises skills, job titles, dates and locations against HireAbility's own ontologies, and their page gives the clearest published example of why that matters:

"AIX, Solaris, HP-UX, Linux, Ultrix, and others are children of the parent UNIX. With Hierarchies option enabled, ALEX would return 'UNIX' as a skill when one of the children of UNIX was identified."

A parser that only extracts gives you the string AIX. A parser with a hierarchy behind it can also tell your search index that this candidate knows UNIX, and that ABAP implies SAP implies ERP. If your product's value is matching or search rather than storage, that hierarchy is the thing you are buying, and no amount of clean extraction replaces it.

ALEX also produces what HireAbility calls a Candidate Snapshot Summary — most-used competencies, most recent employer, highest education level, years in management, years of experience and security clearance — which is a matching feature rather than a parsing one.

On data handling, HireAbility's pages state that resume and job data is never stored on their servers, that the service uses SSL, and that the company is GDPR compliant; their about page names Amazon AWS as the hosting provider.

What HireAbility pricing actually says

HireAbility's pricing page is unusual: it is an argument about pricing rather than a price list. Its own words, as of September 2026:

"Our philosophy at HireAbility is that clients should buy only what they need, no more and no less. We also believe that the more you parse the less you should pay per parse."

and, on mechanics:

"The price per parse declines rapidly as you buy larger packages. Packages are paid for in advance of services rendered, however monthly programs are available (with certain volume restrictions). All pre-paid packages purchased are valid for one year from payment receipt. Unused parsing credits expire at the end of twelve months."

So the shape is knowable even though the number is not. You buy pre-paid parse packages, the per-parse rate falls with package size, credits expire after twelve months, and you are told when you are within 20% of your remaining balance. The page also takes a clear swing at fixed-price annual contracts, and warns that being asked "what's your budget?" should be a red flag.

What that costs you as a buyer is time, not just money. To get a figure you fill in the trial form — name, company, corporate email, phone number, preferred output format and what you are integrating with — and someone gets back to you. The free trial is 30 parses valid for 30 days. If your question is "can I put CV upload into this sprint", the evaluation path is the cost, and it is the same cost at every quote-only vendor, DaXtra included.

Two things follow that are worth planning around:

• Pre-paid credits are a forecast. Buying a year of parses means guessing a year of volume. Guess high and unused credits expire; guess low and you are back in a purchase conversation mid-year.
• A number you cannot see cannot be compared. You can only put HireAbility beside another vendor after the sales cycle, which is exactly when switching is most expensive.

Who should stay with HireAbility

This is not a close call for several kinds of buyer, and pretending otherwise would waste your time:

• You need job posting parsing as well as CV parsing. ALEX Job Parser shares the same skills and job-title taxonomies, so vacancies and candidates come out in a comparable vocabulary. We do not parse job postings at all.
• You need a taxonomy or an ontology. Skills normalisation, job-title normalisation and parent/child hierarchies are a product in their own right, and a client-defined taxonomy is offered on top of theirs.
• You need HR-XML. If you are integrating with an HR system that speaks HR-XML, an API that returns its own JSON shape means you write and maintain the mapping.
• You need a customised schema. HireAbility will add tags and return subsets. Our schema is fixed for everyone.
• Your CVs arrive by email or FTP, or in large batches. ALEX handles mailbox and bulk ingestion. We take one document per request, so a back catalogue of 200,000 CVs is 200,000 calls.
• You need the parser inside your own network. Installed deployments are offered. Ours is a hosted endpoint only.
• You are buying with procurement. A vendor with 25 years of contracts, named hosting and an established compliance story answers a security review in a way a small API does not.

When a published per-parse price fits better

The opposite case is narrower but very common, and it is the one we built for: you are a developer adding CV upload to a job board, an applicant tracking system or a matching tool, you want fields rather than a platform, and you want to know the price before you talk to anybody.

Our published plans, as sold through RapidAPI: a free tier of 100 parses a month that is a hard cap and cannot bill you, a pay-per-use tier at $0.05 a parse with no monthly fee, $29 a month for 1,000 parses, and $99 a month for 5,000. Paid plans allow overage past the quota rather than blocking a working integration at it.

Both latency figures above are the vendors' own, and they are not measured the same way. HireAbility's "about 1 second" is theirs; our 2.2 s median is ours, measured against the live endpoint on a real two-page CV rather than in a lab, and every response carries the server-side time so you can check it yourself on your own documents. Take neither on faith — run ten of your own CVs through both trials, which costs nothing at either vendor.

What ResumeJSON is, and what it is not

A CV goes in as PDF, DOCX, plain text, or a JPEG, PNG or WebP photo or scan of the page; typed JSON comes out: name and contact details, every role with dates normalised to YYYY-MM, education, skills, certifications and languages. A role with no end date comes back with is_current: true, and a field the CV does not state comes back null rather than guessed — a caller cannot tell an invented value from a read one, so we do not produce them. A document that is not a resume returns 422 not_a_resume rather than an empty resume object. Upload limits are 20 MB and 60,000 characters.

What it does not do, stated here rather than discovered later: no skills taxonomy, no job posting parsing, no HR-XML, no schema customisation, no batch endpoint, no self-hosting, no data residency choice, no third-party security audit, no contractual SLA, and support is an email address. If one of those rows decides your purchase, HireAbility is a more complete product and this article is not going to change that.

How to compare the two this week

1. Collect ten real CVs — the awkward ones. Two-column layouts, a scan, a non-English document, one with a gap and one with a current role.
2. Request HireAbility's trial. Thirty parses over thirty days is enough for this test. Ask for JSON if that is what you would integrate; the form offers it.
3. Run the same ten through the free parser — no signup, no key — and read the JSON in the browser.
4. Compare fields, not impressions. Are the dates sortable? Is the current role marked current? Are missing fields empty or invented?
5. Then price it against your real volume. At a few hundred parses a month a published per-parse rate usually wins; at high volume with a taxonomy requirement, a package from a vendor like HireAbility usually does.

If you are still mapping the category, resume parsing software explains how enterprise platforms, self-serve APIs and open-source libraries are priced differently, and open source resume parser covers the case where you would run one yourself instead.