License a people feed for retrieval over people and company records
Give a product that answers people and company questions a licensed dataset to index and retrieve from, instead of calling an API per question or scraping profiles.
- Free API key
- No credit card
- Run your sample
A selection of teams that run this job on Forager · plus other teams on Forager
What it costs: Charged per request: credit pricing.
- People data feed
- Company data feed
- Data feed
- Feed licensee
- AI agents & developer tools
How the data flows
- company records
- Example Inc.
- person id
- per_8f3a1c
- name
- Jane Example
- title
- VP Revenue Operations
- mobile
- +1 (415) 555-0142
- work email
- jane@example.com
Steps
- License the people and company feeds and agree the refresh schedule and permitted use
- Load each delivery into your warehouse or vector index keyed on
person_idandcompany_id - Retrieve the matching records for each question and pass them to the model as context
- Call the API only for contact fields, which stay out of the feed and are paid per result
Inputs and outputs
| Inputs | Outputs |
|---|---|
| feed delivery (S3 or Snowflake) | person records |
| refresh schedule | company records |
person_id | |
company_id |
Questions about this recipe
Where can an AI product license people and company records for retrieval?
This recipe uses Forager People data feed and Company data feed. People data feed: A licensed file of 800M+ professional profiles, refreshed on a schedule and delivered to Snowflake or S3. Give a product that answers people and company questions a licensed dataset to index and retrieve from, instead of calling an API per question or scraping profiles.
What does it cost to license a people feed for retrieval over people and company records?
People data feed is a flat annual licence, global or regional, not priced in credits. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices
What do I need to run this recipe, and what comes back?
You send feed delivery (S3 or Snowflake) and refresh schedule. You get back company records, company_id, person records and person_id, as JSON. You also need a Forager API key, which comes with a free account.
Should my agent call a people API per question or index a data feed?
This recipe uses Forager People data feed and Company data feed. People data feed: A licensed file of 800M+ professional profiles, refreshed on a schedule and delivered to Snowflake or S3. Give a product that answers people and company questions a licensed dataset to index and retrieve from, instead of calling an API per question or scraping profiles.
Is there a free way to try Forager on this workflow?
Yes. Request a sample extract of the people data feed on a 30-minute call and check the fields against your own records before you license it.
When should I run this workflow?
When a product answers thousands of people and company questions a day and needs the records in its own index, with refresh terms it can show its customers. Answers are grounded in licensed records the product controls, and the API spend is limited to the contacts its users actually ask for.
Which Forager products does this recipe use?
People data feed and company data feed. People data feed: a licensed file of 800M+ professional profiles, refreshed on a schedule and delivered to Snowflake or S3. Company data feed: a licensed file of 65M+ company profiles and firmographics, delivered to Snowflake or S3 on a schedule.
How do I know the data is right?
The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.
Which tools can run this workflow?
Delivered as a data share to Snowflake, Databricks and Amazon S3. Or call the endpoints in the steps above from your own code with one API key.
How many steps is this workflow?
4 steps: license the people and company feeds and agree the refresh schedule and permitted use, load each delivery into your warehouse or vector index keyed on person_id and company_id, retrieve the matching records for each question and pass them to the model as context and call the API only for contact fields, which stay out of the feed and are paid per result.
Is there a contract or minimum commitment?
Data feeds are licensed on an annual agreement, with the term, volume and refresh schedule written into it. There are no self-serve plans for feeds.
Can we show Forager data inside our product?
Yes, under platform terms. Self-serve plans cover internal use by your own team. Showing Forager data to your users, or passing records on, is licensed separately: talk to sales about volume and which fields your users need to see.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
- $5 free credits
- No credit card
- Run your sample
A selection of teams that run this job on Forager · plus other teams on ForagerA selection of teams using Forager
-
Clay - GTM workflow builders
Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
-
Juicebox - AI candidate sourcing
Selected use case: Forager data behind its PeopleGPT search and sourcing agents.
-
HubSpot - CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
-
Emergent Labs - Agent builders
AI app-building platform where agents design, code and deploy full-stack apps.
-
Andela - Customer
Selected use case: Forager data for the go-to-market team at a global talent marketplace.
-
SeekOut - Talent intelligence
Selected use case: Forager’s people data feed, used to keep candidate profiles current.
2–3 years on the Forager people data feed, by SeekOut’s own account1
-
Airscale - Waterfall enrichment
Selected use case: a Forager step in its mobile number waterfall.
-
Bitscale - GTM workflow builders
Selected use case: Forager in its contact waterfall for mobile numbers.
Sources
1 SeekOut: SeekOut, customer interview, Sep 2026.
More recipes for LLM apps
-
Ground AI CRM agents with fresh company and people records
-
Brief users on the people they are about to meet, from an email address
-
Refresh contact data before an agent writes to the CRM
-
Resolve a sign-up email to a person inside a copilot
-
Answer hiring and labor-market questions in an AI analyst from a job postings feed
-
Train title-normalisation and company-matching models on structured profiles
