Available
Obtainable from the official source for relevant covered entities; not necessarily present for every company.
Field-level company data
Official registries do not publish one universal schema. Zephira maps legal-entity, director, shareholder, financial and corporate-linkage fields to their source, then separates registry facts from digitisation, resolution and enrichment.
Availability depends on jurisdiction, legal form, filing obligations and source access. A missing field is not evidence that the underlying fact does not exist.legal_nameGlobal Data Intelligence LimitedRegistry-sourcedregistration_identifier09410808Registry-sourcedcompany_statusActiveRegistry-sourcedfiled_financialsStructured document valuesDigitisedcorporate_linkagesResolved relationshipsLinkage-derivedAvailability model
These states describe public official-source availability in the reviewed scope. They are not a promise that every relevant company has filed the field.
Obtainable from the official source for relevant covered entities; not necessarily present for every company.
Obtainable through a paid official document, extract or access channel.
Limited by entity type, period, filing threshold or the attributes the source publishes.
Both disclosure limits and paid official access conditions apply.
Not published or not reliably retrievable from the public official source in the reviewed scope.
Official-source review
The matrix records whether each dataset is available through public official sources, behind an official paywall, limited in scope or unavailable. It does not represent the complete Zephira commercial coverage catalogue.
| Dataset | Available | Paywall | Partial | Partial / paid | Unavailable |
|---|---|---|---|---|---|
| Core registry dataLegal identity and registration fields | 59 | 7 | 1 | 0 | 0 |
| Directors & officersCurrent or historical appointments | 38 | 22 | 0 | 6 | 1 |
| ShareholdersDisclosed individual and corporate owners | 3 | 9 | 22 | 17 | 16 |
| Group structureParent, subsidiary and relationship evidence | 1 | 0 | 28 | 29 | 9 |
| Filed financialsAccounts, filings and structured figures | 18 | 11 | 17 | 3 | 18 |
How to read “partial”Entity-type limits, historical limits, filing thresholds and published-attribute limits can all narrow availability.
How to use this reviewStart at dataset level, then confirm the required jurisdiction, company type, period and access method.
Field availability workbench
Representative fields show what the family can contain. Actual records return only what the relevant source, filing and entity support.
The stable company identity used to anchor every other field and relationship.
Source: Official company registry
Lineage: Registry-sourced
Current or historical appointments returned only where the relevant source discloses them.
Source: Registry record or official filing
Lineage: Registry-sourced / normalised
Disclosed individual and corporate owners, with the local filing context kept visible.
Source: Official ownership filing or extract
Lineage: Registry-sourced / linkage-derived
Structured values digitised from accessible filed accounts without losing their document context.
Source: Filed accounts or annual report
Lineage: Digitised from filing
Parent, subsidiary and people-to-company relationships supported by evidence or labelled derivation.
Source: Registry evidence and resolved entities
Lineage: Entity-resolved / linkage-derived
Operational context added around the legal entity and kept separate from official registry facts.
Source: Identified enrichment sources
Lineage: Firmographic enrichment
Interpreting gaps
Company data can be absent for very different reasons. Dependable workflows preserve that uncertainty instead of converting it into an unsupported negative conclusion.
The official source does not publish the requested attribute for that jurisdiction or entity type.
The company has no applicable filing, or the expected document has not yet been submitted or published.
The field is available only through a paid extract, gated channel or other source condition.
The input could not be matched to one legal entity with enough evidence to return the field safely.
Registry first, not registry only
Official company record or filing.
Mapped into a consistent field.
Matched to the legal company.
Structured from a filed document.
Added context, clearly labelled.
No. Registry disclosure rules, legal forms, filing obligations and source access conditions differ by jurisdiction. Zephira normalises common fields while preserving those local limits.
Not uniformly. Directors, officers, shareholders and ownership data are returned where the appropriate official source publishes them and access is permitted.
No. A missing field can mean the source does not disclose it, the relevant filing is unavailable, access is restricted or the record could not be resolved. It should not be interpreted as proof that no relationship exists.
Financial fields are structured from accessible company accounts and other filed financial documents. The available periods and line items depend on local filing rules and the source documents.
Registry-sourced fields begin in an official company record or filing. Enriched fields add operational context from identified sources. Zephira keeps those classifications distinguishable.
Yes. Send the required jurisdictions, company types and fields, and the Zephira team can review the applicable official sources and delivery conditions before you commit.
Yes. Company data can be delivered through company search, REST API, bulk feeds and MCP for AI agents, subject to source availability, licensing and the selected access model.
company-data field availability is part of Zephira's registry-sourced company-data platform. Field availability explains which identity, people, ownership, financial and relationship fields can be returned by jurisdiction and source.
Compliance, risk, data, product and AI teams use company-data field availability when they need structured company facts with clear provenance.
Official company registries and filed company documents are the starting point. Source context is retained so users can trace material facts.
Confirm the fields