$5 free Limited time. Sign up to activate. Get your $5 →
AI SDRs and agent builders · Agent frameworks and builders

Work email API for AI agent builders

Land in the right inbox.

What agent builders need from work emails, what Forager returns, and how teams like yours test it.

3 recipes use work emails for agent frameworks and builders.

  • $5 free credits
  • 800M+ people
  • 65M+ companies

A selection of agent builders using Forager for work emails · plus other teams on Forager

  • Clay
  • Juicebox
  • HubSpot
  • Emergent Labs
  • Andela
  • Orbital
  • Coram
  • BetterContact
For agent frameworks and builders
The job
Let GTM engineers and developers build production enrichment workflows by prompting a coding agent against typed endpoints, or add a people endpoint to their own web-data API.
When
A developer asks a coding agent to 'enrich new sign-ups with role and company and route them'.
Outcome
GTM engineers ship production workflows in minutes and developers enrich sign-ups and leads with one API key.
Lead recipe 1

Give coding agents typed people and company data tools

When to use it: A developer asks a coding agent to 'enrich new sign-ups with role and company and route them'.

  1. Publish typed schemas for person_role_search, person_detail_lookup, reverse lookup, organization_search and job_search
  2. Coding agent generates the workflow code and calls endpoints with one API key
  3. Use _totals endpoints to estimate cost before paginating
  4. Deploy as a scheduled job or webhook handler
InputsOutputs
developer promptgenerated workflow
API keyenriched records
typed endpoint schemas
Lead recipe 2

Offer people and company data as a built-in integration in an AI app builder

When to use it: A user prompts the app builder for a CRM, lead-gen or networking app that needs real people and company data.

Show the steps
  1. Register an integration that wraps POST /person_role_search/, POST /person_detail_lookup/ and POST /organization_search/ with typed schemas
  2. When generated code needs contacts, call /person_contacts_lookup/work_emails/ and POST /person_contacts_lookup/phone_numbers/ through the platform's metered key
  3. For card or badge capture apps, OCR the name and company and resolve the person with POST /person_detail_lookup/
  4. Bill builders in platform credits and show credits used per call
InputsOutputs
natural-language app promptperson
name + companycompany
company domainwork_email
phone_number
Open the recipe: Offer people and company data as a built-in integration in an AI app builder
Lead recipe 3

Add Forager as a waterfall step in an agent's contact tool

When to use it: An agent's find-contact tool returns nothing for a third of prospects because its single source has no mobiles.

Show the steps
  1. Define one find_contact tool in your framework that takes a LinkedIn URL or name and company
  2. Inside it, call POST /person_contacts_lookup/phone_numbers/ then POST /person_contacts_lookup/work_emails/ when the earlier source returns nothing
  3. Return a typed result with the field names, the source that found it and the person_id
  4. Count credits per found result only, so a miss in the Forager step adds 0 to the run's cost
InputsOutputs
LinkedIn URL or public identifierphone_number
full name + company domainwork_email
personal_email
source
person_id
Open the recipe: Add Forager as a waterfall step in an agent's contact tool
Fields

Fields you get back

  • generated workflow
  • enriched records
  • person
  • company
  • work_email
  • phone_number
  • personal_email
  • source
  • person_id

From the workflows above. Full field reference: Work emails and the Work emails API reference.

Who owns this

Who evaluates work emails at agent frameworks and builders, and what they are judged on

  • Product manager who owns the enrichment feature: judged on what users see when they open a record
  • Engineering lead integrating the API: judged on response time and errors they can route on
  • Partnerships or data lead managing vendors: judged on cost per valid result

A selection of agent builders using Forager for work emails · plus other teams on 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.

  • Orbital
    • Lead databases

    Selected use case: contact lookups in its enrichment waterfall, for teams selling to local businesses.

  • Coram
    • Internal use

    Selected use case: mobile numbers for outbound calling.

  • BetterContact
    • Waterfall enrichment

    Selected use case: a Forager step in its waterfall for mobile numbers.

“We use Forager to enrich our contact data with email addresses and mobile phone numbers. After analyzing all the data providers we use, we found Forager to deliver the best overall data quality.”
AndelaRyley L.Growth Marketing Associate
800M+people
65M+companies
How to test it

Test work emails on your own sample

  1. Pull a sample. Take profiles your users looked up last week.
  2. Run it. Use a self-serve key, or book a demo and send us the list.
  3. Measure what your users feel. Connect rate for mobiles, bounces for emails, and whether the right person answers.
  • $5 free credits
  • No credit card
  • Pay per result
FAQ

Frequently asked questions

How do AI agent builders use Forager work emails?

Let GTM engineers and developers build production enrichment workflows by prompting a coding agent against typed endpoints, or add a people endpoint to their own web-data API. Verified work email addresses for a person at their current employer. This page walks through 3 workflows with the exact steps.

What do work emails cost for AI agent builders?

Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. That is $0.07 per work email on Starter month to month and $0.05 on Pro with yearly billing. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices

Why do AI agent builders add work emails?

Typed people and contact lookups your agents can call, paid per result. Products like yours are judged on whether the agent reached the right person, which is why the cost that counts is per result that reaches the right person. Run your own sample to see what work emails returns for your users before you build on it.

Which people and company data APIs work well with coding agents?

The workflow uses Forager People search, Person enrichment, Company enrichment, Job postings API, Work emails, Personal emails and Reverse email lookup. People search: Find the people who hold a role at target companies, filtered by title, seniority, department and location. Let GTM engineers and developers build production enrichment workflows by prompting a coding agent against typed endpoints, or add a people endpoint to their own web-data API.

What inputs does it take and what does it return?

You send LinkedIn URL or public identifier, API key and company domain. You get back work_email, person_id, phone_number and company, from POST /person_contacts_lookup/work_emails/, as JSON.

Can our users see Forager data in our product?

Yes, under platform terms. Self-serve plans cover internal use by your own team. Showing Forager contacts to your users, or passing records on, is licensed separately: talk to sales about volume and which fields your users need to see.

Am I charged when no work email is found?

No. A work email lookup that finds nothing costs 0 credits, so you pay for work emails we find. Search, enrichment and reverse lookups are the exception: they are charged per request.

Can AI agent builders test work emails for free?

Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.

How do I add contact enrichment to a vibe coded app?

When generated code needs contacts, call /person_contacts_lookup/work_emails/ and POST /person_contacts_lookup/phone_numbers/ through the platform's metered key. For card or badge capture apps, OCR the name and company and resolve the person with POST /person_detail_lookup/.

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.

How is a work email finder different from guessing the email pattern?

A pattern guess (first.last@company.com) gives you an address that may not exist or may belong to someone who left. A work email lookup returns the address for that person at their current employer, and with Forager a work email lookup that finds nothing costs 0 credits.

Where can I use Forager work emails?

Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Everything else connects through the REST API with one API key.

Start building

Put people, company and job data your users can act on inside your product

Send us a list. We run it, show you what we find, then talk volume and terms.

  • $5 free credits
  • No credit card
  • Run your sample
Platforms and teams that build on Forager
  • Clay
  • Juicebox
  • Nooks
  • Andela
  • HubSpot
  • SeekOut