This article covers the current rate limits, authentication requirements, API documentation, and known limitations across the Forge APIs and MCP tools.
Rate limits vary between Forge products.
The following limits currently apply:
Search and search-count requests: 20 requests per minute per account
Lookalike search: 20 requests per minute per account. Lookalike preview: 60 requests per minute per API key
Company followers search: 10 requests per minute per account
Single email and phone lookups: 120 requests per minute per API key
Enrichment job status and results, balance and filter lists: 60 requests per minute per API key
Maximum of 500 contacts per bulk enrichment request. Larger lists need to be split into several requests
Bulk enrichment has no per-minute limit, but there is a cap on active jobs per account (the API returns a 429 when it is reached)
The full per-endpoint list is in the Leadsforge Public API article.
Besides the rate limits, the Leadsforge API has a free monthly allowance:
Every account gets 1,000 free search requests and 1,000 free search-count requests per calendar month. Every cursor page counts as one search request. After that, each request costs 1 credit.
Lookalike previews: 300 free per calendar month, then 1 credit each.
Enrichment works as before and is charged per enriched contact.
Your Leadsforge API key keeps working whether your subscription is active or cancelled, as long as you have credits.
If the free allowance is used up and you have no credits, the API returns a 402 error.
No API rate limit is currently enforced.
No API rate limit is currently enforced.
No API rate limit is currently enforced on the public API.
No API rate limit is currently enforced.
No API rate limit is currently enforced.
Warmforge uses endpoint-specific limits:
Most mailbox and placement-test GET requests: 100 requests per minute
SMTP/OAuth2 connection requests: 10 requests per minute
Placement-test creation: 10 requests per minute
Mailbox bulk updates currently have no rate limit
These limits may change as the APIs evolve.
MCP uses product-specific API keys for authentication.
The following headers are used:
Salesforge: X-Salesforge-Key
Primeforge: X-Primeforge-Key
Leadsforge: X-Leadsforge-Key
Infraforge: X-Infraforge-Key
Warmforge: X-Warmforge-Key
Mailforge: X-Mailforge-Key
Only configure the headers for the Forge products you are using.
Primeforge mailbox exports are an exception to the normal MCP authentication pattern.
All public API mailbox exports require:
The normal API-key authentication header
The destination platform’s login email address in the request body
The destination platform’s login password in the request body
This applies to exports to:
Salesforge*
Warmforge*
Instantly
Smartlead
EmailBison
Lemlist
Reply.io
Snov.io
Woodpecker
Plusvibe
* The only exception for Salesforge and Warmforge is if you’ve signed up using Google SSO, in which case the destination platform’s login password is not required.
Some export destinations have additional requirements:
EmailBison also requires appUrl and clientId
Lemlist requires an additional OTP/magic-link verification step
The email and password requirements do not replace the API key. They are required in addition to it for export operations.
Use the appropriate MCP tool depending on the export destination:
Salesforge: primeforge_export_to_salesforge
All other supported platforms: primeforge_export_mailboxes
MCP functionality is still being expanded. The following limitations currently apply.
dailyEmailLimitThe underlying public API supports updating a mailbox's dailyEmailLimit on Salesforge, but this is not currently supported through MCP.
list_contacts, count_contacts and enroll_contacts filter by tag ID (the tagIds parameter). They don't accept tag names. If you pass a tag name instead of a tag ID, the filter is not applied as expected.
To find a tag's ID, use the list_tags tool. It returns the tags in a workspace with their IDs and names, and you can search by name. Then pass the ID in tagIds.
enroll_contacts is deprecated. It enrolls matching contacts immediately without a conflict review. For new integrations, use preflight_enrollments to check the enrollment first and confirm_enrollment_preflight to confirm it.
Each Forge product has its own API documentation and Swagger/OpenAPI reference.
Use the documentation for the product you are integrating with:
The API endpoints and authentication methods can differ between products, so make sure you are using the documentation for the correct API.
Forge APIs and MCP tools are actively being developed, so features listed as unsupported may become available over time.
We will update this article when:
New MCP functionality becomes available
Existing MCP limitations are resolved
API rate limits change
Authentication requirements change
For MCP setup instructions, see the Forge MCP Server article.