> ## Documentation Index
> Fetch the complete documentation index at: https://www.forager.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Forager is a REST API for B2B people, company and job post data: contact lookups (phone numbers, personal emails, work emails), person, company and job post search, and bulk data feeds.
> Server: https://api-v2.forager.ai. Send the API key in the X-API-KEY header. Most paths include {account_id}. Read FORAGER_API_KEY and FORAGER_ACCOUNT_ID from the environment; never put the key in client-side code, logs or prompts.
> To add Forager to a project, follow https://www.forager.ai/docs/guides/agent-quickstart.md. To pick an endpoint, read https://www.forager.ai/docs/guides/choose-an-endpoint.md. For end-to-end builds, see https://www.forager.ai/docs/recipes/overview.md.
> Most requests spend credits. Do not guess costs; use https://www.forager.ai/docs/api-overview/credit-pricing.md and ask the user before spending credits.
> Use only endpoints and fields defined in https://www.forager.ai/docs/openapi.yaml. Forager has no MCP server for the API yet; the /mcp endpoint on this site searches the documentation only.

# Data feed FAQ

> Answers about Forager data feed record counts, LinkedIn identifiers and records removed from the dataset.

![Data feed FAQ: common questions about Forager data feeds and their answers](https://mintcdn.com/forager/EGsWCxLOYv1Cb__c/images/illustrations/data-feed-faq-questions.svg?fit=max\&auto=format\&n=EGsWCxLOYv1Cb__c\&q=85\&s=911aa16c4ea2f32e1ace3ab1b74b9641)

> [accordion] Why does my data feed have more person records than were updated in the last month?
>
> This is expected behavior.
>
> The **total record count** represents all person profiles currently in the dataset.\
> The **“updated in the last month” count** reflects how many of those profiles we were able to recrawl.
>
> We no longer crawl profiles when a:
>
> * Profile becomes inactive.
> * Profile is banned on LinkedIn.
> * Profile no longer exists.

> [accordion] Why do some person records not have LinkedIn identifiers?
>
> You may discover a small subset of LinkedIn profiles with missing LinkedIn Identifiers. This typically happens when a LinkedIn profile becomes banned.

> [accordion] How do refresh cycles work?
>
> * Forager data feeds are continuously refreshed on a rolling basis.
> * Delivery schedules (daily, weekly, monthly) control how often the recrawled profiles are delivered to you, not how often the underlying data is refreshed.
> * Transfers can be limited to records crawled since the last scheduled transfer (net new data only). Ask support which mode your feed uses.
> * The `date_updated` field indicates when the profile was last crawled.

> [accordion] How are deletions handled?
>
> When Forager determines that a record is no longer valid, legally distributable, or should no longer appear in the dataset. The crawlers will no longer update this profile, causing the profile not to be transferred in any future data transfers.

> [accordion] How do schema versions change?
>
> Forager schemas are versioned to ensure stability for downstream pipelines.
>
> When fields are added, structures evolve, or improvements are made, a new schema version is released. The schema version is included in:
>
> * File paths for bucket deliveries
> * The `schema_version` field of each record (see [Row format](https://www.forager.ai/docs/data-license/v2/output-data-file-details.md#row-format))
>
> This allows your data engineering team to:
>
> * Continue using older versions
> * Migrate on your timeline
> * Validate changes before moving production pipelines
>
> Schema changes are designed to be additive whenever possible, minimizing breaking changes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.