Leadfeeder
Leadfeeder identifies the B2B companies visiting your website and enriches them with firmographics, contacts, intent signals, and CRM data. Revenue teams use it to prioritise outreach, discover buyer contacts, track campaign performance, and action accounts into lists and tags — all through natural-language queries.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Buyer & Account Intelligence Signals
- Secondary Subcategories
- None listed
- Brand
- Leadfeeder
- Access
- Account required
- First tracked
- 2026-08-11
- Tool count
- 65
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is visible.
ChatGPT Plugin Discoverability Score
ChatGPT organic discovery is not live yet
Leadfeeder is tracked in the ChatGPT Plugin registry. Public organic-discovery measurement is not live for ChatGPT yet, so there is no score to publish today.
Get notified when your score goes live
Enter your work email and we’ll notify you when ChatGPT Plugin organic discovery scoring launches.
No spam. Unsubscribe any time.
Competing in ChatGPT Buyer & Account Intelligence Signals
View CategoryHow the Discoverability Score works
Organic discovery scoring for Leadfeeder on ChatGPT is not live yet. The score will use measured agent conversations when it launches.
Organic discovery scoring is pending. Your Plugin score will appear on this scale when measurement goes live.
FoundDiagnostic
Whether Claude found your Plugin in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.
PickedMain score
How often your Plugin appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.
PositionedDiagnostic
What position your Plugin appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.
65 tools agents can invoke
Add a single company to one or more lists. Best when you have one company and want it placed on several lists at once (company → many lists). WHEN NOT TO USE: If you are adding multiple companies to the same list, do NOT call this tool in a loop — use Create Batch Add to List Job (create_batch_add_to_list_job) instead, which adds up to 100 companies to one list in a single request. Rule of thumb: 2+ companies going into one list → use the batch job; one company going into one or many lists → use this tool. The list IDs passed here come from the Retrieve Lists and Get List Details endpoints, and must be company lists (e.g. company_123). Credit Note: Adding a company to lists does not consume credits.
add_company_to_lists
Allows the addition of this contact to one or more lists. Since lists are a separate entity, the IDs that you must pass in this endpoint come from the **Retrieve Lists** and **Get List Details** endpoints. Credit Note: Adding a contact to lists does not consume credits. :::info Requires the `contacts:write` OAuth2 scope. :::
add_contact_to_lists
Allows the assignment of one or more tags to a given company. Since tags are a separate entity, the IDs that you must pass in this endpoint come from the **Retrieve Tags** and **Get Tag Details** endpoints. Credit Note: Assigning tags to a company does not consume credits. :::info Requires the `companies:write` OAuth2 scope. :::
assign_tags_to_company
CRITICAL: CREDIT-CONSUMING TOOL Using this tool MAY consume Leadfeeder credits. You MUST follow this protocol: 1. PAUSE: Do not execute this tool automatically. 2. INFORM: Tell the user this action may consume credits. It is not possible to know upfront how many credits will be consumed (if any). The actual consumption will be determined during execution. 3. CONFIRM: Ask the user for an explicit Yes/No confirmation to proceed. 4. EXECUTE: Only call this tool after receiving clear, affirmative consent. Returns all financial reports for a given company. Credit Note: Accessing financial data consumes 1 credit per company only if financial data is available and there was no active deep data access within the last 12 months. Once charged, no additional credits are consumed for accessing the same company’s financial data again within that 12-month period. :::info Requires the `companies:read` OAuth2 scope. :::
get_company_financials
PREFERRED way to add multiple companies or contacts to a single list (many members → one list). Use this instead of calling add_company_to_lists / add_contact_to_lists repeatedly: one job adds up to 100 members in a single request. Rule of thumb: whenever 2+ members are going into the same list, use this job rather than looping the per-entity tool. Schedules an asynchronous job. The target list is identified by data.attributes.list_id; the list's list_type determines whether company or contact references are accepted (every item's type must match). Up to 100 items per request. To remove members, use the separate batch-remove job (create_batch_remove_from_list_job) — adding and removing are distinct jobs. Returns 202 Accepted with a job handle. Poll Get Batch Add to List Job (get_batch_add_to_list_job) to observe progress and the per-item outcome (some items may fail while others succeed). For adding one company to several lists at once, use add_company_to_lists instead. Credit Note: Adding members to a list does not consume credits.
create_batch_add_to_list_job
PREFERRED way to remove multiple companies or contacts from a single list (many members → one list). Use this instead of calling remove_company_from_lists / remove_contact_from_lists repeatedly: one job removes up to 100 members in a single request. Rule of thumb: whenever 2+ members are leaving the same list, use this job rather than looping the per-entity tool. Schedules an asynchronous job. The target list is identified by data.attributes.list_id; the list's list_type determines whether company or contact references are accepted (every item's type must match). Up to 100 items per request. To add members, use the separate batch-add job (create_batch_add_to_list_job) — adding and removing are distinct jobs. Returns 202 Accepted with a job handle. Poll Get Batch Remove from List Job (get_batch_remove_from_list_job) to observe progress and the per-item outcome (some items may fail while others succeed). For removing one company from several lists at once, use remove_company_from_lists instead. Credit Note: Removing members from a list does not consume credits.
create_batch_remove_from_list_job
CRITICAL: CREDIT-CONSUMING TOOL Using this tool MAY consume Leadfeeder credits. You MUST follow this protocol: 1. PAUSE: Do not execute this tool automatically. 2. INFORM: Tell the user this action may consume credits. It is not possible to know upfront how many credits will be consumed (if any). The actual consumption will be determined during execution. 3. CONFIRM: Ask the user for an explicit Yes/No confirmation to proceed. 4. EXECUTE: Only call this tool after receiving clear, affirmative consent. Trigger an asynchronous job to enrich companies with AI-generated custom field values. The custom field must exist and be of an AI type (`ai_score`, `ai_text`, `ai_number`, `ai_boolean`). Create custom fields via the Custom Fields API first. The job runs in the background; poll the status endpoint to check progress. A maximum of 50,000 companies are enriched per job, whether targeted via `company_ids` or `list_id`; companies beyond this limit are not processed. Split larger selections across multiple jobs. Credit Note: Credits are consumed as companies are enriched. :::info Requires the `companies:read` OAuth2 scope. :::
create_company_enrichment_job
Create a new custom field in the account. :::info Requires the `custom_fields:write` OAuth2 scope. :::
create_custom_field
CRITICAL: CREDIT-CONSUMING TOOL Using this tool MAY consume Leadfeeder credits. You MUST follow this protocol: 1. PAUSE: Do not execute this tool automatically. 2. INFORM: Tell the user this action may consume credits. It is not possible to know upfront how many credits will be consumed (if any). The actual consumption will be determined during execution. 3. CONFIRM: Ask the user for an explicit Yes/No confirmation to proceed. 4. EXECUTE: Only call this tool after receiving clear, affirmative consent. Trigger an asynchronous job to enrich the given contacts with email and phone data. Accepts either explicit `contact_ids` or a `list_id` to target an entire list. The job runs in the background; poll the status endpoint to check progress. Credit Note: Credits are consumed as contacts are enriched. :::info Requires the `contacts:read` OAuth2 scope. :::
create_find_contact_data_job
Create a new tag with the provided attributes. This endpoint allows clients to define a new tag that can be assigned to companies. The response returns the full tag object, including its generated identifier and timestamps. Credit Note: Creating tags doe not consume credits. :::info Requires the `tags:write` OAuth2 scope. :::
create_tag
Create a new custom feed (a saved, filtered view of web-visiting companies) for the given account. The body lives under `data.attributes`. `advanced_filters` is a recursive tree: every node has `type: group` with `operator: and|or` and an `items` array; leaf conditions are `type: filter` with `field`, `operator`, `value`, and an optional `display_value` (a human-readable label for the value — set it equal to `value` when in doubt). Groups can be nested to express mixed AND/OR logic, and a group may set `negated: true` to invert it. Mirror the structure of the example bodies below exactly. Field/operator/value rules are field-specific and cannot be expressed in the schema: numeric fields like `employee_count` use `at_least` / `less_than` with an integer value; string fields like `country_code` or `region` use `is` / `is_not`; URL/text fields like `page_url` use `contains` / `begins_with`. Use ISO codes for `country_code` (e.g. "DE") and put the readable name in `display_value` (e.g. "Germany"). For the full list of fields and the operators/value formats each one accepts, see https://docs.leadfeeder.com/api/public/custom-feed-filter-reference-363484m0
create_web_visits_custom_feed
Create a new list in the account. :::info Requires the `lists:write` OAuth2 scope. :::
create_list
Delete a custom field from the account. Once removed, the custom field will no longer be accessible. Credit Note: Deleting custom fields does not consume credits. :::info Requires the `custom_fields:write` OAuth2 scope. :::
delete_custom_field
Delete a list from the account. Once removed, the list will no longer be accessible. Credit Note: Deleting list does not consume credits. :::info Requires the `lists:write` OAuth2 scope. :::
delete_list
Delete a specific tag identified by its ID Removes the tag from the account and unassigns it from all associated companies. Once deleted, the tag cannot be recovered. Credit Note: Deleting tags does not consume credits. :::info Requires the `tags:write` OAuth2 scope. :::
delete_tag
Delete a custom feed by its ID. :::info Requires the `web_visits:write` OAuth2 scope. :::
delete_web_visits_custom_feed
Enriches an input IP (IPv4/IPv6) with matching company information (if any). Subscription required: This tool requires an active IP Enrich subscription. If the account does not have this subscription, every call returns `403 access_denied`. Do not retry — contact Leadfeeder support to activate the subscription. Monthly call limit: The account has a monthly call limit set by its subscription tier. The limit is checked before the lookup executes; once reached, calls return `403 api_usage_limit_exceeded` for the rest of the month. Only successful calls count toward the limit — failed ones (invalid IP, no company found) do not. The limit resets at the start of each calendar month. No credits consumed: This tool does not use Leadfeeder credits. It uses a separate quota called matches, defined by the account's IP Enrich subscription tier. If a company was resolved from the IP (i.e. `company_type` is `"company"` in the response), `meta.num_results` is `1` and the call counts against the monthly limit. If the IP belongs to a network or ISP instead (`"shared_network"` in the response), `meta.num_results` is `0` and the call does not count.
enrich_ip
Estimate the credit cost for enriching companies with AI-generated custom field values. Target the estimate with a specific `list_id`, flat `company_ids`, or a pre-computed `company_count`. Credit Note: This endpoint does not consume credits. :::info Requires the `companies:read` OAuth2 scope. :::
estimate_company_enrichment_job
Estimate the credit cost for enriching contacts with email and phone data. Accepts either explicit `contact_ids` or a `list_id` to target an entire list. Returns the number of eligible contacts and the estimated total credits that would be consumed. Credit Note: This endpoint does not consume credits. :::info Requires the `contacts:read` OAuth2 scope. :::
estimate_find_contact_data_job
Retrieve the status of a batch add-to-list job created via `POST /v1/lists/batch-add-to-list-jobs`. While `status` is `running`, `results` and `summary` are omitted. Once `status` becomes `completed`, `results` carries the per-item outcome and `summary` carries the per-outcome counts (including `failed_count`) together with `list_size_before` and `list_size_after`. A job created from an `advanced_search` selection reports `summary` counts only — no per-item `results`. On `failed`, `errors` describes the failure. Credit Note: This endpoint does not consume credits. :::info Requires the `lists:read` OAuth2 scope. :::
get_batch_add_to_list_job
Retrieve the status of a batch remove-from-list job created via `POST /v1/lists/batch-remove-from-list-jobs`. While `status` is `running`, `results` and `summary` are omitted. Once `status` becomes `completed`, `results` carries the per-item outcome and `summary` carries the per-outcome counts (including `failed_count`) together with `list_size_after`. A job created from an `advanced_search` selection reports `summary` counts only — no per-item `results`. On `failed`, `errors` describes the failure. Credit Note: This endpoint does not consume credits. :::info Requires the `lists:read` OAuth2 scope. :::
get_batch_remove_from_list_job
Get the details of a specific buyer persona by ID, including its name, creation timestamp, and the full set of filter criteria that define it. Credit Note: Retrieving a buyer persona definition does not consume credits. :::info Requires the `buyer_personas:read` OAuth2 scope. :::
get_buyer_persona
Fetch detailed information about a specific campaign using its campaign ID. Use the include parameter to attach related campaign data, campaign settings, list, or custom feed information to the result. :::info Requires the `campaigns:read` OAuth2 scope. :::
get_campaign
CRITICAL: CREDIT-CONSUMING TOOL Using this tool MAY consume Leadfeeder credits. You MUST follow this protocol: 1. PAUSE: Do not execute this tool automatically. 2. INFORM: Tell the user this action may consume credits. It is not possible to know upfront how many credits will be consumed (if any). The actual consumption will be determined during execution. 3. CONFIRM: Ask the user for an explicit Yes/No confirmation to proceed. 4. EXECUTE: Only call this tool after receiving clear, affirmative consent. Fetch detailed information about a specific company, including firmographics and hierarchy information based on the provided Leadfeeder company_id. Credit Note: Accessing full deep data consumes 1 credit, unless the company was already accessed within the last 12 months. :::info Requires the `companies:read` OAuth2 scope. :::
get_company
Retrieve the current status of a Company AI Enrichment job. Returns progress counters, credit consumption, and any errors. Jobs are retained for 7 days after completion. Credit Note: This endpoint does not consume credits. :::info Requires the `companies:read` OAuth2 scope. :::
get_company_enrichment_job
CRITICAL: CREDIT-CONSUMING TOOL Using this tool MAY consume Leadfeeder credits. You MUST follow this protocol: 1. PAUSE: Do not execute this tool automatically. 2. INFORM: Tell the user this action may consume credits. It is not possible to know upfront how many credits will be consumed (if any). The actual consumption will be determined during execution. 3. CONFIRM: Ask the user for an explicit Yes/No confirmation to proceed. 4. EXECUTE: Only call this tool after receiving clear, affirmative consent. Get the details of a contact by ID. Credit Note: Accessing full deep data consumes 1 credit, unless the contact was already accessed within the last 12 months. :::info Requires the `contacts:read` OAuth2 scope. :::
get_contact
Retrieves the identity of the current API user - a "whoami" endpoint. Unlike most endpoints, this one does not require the `account_id` query parameter — the user's identity is independent of the account they are currently working on.
get_current_user_info
Retrieve a single custom feed by its ID. :::info Requires the `web_visits:read` OAuth2 scope. :::
get_web_visits_custom_feed
Fetch the details of a specific custom field using its internal name. The response returns the field's attributes. Credit Note: Retrieving custom field definitions does not consume credits. :::info Requires the `custom_fields:read` OAuth2 scope. :::
get_custom_field
Access usage statistics for various API endpoints for monitoring and auditing purposes. Returns usage data for all endpoints accessible by the requesting account within the specified date range. :::info Requires the `usage:read` OAuth2 scope. :::
usage
Retrieve the current status of a Find Contact Data job. Returns progress counters, credit consumption, and any errors. Jobs are retained for 7 days after completion. Credit Note: This endpoint does not consume credits. :::info Requires the `contacts:read` OAuth2 scope. :::
get_find_contact_data_job
Get the details of a specific Ideal Customer Profile (ICP) by ID, including its name, creation timestamp, and the full set of filter criteria that define it. Credit Note: Retrieving an ICP definition does not consume credits. :::info Requires the `icps:read` OAuth2 scope. :::
get_icp
Retrieve the details of a specific list using its unique ID. The response includes the list's attributes, such as its name and scope, along with any related information requested through query parameters. This endpoint is used to fetch the full definition of a list before viewing, updating, or managing its assigned items. Credit Note: Retrieving list definitions does not consume credits. :::info Requires the `lists:read` OAuth2 scope. :::
get_list
Fetch the details of a specific tag using its unique tag ID. Returns the tag’s attributes, including its name, color, and timestamps indicating when it was created and last updated. Credit Note: Retrieving tag data does not consume credits. :::info Requires the `tags:read` OAuth2 scope. :::
get_tag
Lists every Leadfeeder account available to this API key. Use this tool whenever you need to list, get, show, or choose accounts. get_account_info IS the list-accounts tool: there is NO get_accounts, list_accounts, or accounts tool, so never invent or call another name — always call get_account_info. Call with no account_id to list all accounts; each result includes the account name and id, but no credit details. Call with a specific account_id to retrieve that one account's credit details. Every account also carries the company it belongs to under relationships.account_company, as an id only. Pass include=account_company to load that company's name as well — do this whenever you need to name or group accounts by their company, since the id alone is not meaningful to the user.
get_account_info
Find matching companies based on the provided input parameters. Returns matching company IDs and basic company information. **Important:** Each company object must include at least one of these required fields: `company_name`, `url`, `vat_id`, or `register_id`. Additional fields like email, phone, and address can improve match accuracy but cannot be used alone. Credit Note: Matches do not consume credits. Credits are only used if you subsequently retrieve deep data for a company you haven't accessed within the last 12 months. :::info Requires the `companies:read` OAuth2 scope. :::
match_companies
Remove a single company from one or more lists. Best when you have one company and want it taken off several lists at once (company → many lists). WHEN NOT TO USE: If you are removing multiple companies from the same list, do NOT call this tool in a loop — use Create Batch Remove from List Job (create_batch_remove_from_list_job) instead, which removes up to 100 companies from one list in a single request. Rule of thumb: 2+ companies leaving one list → use the batch job; one company leaving one or many lists → use this tool. The list IDs come from the Retrieve Lists and Get List Details endpoints, and must be company lists (e.g. company_123). Credit Note: Removing a company from lists does not consume credits.
remove_company_from_lists
Allows the removal of this contact from one or more lists. Credit Note: Removing a contact from lists does not consume credits. :::info Requires the `contacts:write` OAuth2 scope. :::
remove_contact_from_lists
Retrieve all buyer personas defined in the account. Each buyer persona is a saved set of contact-level filter criteria (department, job title, location, seniority) used to identify target contacts. Credit Note: Retrieving buyer persona definitions does not consume credits. :::info Requires the `buyer_personas:read` OAuth2 scope. :::
get_buyer_personas
Retrieve statistics for a specific campaign over a defined time period. Use frequency, start_period, and end_period to control how the campaign performance data is grouped and returned. :::info Requires the `campaigns:read` OAuth2 scope. ::: Pagination: use `page[num]` to page through results, starting at 1. Increment by 1 for each subsequent page. Stop when `page[num]` exceeds `meta.pagination.page_count`. `page[size]` controls how many items are returned per page (default: 20, max: 100).
get_campaign_stats
Retrieve the list of all campaigns available in the account. Use pagination to control the number of campaigns returned, and include related campaign data, campaign settings, list, or custom feed information when needed. :::info Requires the `campaigns:read` OAuth2 scope. ::: Pagination: use `page[num]` to page through results, starting at 1. Increment by 1 for each subsequent page. Stop when `page[num]` exceeds `meta.pagination.page_count`. `page[size]` controls how many items are returned per page (default: 20, max: 100).
get_campaigns
CRITICAL: CREDIT-CONSUMING TOOL Using this tool MAY consume Leadfeeder credits. You MUST follow this protocol: 1. PAUSE: Do not execute this tool automatically. 2. INFORM: Tell the user this action may consume credits. It is not possible to know upfront how many credits will be consumed (if any). The actual consumption will be determined during execution. 3. CONFIRM: Ask the user for an explicit Yes/No confirmation to proceed. 4. EXECUTE: Only call this tool after receiving clear, affirmative consent. Fetch one or more companies by their Leadfeeder IDs in a single call. Use this instead of calling get_company multiple times when you have more than one ID. Pass the IDs comma-separated in the `ids` parameter, e.g. "159001425,129011" (up to 100 IDs).
get_companies_by_ids
CRITICAL: CREDIT-CONSUMING TOOL Using this tool MAY consume Leadfeeder credits. You MUST follow this protocol: 1. PAUSE: Do not execute this tool automatically. 2. INFORM: Tell the user this action may consume credits. It is not possible to know upfront how many credits will be consumed (if any). The actual consumption will be determined during execution. 3. CONFIRM: Ask the user for an explicit Yes/No confirmation to proceed. 4. EXECUTE: Only call this tool after receiving clear, affirmative consent. Fetch known IP addresses associated with a given set of companies, enabling identification of web traffic and network activity linked to those organizations based on the provided company IDs. Credit Note: Retrieving IP address data consumes 1 credit per company, unless the company's IP data was already accessed within the last 12 months. :::info Requires the `companies:read` OAuth2 scope. :::
get_company_ips
CRITICAL: CREDIT-CONSUMING TOOL Using this tool MAY consume Leadfeeder credits. You MUST follow this protocol: 1. PAUSE: Do not execute this tool automatically. 2. INFORM: Tell the user this action may consume credits. It is not possible to know upfront how many credits will be consumed (if any). The actual consumption will be determined during execution. 3. CONFIRM: Ask the user for an explicit Yes/No confirmation to proceed. 4. EXECUTE: Only call this tool after receiving clear, affirmative consent. Retrieve a list of contacts based on the provided IDs. Credit Note: Each contact will contain its full deep data and it will consume 1 credit, unless the contact has already been accessed within the last 12 months. :::info Requires the `contacts:read` OAuth2 scope. :::
get_contacts
Retrieve all custom feeds accessible to the current user for the given account. :::info Requires the `web_visits:read` OAuth2 scope. :::
get_web_visits_custom_feeds
Retrieve all custom feed folders accessible to the current user for the given account. :::info Requires the `web_visits:read` OAuth2 scope. :::
get_web_visits_custom_feed_folders
Retrieve the list of all custom field definitions available in the account. The response includes each field's attributes. Credit Note: Retrieving custom field definitions does not consume credits. :::info Requires the `custom_fields:read` OAuth2 scope. ::: Pagination: use `page[num]` to page through results, starting at 1. Increment by 1 for each subsequent page. Stop when `page[num]` exceeds `meta.pagination.page_count`. `page[size]` controls how many items are returned per page (default: 20, max: 100).
get_custom_fields
Retrieve all Ideal Customer Profiles (ICPs) defined in the account. Each ICP is a saved set of company-level filter criteria (employee count, industry, location) used to identify target companies. Credit Note: Retrieving ICP definitions does not consume credits. :::info Requires the `icps:read` OAuth2 scope. :::
get_icps
Retrieve the members of a list. The list is addressed by its `{id}`, a scope-prefixed list identifier (e.g. `company_123` or `contact_456`). There is a single `List` resource: the list's `list_type` determines whether the members are companies or contacts. The response contains bare references (IDs only) in `data`, with `type` following the list's `list_type` (`company` for a company list, `contact` for a contact list). Results are cursor-paginated. To retrieve the full company or contact data for these members, pass the returned IDs to the Retrieve Companies (`GET /v1/companies`) or Retrieve Contacts (`GET /v1/contacts`) endpoints. Credit Note: Retrieving list members does not consume credits. :::info Requires the `lists:read` OAuth2 scope. ::: Pagination: pass `page[cursor]` from `meta.pagination.next_cursor` to fetch the next page. Stop when `next_cursor` is null. `page[size]` controls how many items are returned per page (default: 20, max: 100).
get_list_items
Retrieve all lists available in the account. The response includes each list's attributes and can be filtered through query parameters. Credit Note: Retrieving list definitions does not consume credits. :::info Requires the `lists:read` OAuth2 scope. ::: Pagination: use `page[num]` to page through results, starting at 1. Increment by 1 for each subsequent page. Stop when `page[num]` exceeds `meta.pagination.page_count`. `page[size]` controls how many items are returned per page (default: 20, max: 100).
get_lists
How do I improve a ChatGPT Plugin's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Leadfeeder alternatives on ChatGPT?
As of 2026-08-14, Leadfeeder competes with 6sense, Actively, Common Room, G2 MCP, Humantic AI, Needle, PredictLeads in ChatGPT Buyer & Account Intelligence Signals, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.