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.
● You know what's missing before you pay
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 →
01Places
16 preloaded cities, ready to sweepGive a point and a radius, get back the records. Each response states what percentage of addresses, phone numbers and websites is actually filled in.
02Jobs
6 012 postings where the source returns 1,000The 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.
03Captions
50 videos per call, in a single batchThe text arrives with its time markers, segment by segment. A quote stays traceable back to the source video, down to the second.
04Verify
100 addresses per call, checked in parallelSyntax, disposable domain, MX records, then an SMTP dialogue cut before anything is sent. Four verdicts, each with its reason — never an opaque score.
04Why not an aggregator
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.
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.
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.
It's the only test that matters: are the fields you need filled in on your own areas.