Registries
Best for statutory filings, officers, incorporation history, and jurisdictional facts. HubbleField should sit beside them when a workflow needs current public company context.
PRIVATE COMPANY DATA API
Private company data API for agent-led discovery
HubbleField gives builders a structured, public-safe private-company profile layer for research, monitoring, enrichment, and agent workflows. It is not a full registry mirror and it is not a route into private diligence.
BUILDER INTENT
Who uses the API
- agent-builder search tools that need a clean private-company profile layer
- investor or adviser research workflows comparing public context with registries and CRMs
- corporate-development scans that need source-linked profiles before deeper diligence
- founder visibility products that turn approved public facts into agent-readable records
WHAT RETURNS
Public API layer
- company identity, website, profile URL, stage, geography, and categories
- public product summary, customer profile, founder-approved positioning, and source links
- freshness state, profile update dates, trust-signal summaries, and public access paths
- REST and MCP-readable shapes that point agents back to stable HubbleField pages
WHAT STAYS OUT
Gated private diligence
- cap table, full financial model, customer lists, contracts, and diligence files
- unpublished listings, internal review notes, sensitive raise material, and personal data
- founder-approved diligence packs unless a future permissioned workflow explicitly grants access
- suitability, valuation, transaction, or decision-making material
REST AND MCP
One disclosure boundary, two integration surfaces.
REST is the direct HTTP surface for internal tools, data products, and scripted workflows. MCP is the agent tool surface for Claude, ChatGPT, Cursor, and other clients. Both are designed around the same public-tier fields until a permissioned route explicitly grants more.
Use the API reference for endpoint detail, MCP tool contracts for exact schemas, and the MCP setup page for agent installation.
EXAMPLE REQUEST
Placeholder-only shape for builder evaluation.
Example request
GET /api/v1/search_companies?query=workflow%20automation&hq_country=GB&limit=3
Authorization: Bearer <token>Example response
{
"ok": true,
"results": [
{
"slug": "atlas-robotics",
"name": "Atlas Robotics Ltd",
"profile_url": "https://hubblefield.com/co/atlas-robotics",
"hq_country": "GB",
"stage": "seed",
"categories": ["industrial_automation", "workflow_software"],
"one_liner": "Placeholder company building robotics workflow tools for factory teams.",
"freshness_state": "fresh",
"source_links": ["https://example.com/atlas-robotics"],
"access_path": "/waitlist?role=agent_builder"
}
],
"next_cursor": "example-private-cloud-tools"
}This example uses synthetic placeholder data only. It does not contain real company records, token values, private documents, or founder diligence.
WHERE HUBBLEFIELD DIFFERS
Enrichment APIs
Useful for scale and third-party augmentation. HubbleField is narrower: founder-supplied profiles, freshness context, public boundaries, and stable pages agents can cite.
HubbleField
Built for public-safe private-company discovery across web, REST, and MCP. Coverage and depth depend on published HubbleField profiles and launch state.
ROUTE OWNERSHIP
This page owns the commercial API/data-layer evaluation.
The technical API reference owns endpoints and OAuth detail. The MCP setup page owns agent installation. This page answers whether HubbleField is the right public-safe data layer for private-company discovery workflows.
RELATED PATHS
FAQ
What does HubbleField's private-company data API return?
It returns public-tier company profile fields such as identity, categories, geography, stage, public summary, source links, freshness state, profile URL, and approved access paths.
Is HubbleField a Companies House or registry replacement?
No. Registries remain the source for statutory facts and filings. HubbleField is a founder-supplied discovery layer for current public company context and agent-readable workflows.
Does the public API expose private diligence?
No. Cap tables, full financial models, customer lists, contracts, diligence files, unpublished listings, personal data, and sensitive raise material stay outside the public API layer.
Should builders use REST or MCP?
Use REST for direct HTTP integrations and MCP for agent tool calls. Both share the same public-tier disclosure boundary unless a separate permissioned route explicitly grants more.
Is HubbleField investment advice?
No. HubbleField is information only, not investment advice, not matching, not broker activity, and not an offer of securities in any jurisdiction.
SCHEMA DECISION
This page uses WebPage, BreadcrumbList, and visible FAQPage JSON-LD. It does not use Product, Offer, Dataset, SoftwareApplication, or APIReference schema because this is a commercial landing page for an information-only API surface, not a live public dataset catalogue or technical reference.