Add to ChromePurchased contact and company data use credits separately from Free Mode. Check the lookup cost before enriching a large list. For website research without a paid lookup, start with public company pages. Compare plans.
rtrvr Enrich appends external data to your extracted results and sheets by matching them against Bright Data's dataset marketplace — LinkedIn people and companies, Crunchbase, Instagram, Amazon, Zillow, Indeed, and Google Maps. It runs inside a code plan via the rtrvr.enrich(...) helper. Your first 1,000 enrich records and web searches each month are free (one shared allowance), and anything beyond that bills automatically in credits at cost — no approval prompts.
Available Datasets
Reference a dataset in a plan with the rtrvr.datasets constants (e.g. rtrvr.datasets.linkedinPeople). The links below open each dataset's page in the Bright Data marketplace.
| Dataset | rtrvr.datasets key | Modes |
|---|---|---|
| LinkedIn people profiles | linkedinPeople | Instant lookup + Live scrape |
| LinkedIn people + business contact info (emails) | linkedinPeopleContact | Instant lookup only (a live scrape on it is served by linkedinPeople — profile fields, no email/phone) |
| LinkedIn company information | linkedinCompanies | Instant lookup + Live scrape |
| Crunchbase companies | crunchbaseCompanies | Live scrape only |
| Instagram profiles | instagramProfiles | Live scrape only |
| Amazon products | amazonProducts | Live scrape only |
| Zillow properties | zillowProperties | Live scrape only |
| Indeed job listings | indeedJobs | Live scrape only |
| Google Maps businesses | googleMaps | Live scrape only |
Fields
Each dataset exposes dozens of fields. The most commonly used ones are below — call field discovery (rtrvr.enrich({ dataset, fields: true }), free) to get the full, live list before you filter, since wrong field names fail the job.
| Dataset | Key fields |
|---|---|
linkedinPeople / linkedinPeopleContact | id (profile slug — the lookup key), url, name, position (role/title), current_company_name, city, about (bio), experience. The contact variant adds email and cellphone_number — partial coverage, most profiles return null for both. |
linkedinCompanies | url, name, website, industries, company_size, headquarters |
crunchbaseCompanies | Company profile fields — name, about, industries, founded date, size, region, website, socials — use field discovery for the full list |
instagramProfiles | Profile fields — profile name/id, followers, posts, website, bio, verification — use field discovery for the full list |
amazonProducts | asin, url, title, brand, initial_price, currency, availability, reviews_count, categories — 113 fields in total, use field discovery |
zillowProperties | zpid, url, address, price, bedrooms, bathrooms, homeStatus, yearBuilt — 140 fields in total, use field discovery |
indeedJobs | jobid, url, job_title, company_name, location, salary_formatted, job_type, date_posted_parsed, description_text |
googleMaps | place_id, url, name, address, category, reviews_count, open_hours, business_details |
Two Modes: Instant Lookup vs Live Scrape
Enrichment runs one of two ways. Instant lookup queries Bright Data's pre-collected index and is the default for people and company enrichment; live scrape fetches fresh data on demand for exact URLs or datasets the index doesn't serve.
| Instant Lookup | Live Scrape | |
|---|---|---|
| API | Bright Data Search API | Web Scraper API (/scrape, sync) |
| Speed | Sub-second | ~10–30s per input |
| Cost | Free up to the monthly allowance, then 0.25 credits / returned record | Free up to the monthly allowance, then 0.15 credits / successful record |
| Datasets | The 3 LinkedIn datasets only | Any scraper-backed dataset (Amazon, Zillow, Indeed, Google Maps, Crunchbase, Instagram) |
| How to call | { dataset, filter, fields } | { dataset, scrapeUrls, fields } |
| Best for | Bulk lookups by field (e.g. profile id) | Exact URLs, non-LinkedIn data, or lookup misses |
| Limits | Pass all keys in one in filter — batching is server-side | Max 20 inputs per call — chunk larger lists with rtrvr.mapLimit |
Slow Scrapes: Pending Jobs
Bright Data serves a scrape inline only while it fits their one-minute window. A heavier job (20 Zillow listings, say) hands back a job handle instead, and the call returns { pending: true, snapshotId } having billed nothing. Do other work, then collect the records later in the same plan:
let { records, pending, snapshotId } = await rtrvr.enrich({
dataset: rtrvr.datasets.zillowProperties,
scrapeUrls: listingUrls, // max 20 per call
fields: ['zpid', 'address', 'price', 'bedrooms'],
});
// ...do other free work here while Bright Data finishes...
if (pending) {
({ records, pending } = await rtrvr.enrich({ collect: snapshotId, fields: ['zpid', 'address', 'price', 'bedrooms'] }));
}
// Never re-scrape a pending job — collecting it is how you avoid paying twice.Cost & Credits
- 01
Free allowance — your first 1,000 records each month are free. Enrich records and web searches draw from one shared allowance, which resets on your account's renewal date.
- 02
Instant lookup — 0.25 credits per returned record beyond the allowance; zero matches cost nothing.
- 03
Live scrape — 0.15 credits per successful record beyond the allowance; failed inputs are free.
- 04
Discovery — listing datasets and inspecting fields is always free and never counts against the allowance.
- 05
Pending jobs — a scrape that exceeds the sync window bills nothing until you collect it.
- 06
Credits are billed at cost (1 credit = $0.01). Overflow beyond the free allowance bills automatically — there are no approval prompts.
Free Allowance & Billing
Enrichment runs without approval prompts. Every account gets 1,000 free records per month, shared between enrich calls and web searches, resetting on the account's renewal date. When a run exceeds what's left of the allowance, the overflow bills automatically at the per-record rates above. Each response reports creditsUsed and how many records the free allowance covered, so a plan can always tell you exactly what a run cost.
Example: Enrich LinkedIn Profiles
You do not have to write this yourself — ask in plain English (e.g. "enrich these LinkedIn profile URLs with name, title, and company") and the agent generates and runs the plan. The code below is what it runs under the hood.
// Build lookup keys from your sheet rows — match on the lowercase LinkedIn
// profile slug (the segment after /in/), NOT the full URL.
const ids = rows
.map(r => r.linkedinUrl?.split('/in/')[1]?.split(/[/?#]/)[0].toLowerCase())
.filter(Boolean);
// Instant lookup — no approval step needed: the first 1,000 records/month are
// free and overflow bills automatically (the response reports creditsUsed).
// Pass ALL ids in ONE `in` filter (batching is server-side).
const { records } = await rtrvr.enrich({
dataset: rtrvr.datasets.linkedinPeople,
filter: { name: 'id', operator: 'in', value: ids },
fields: ['id', 'name', 'position', 'current_company_name', 'city'],
});
// records → join back onto your rows on `id`, then write the enriched columns.Enriching LinkedIn URLs with Emails
To add emails and phone numbers, use the linkedinPeopleContact dataset — same instant lookup by id slug, but request the email and cellphone_number fields explicitly (they are dropped unless named). Coverage is partial: this is partner-sourced B2B contact data, and most profiles return null for both, so treat any email you get as a bonus rather than a guarantee. It is lookup-only: there is no scraper behind it, so scrapeUrls on linkedinPeopleContact is served by the linkedinPeople profiles scraper and returns profile fields but never email/cellphone_number — a person missing from the instant lookup cannot be recovered by a live scrape; report the miss.
const { records } = await rtrvr.enrich({
dataset: rtrvr.datasets.linkedinPeopleContact,
filter: { name: 'id', operator: 'in', value: slugs },
fields: ['id', 'name', 'position', 'current_company_name', 'email', 'cellphone_number'],
});
const filled = records.filter(r => r.email).length;
// e.g. "12 of 60 profiles had an email" — a blank email on a matched row is
// normal, not a failed lookup.Example: Enrich Companies by Domain
The linkedinCompanies dataset is instant-searchable and carries a website field, so a column of company domains can be enriched with firmographics in a sub-second lookup — no scraping required.
const { records } = await rtrvr.enrich({
dataset: rtrvr.datasets.linkedinCompanies,
filter: { name: 'website', operator: 'in', value: domains },
fields: ['name', 'website', 'industries', 'company_size', 'headquarters'],
});
// Domains are stored as full URLs, so `in` can miss on scheme or a leading
// "www.". If a domain returns nothing, retry it with the `includes` operator.Example: Enrich Amazon Products by URL
Non-LinkedIn datasets are live-scrape only: you supply each product's URL and get a fresh record back. Chunk lists larger than 20 with rtrvr.mapLimit.
const chunks = [];
for (let i = 0; i < productUrls.length; i += 20) chunks.push(productUrls.slice(i, i + 20));
const results = await rtrvr.mapLimit(chunks, 2, async chunk =>
rtrvr.enrich({
dataset: rtrvr.datasets.amazonProducts,
scrapeUrls: chunk,
fields: ['asin', 'title', 'brand', 'initial_price', 'availability'],
}),
);
// Each result may come back `pending` — collect it with { collect: snapshotId }.
// Join back onto your rows on `url` (or `input_url`, the URL you passed in).Web Search
Plans can also search the web programmatically with rtrvr.webSearch({ query, count?, gl?, hl?, recency?, since?, until?, news?, sortByDate? }) — one Google query per call, returning parsed organic results ({ title, url, snippet, source?, date?, dateText? }) and, for place-flavored queries, localResults (Google's local pack: name, address, rating, reviews, category, and a canonical maps link). Phone numbers and websites are not in the pack — they come from each business's own site or listing. Bound a search to a time window with recency (hour, day, week, month, year) or with explicit since/until dates (YYYY-MM-DD), and add sortByDate to order newest first. A time-bounded search returns each result's publication date as an absolute, already-normalized date, so a plan never has to parse a phrase like 5 hours ago itself; appliedFilters states the window that was applied and notice states anything that could not be. A result with no date is undated, which never means recent. Date filtering runs on Google's news vertical, the only one that carries publication dates, so any date filter turns news on unless you explicitly pass news: false. Queries draw from the same 1,000-record monthly free allowance as enrichment, then cost a flat 0.15 credits per query with no approval prompt, and it replaces navigating a browser tab to Google. Localize with gl (country) and hl (language).
Recipe: Local-Business Lead Generation
The pieces compose into a lead-generation pipeline — ask in plain English (e.g. "find 100 businesses in Casablanca and Rabat that likely need a website") and the agent runs this shape:
- 01
Fan
rtrvr.webSearchover each industry × city (localized, e.g.gl: 'ma', hl: 'fr') and harvest the local pack — business name, phone, website (or its absence), rating, maps link. - 02
Construct a Google Maps link per business:
https://www.google.com/maps/search/?api=1&query=Name+Cityresolves to the real place page. - 03
Enrich businesses that have a website with a free fetch of their contact/about page (email, socials), or instantly via the
linkedinCompaniesdataset filtered onwebsite. - 04
Qualify with one LLM pass (
rtrvr.inferSheetData) — e.g. a "why they need a website" column and a priority score. - 05
Rows append to a Google Sheet as they are found, so partial progress always survives; export the sheet as CSV when done.