Firecrawl said on 13 November 2026 that Alexandria covers more than 75 million companies, offering sales teams a way to retrieve company profiles for account research. The published Apollo and FullEnrich schedules permit qualifying internal use, not unrestricted sharing with customers. For 100 matched company lookups, the listed rates give 1,500 Firecrawl credits with Apollo or 1,000 with FullEnrich, before other calls and AI costs.
Alexandria connects assistants to structured data providers through Firecrawl. These integrations were already listed in its 1 October announcement; the November coverage update is not a new grant of reuse rights.
Who may see the company records?
For an internal sales assistant, Apollo’s schedule allows storing and combining records for the organization’s own business purposes. It bars disclosure outside the organization, including through agent outputs, and prohibits using the data to train, fine-tune or improve AI models. Retrieval for a permitted task is not permission to train on the records.
FullEnrich’s schedule permits professional, business-to-business use in the ordinary course of your own business. Sharing records through a customer-facing feature requires a separate written agreement with Firecrawl. It also restricts unsolicited outreach; marketing must use business email, with professional-capacity contact and opt-outs respected.
The practical implication: a paying customer remains external even after signing in. These schedules do not establish permission for a particular client deliverable or externally shared AI summary. Nor should builders import the different audience rules in our guide to Firecrawl’s Benzinga display permissions into company-data features.
How long can you keep saved records?
Apollo, sections F.6 and F.8: already-delivered records may remain in internal use after access ends, subject to the applicable terms. Opt-out and deletion obligations continue; retention is conditional, not ownership.
FullEnrich, sections A.6 and A.7: delete affected records within ten days of the relevant notice. When source or service access ends, delete all covered data within ten days, except narrowly required legal retention.
For a CRM that mixes providers, this suggests keeping source identity with stored fields, exports and logs so deletion can be applied correctly. FullEnrich also requires preservation of attached provenance and attribution markers.
Apollo’s page header says F-1.0.2 while its body says F-1.0.0. Confirm the accepted version before relying on it.
What do 100 company lookups cost?
This is an illustrative credit budget, not a test or invoice: start with 100 known company domains, make one direct lookup per domain, and assume every lookup returns one matched company. Exclude searches for domains, contact enrichment, retries, refreshes, additional providers and AI reasoning.
Selected lookup | Credits per matched record | 100 matched records |
|---|---|---|
15 | 100 × 15 = 1,500 credits | |
10 | 100 × 10 = 1,000 credits |
Both capability references say a no-match result is unbilled. That does not establish the billing treatment of every kind of failed request. Nor do the two prices imply equivalent records, field completeness or accuracy.
As checked on 14 November, Firecrawl’s USD pricing lists 1,000 free credits refreshed monthly. With that balance untouched and the provider available to the account, the arithmetic covers 66 Apollo matches for 990 credits, or 100 FullEnrich records for 1,000. The latter leaves nothing for other credit-billed work.
Hobby includes 5,000 credits per month for US$19 billed monthly, or a displayed US$16 monthly equivalent billed annually. The two workloads use 30% and 20% of that allowance. A new monthly Hobby subscription still costs US$19; these percentages are not separately purchasable jobs. Credits are shared across endpoints, and model subscriptions, taxes and integration work are outside this calculation.
Additional providers need an additional budget. If 100 Apollo lookups match and 20 FullEnrich follow-up checks also return records, the total becomes 1,500 + 200 = 1,700 credits. This is another hypothetical workload, not a measured fallback rate.
Alexandria tool-only discovery is free; executing a tool uses its listed rate, and adding web search can incur separate charges. Agent’s five free daily runs are a different allowance. The documentation does not conclusively establish how that allowance applies to every third-party paid call, so it is not deducted here.
Which fields and quality measures matter?
Choose the fields your team needs before choosing the cheaper lookup. Apollo’s documented company response includes revenue and funding. FullEnrich’s selected lookup schema lists fields such as headcount, industry, founding year, technologies and locations, but does not list revenue or funding. A schema describes supported output; it does not guarantee a complete record for every company.
Firecrawl’s live company-enrichment leaderboard uses “quality” to mean the proportion of calls completed without a tool error over the previous 24 hours. That is an operational measure, not proof that a returned employee count is correct. Its speed measure is the time within which 95% of successful calls finish.
The separate Firecrawl study dated 2 October evaluates 200 US companies against an answer key. It is vendor-run and addresses a different question from the live error-rate leaderboard. Neither establishes accuracy for your own prospect list, particularly one drawn from another country or business segment.
What to check before connecting an assistant
For known accounts, begin with the documented company lookup that supplies the required fields. If the task is instead finding recent public announcements, our Firecrawl AI-news briefing walkthrough covers that separate web-research workflow; it is not evidence about these company lookups.
Review access deliberately. Alexandria’s documentation requires an organization administrator to review provider terms; Agent skips providers whose required terms have not been accepted. A credit balance alone does not establish eligibility.
Constrain automated spending. Agent’s provider controls let you select permitted providers and limit calls per turn. Inspect reported paid calls and credit use; a limit on calls is not the same as a fixed price.
Keep a human decision point. Check important company facts against original company sources before relying on them for account selection or outreach. Under Firecrawl’s general supplement, automated-agent actions remain the account holder’s responsibility.
For internal account research, choose by required fields, match usefulness and the storage obligations you can support. For a customer-facing feature, settle the reuse rights before committing to the integration.