MoltSets alternative: BlitzAPI vs MoltSets, measured on the same list
Both providers were queried on the same 3,445 LinkedIn profiles on September 17, 2026. BlitzAPI returned a person for 3,115 of them, MoltSets for 2,915, and 2,730 came back from both. Those 2,730 are the only contacts where the two answers can be compared person by person: see the contacts both returned. The main measures are each counted on the whole list, or on what each provider returned.
This page is published by BlitzAPI, one of the 6 providers in the run. The reference every answer is scored against comes from none of them, and the rules were fixed before the run. How we test.
01
The main measures, side by side
On the three measures this run can test for separation, BlitzAPI is ahead on accurate records per 100, coverage and accuracy, and MoltSets on none.
BlitzAPIAhead on 3 of 3 tested
MoltSetsAhead on 0 of 3 tested
The measure the report ranks on
Accurate records per 100 contacts
per 100 queried · higher is better
BlitzAPI ahead by 38.7 pointsbeyond the combined interval of 3.0
BlitzAPI: 82.4Ahead
MoltSets: 43.7
Coverage multiplied by accuracy: out of every 100 contacts sent, how many came back with the right current employer and a matching title.
Coverage
a person returned at all
% of queried · higher is better
BlitzAPI ahead by 5.8 pointsbeyond the combined interval of 2.2
BlitzAPI: 90.4%Ahead
MoltSets: 84.6%
Accuracy
right current employer and a matching title
% of answered · higher is better
BlitzAPI ahead by 39.5 pointsbeyond the combined interval of 2.8
BlitzAPI: 91.2%Ahead
MoltSets: 51.7%
Wrong title
right employer, the title does not match
% of answered · lower is better
BlitzAPI lower by 11.6 pointsseparation not tested
BlitzAPI: 2.5%
MoltSets: 14.1%
Stale employer rate
an employer the person has left
% of answered · lower is better
BlitzAPI lower by 28.8 pointsseparation not tested
BlitzAPI: 4.4%
MoltSets: 33.2%
Show the exact numbers
| Measure | Counted on | BlitzAPIvalue ± margin | MoltSetsvalue ± margin | Gappoints | Reading |
|---|---|---|---|---|---|
| Accurate records per 100 contacts | per 100 queried | 82.4 ± 1.3 | 43.7 ± 1.7 | 38.7 | BlitzAPI ahead |
| Coverage | % of queried | 90.4% ± 1.0 | 84.6% ± 1.2 | 5.8 | BlitzAPI ahead |
| Accuracy | % of answered | 91.2% ± 1.0 | 51.7% ± 1.8 | 39.5 | BlitzAPI ahead |
| Wrong title | % of answered | 2.5% | 14.1% | 11.6 | Separation not tested |
| Stale employer rate | % of answered | 4.4% | 33.2% | 28.8 | Separation not tested |
In this run BlitzAPI is third of 6 on coverage, behind Apollo and Prospeo.
The 38 published segments, each read on coverage, accuracy, accurate records per 100 and the stale rate, make 152 segment-and-measure comparisons. MoltSets is ahead of or level with BlitzAPI on 5 of them, in 5 distinct segments. Exact ties are counted for MoltSets.
02
What a wrong answer is made of
Each provider's answers are broken down into four verdicts: right employer and title, right employer with a different title, stale employer, and unverifiable.
Of the answers MoltSets returns, 33.2% name an employer the person has left, against 4.4% for BlitzAPI.
BlitzAPI3,115 returned
MoltSets2,915 returned
04
After a job change
The same list, split by how long each person has held their current job. Read a column to compare the two providers at one job age, a row to follow one provider from the newest jobs to the oldest, and use the selector to change the measure.
On accurate records per 100, the two providers are furthest apart on 4 to 6 months (72 points) and closest on more than 12 months (23).
Measure
accurate records per 100 contacts queried, by months since the current job started
accuracy, the share of returned contacts carrying the right employer and title, by months since the current job started
coverage, the share of contacts the provider returned at all, by months since the current job started
stale rate, the share of returned contacts naming an employer the person has left. Lower is better
| Provider | 0 to 1n = 785 | 2 to 3n = 916 | 4 to 6n = 255 | 7 to 12n = 448 | 12+n = 1,041 | Shape |
|---|---|---|---|---|---|---|
| BlitzAPI | 65798311 | 7386868 | 9398950 | 9598971 | 9699970 | |
| MoltSets | 29368150 | 27338249 | 21248752 | 48568628 | 7383887 |
Reading aidweakest to strongest within a column. Bold marks the strongest value of the column.
05
What this page does not compare
- Work history. MoltSets returns about 1.0 role per profile, against 10.18 for BlitzAPI and 10.57 in the reference. On past roles the two endpoints differ in scope: a recall figure would measure what each one returns at all, not how well it returns it.
- Cost. Neither provider publishes a unit price that can be sourced and dated, so this page has no cost column and no billing unit.
- Separation. Three of the five main measures on this page carry a published confidence interval: accurate records per 100, coverage and accuracy. For the other two, the wrong title rate and the stale employer rate, the page prints the gap and says that the separation was not tested.
- Search. Both providers were handed the person, as a profile URL. A provider whose strength is finding someone from a name and a company is not measured on that strength here.
06
How each one was queried
- BlitzAPIPOST https://api.blitz-api.ai/v2/enrichment/person
- MoltSetsPOST https://api.moltsets.com/api/v1/reverse_linkedin_lookup
Each provider keeps the same colour in every figure and in every edition, from the first report it appears in. Colours follow the order providers first appear, then the alphabet, never the ranking, and the provider publishing the test never takes the colour closest to its own brand.
Full protocol, definitions, uncertainty rules, limits and the corrections policy: the methodology page. To contest a figure, write to antoine@blitz-api.ai with test id 2026-09-17_combined.
