PRIVATE COMPANY DATA SOURCE MAP

Private company data sources, mapped by job.

Private-company research usually needs more than one source. Statutory registries confirm legal facts, broad databases help with market coverage, risk datasets monitor company health, APIs support internal tools, and MCP access makes retrieval usable by AI agents. HubbleField adds a public, founder-supplied and approval-gated profile layer for human and authenticated agent discovery.

Request investor access Request API/MCP access

SOURCE MAP BY JOB

Choose the source by the job it can actually do.

Legal facts

Statutory registries

Best use: Confirm company existence, officers, filings, jurisdiction, incorporation history, and statutory changes.
Boundary: They rarely explain commercial relevance, founder-approved positioning, current traction, or public/private disclosure boundaries.
How HubbleField complements it: HubbleField sits beside registry checks with a current public profile that is founder-supplied, structured, and reviewed before discovery use.

Market coverage

Broad private-market databases

Best use: Build an initial target universe, enrich firmographic fields, and compare markets at scale.
Boundary: Coverage, freshness, field definitions, opt-in state, and source permission still need review.
How HubbleField complements it: HubbleField is not positioned as the widest database. It adds a public profile layer where founders provide current context for humans and agents.

Change monitoring

Risk and monitoring datasets

Best use: Track filings, adverse signals, web changes, hiring movement, domain state, and source-health changes after first discovery.
Boundary: Monitoring signals can explain what changed, but they do not replace diligence or founder confirmation.
How HubbleField complements it: HubbleField keeps profile freshness visible so a researcher can see when public facts were last confirmed or need review.

Approved public context

Founder-supplied public profiles

Best use: Read the company story, product category, evidence labels, source links, freshness dates, and public profile fields in one place.
Boundary: A public profile should not include private diligence files, confidential documents, cap tables, customer lists, or non-public investor data.
How HubbleField complements it: This is HubbleField's main role: founder-supplied, approval-gated, agent-readable company profiles designed for public-safe discovery.

Internal tools

HTTP APIs

Best use: Feed repeatable research workflows, dashboards, screening tools, and enrichment checks through stable HTTP calls.
Boundary: An API contract should expose only the authorised field tier and should not imply access to gated diligence.
How HubbleField complements it: HubbleField's API surface is for structured public profile retrieval and permission-aware workflows, not private document access.

AI-agent retrieval

MCP access

Best use: Let agents search, retrieve, compare, and cite public profile facts without scraping unstructured pages.
Boundary: Agent access still needs authentication, source citation, non-PII event tracking, and the same disclosure boundary as the web and API surfaces.
How HubbleField complements it: HubbleField makes profile data readable by authenticated agents while keeping private diligence and account-bound data out of anonymous public retrieval.

COMPARISON TABLE

Private-company source types side by side.

Source type	Best job	Boundary to record	HubbleField role
Statutory registries	Legal facts	They rarely explain commercial relevance, founder-approved positioning, current traction, or public/private disclosure boundaries.	HubbleField sits beside registry checks with a current public profile that is founder-supplied, structured, and reviewed before discovery use.
Broad private-market databases	Market coverage	Coverage, freshness, field definitions, opt-in state, and source permission still need review.	HubbleField is not positioned as the widest database. It adds a public profile layer where founders provide current context for humans and agents.
Risk and monitoring datasets	Change monitoring	Monitoring signals can explain what changed, but they do not replace diligence or founder confirmation.	HubbleField keeps profile freshness visible so a researcher can see when public facts were last confirmed or need review.
Founder-supplied public profiles	Approved public context	A public profile should not include private diligence files, confidential documents, cap tables, customer lists, or non-public investor data.	This is HubbleField's main role: founder-supplied, approval-gated, agent-readable company profiles designed for public-safe discovery.
HTTP APIs	Internal tools	An API contract should expose only the authorised field tier and should not imply access to gated diligence.	HubbleField's API surface is for structured public profile retrieval and permission-aware workflows, not private document access.
MCP access	AI-agent retrieval	Agent access still needs authentication, source citation, non-PII event tracking, and the same disclosure boundary as the web and API surfaces.	HubbleField makes profile data readable by authenticated agents while keeping private diligence and account-bound data out of anonymous public retrieval.

EXAMPLE WORKFLOWS

Use several sources before any private review step.

Investor shortlisting

Start with a thesis, jurisdiction, sector, stage, and exclusion rules.
Use registries for legal facts and broad databases for an initial universe.
Use HubbleField profiles to inspect current founder-supplied public context before deciding what needs diligence.

Adviser or corporate-development market scan

Create a market map from registries, websites, directories, and specialist datasets.
Use monitoring data to keep the target list current.
Use HubbleField to read approved public profiles and route next steps without claiming suitability or transaction readiness.

AI-agent research flow

Give the agent a precise research job and approved source boundaries.
Let HTTP or MCP tools retrieve public profile fields and source links.
Require citations, freshness notes, and a clear unknowns list before any human review step.

Founder profile preparation

Prepare public identity, category, product, traction, trust, and freshness fields.
Keep sensitive documents, financial detail, customer names, and private diligence behind permissioned workflows.
Use the agent-readable checklist before publishing a founder-supplied profile.

WHERE HUBBLEFIELD FITS

A public, founder-supplied, approval-gated profile layer.

HubbleField is an information-only, founder-supplied profile layer.
Public pages are for discovery context, source-linked facts, and freshness-aware profile review.
Profile publication remains approval-gated before it is used as a public discovery surface.
HTTP and MCP access should read the same authorised public profile boundary unless a separate permissioned workflow grants more.
HubbleField does not broker transactions, does not value companies, does not select targets, and does not expose private documents.
Information only. Not investment advice. Not an offer of securities in any jurisdiction.

INTERNAL LINKS BY READER JOB

Private company databaseFor evaluating the HubbleField structured discovery surface.How to find private companiesFor a practical research workflow before formal diligence.Private company deal sourcingFor thesis-led target discovery and public evidence boundaries.Private company monitoringFor source freshness, profile changes, and watchlist workflows.Private company data APIFor HTTP builders evaluating public-safe profile retrieval.MCP private-company discoveryFor authenticated agent setup and tool-led retrieval.Agent-readable profile checklistFor founders preparing structured public company facts.List your companyFor founders preparing the supply-side profile path.

FAQ

What private-company data source should I start with?

Start with the job. Use statutory registries for legal facts, broad databases for market coverage, risk datasets for monitoring, HTTP APIs for internal tools, and MCP access for agent retrieval. Use founder-supplied profiles when you need approved public company context.

Is HubbleField a Companies House or registry replacement?

No. Registries remain the source for statutory facts. HubbleField complements them with founder-supplied public profiles, freshness context, and agent-readable fields.

Does HubbleField score companies or data providers?

No. This resource maps source types by job. HubbleField does not score data providers, score companies, make suitability assessments, or tell a reader which company to invest in or acquire.

Can AI agents use private-company data safely?

Yes, when the retrieval path is authenticated, field tiers are explicit, source links are visible, and the agent stays within the same public or permissioned boundary as the user.

Does HubbleField expose private diligence?

No. Private documents, cap tables, full financials, customer lists, contracts, investor identities, unpublished listings, and account-bound data stay outside anonymous public discovery.

NEXT STEPS

Pick the path that matches your research job.

Investor, adviser, and corporate-development teams can request research access. API and MCP builders can request the agent-readable route. Founders can prepare the public profile layer that those workflows can cite.

Request investor access Request API/MCP access Prepare a company profile

Information only. Not investment advice. Not an offer of securities in any jurisdiction.

PRIVATE COMPANY DATA SOURCE MAP