Skip to content
RankFabrik · data

● You know what's missing before you pay

Collected data, with its fill rate written on it.

Located businesses, job postings, video transcripts — and every email checked before you send it. Every collection API carries the percentage of fields actually filled, call by call; what's missing at the source arrives empty, never filled in by a model.

500 units a month, no credit card.

No code? Agencies: order a ready-made list of verified local leads →

200 GET /rechercher?q=boulangerie&ville=lyon
name"Boulangerie Saint-Vincent"
address"12 quai de la Pêcherie, 69001"
phone"+33 4 78 28 41 …"
website""
rating4.6
reviewsCount0
completeness — share actually filled in
address 100 %
phone 61 %
website 44 %
reviewsCount 0 %
6,012postings on a search where the public source stops at 1,000
123sfor that full sweep, duplicates removed
1.2sa whole Places area collected at call time, then deduplicated
€0billed on a call that returns no result

01Places

16 preloaded cities, ready to sweep

Local businesses and professionals, collected the moment you call.

Give a point and a radius, get back the records. Each response states what percentage of addresses, phone numbers and websites is actually filled in.

spacing 1.2 km seen 2×, counted 1× 18 places · 12 cells PL. 01 AREA GRID SC. 1:1

02Jobs

6 012 postings where the source returns 1,000

Job postings collected on demand, deduplicated on the identifier.

The public source stops at a thousand postings per search. By segmenting on publish window and by area, we reached 6,012 postings on the same query, in 123 seconds.

source cap · 1,000 positions 24h 1000 7d 1000 30d 1000 Lyon 1000 Lille 1000 rest 1012 6,012 postings · 123s · duplicates removed no request exceeds the cap PL. 02 SEARCH SEGMENTATION SC. 1:1

03Captions

50 videos per call, in a single batch

Transcripts of public videos, segmented and timestamped.

The text arrives with its time markers, segment by segment. A quote stays traceable back to the source video, down to the second.

introduction 00:00 demonstration 04:12 questions 11:38 segment · 00:05:47 chapters read once · timestamps already present PL. 03 TIMED BREAKDOWN SC. 1:1

04Verify

100 addresses per call, checked in parallel

Email address verification, without ever sending a message.

Syntax, disposable domain, MX records, then an SMTP dialogue cut before anything is sent. Four verdicts, each with its reason — never an opaque score.

one handshake · stops before a message is sent MX resolve mail exchanger CONNECT :25 HELO identify MAIL FROM <> RCPT TO name@domain.com verdict deliverable undeliverable risky unknown PL. 04 SMTP DIALOGUE SC. 1:1

04Why not an aggregator

An outage on our side never becomes an outage on yours.

An outage stays in its corner

The products share nothing: no entry point, no counter, no database. The day one stops, the others keep answering as if nothing happened — and your job in progress doesn't stop either.

One quota per product

A jobs sweep that runs wild doesn't eat into your transcription units. The counters don't talk to each other, which keeps the bill readable when several teams are calling.

The limits are in the contract

Every product sheet has a "what this service doesn't do" section. Review counts are always zero on Places — it's written before you buy, not discovered three weeks in.

Get a key, make a call, look at the fill rate.

It's the only test that matters: are the fields you need filled in on your own areas.