What the official source provides
Latvia's Enterprise Register information portal exposes an anonymous public backend for legal-entity search and profile retrieval. Supported public endpoints can return officers, members, shareholders, beneficiaries and document metadata.
The meaning of each row remains source-specific. A public member or shareholder record can be direct relationship evidence. A beneficiary row is evidence only when the source returns it. An empty or hidden array can reflect source disclosure limits and must not be described as proof that no relationship exists.
Document metadata is publicly visible in supported buckets, while direct anonymous binary download is currently blocked in the implemented path.
What dossaro adds
dossaro connects those public source operations for an AI agent:
- search and resolve a Latvian legal entity;
- retrieve the public company profile;
- request officer, member, shareholder or beneficiary rows separately;
- preserve source-native relationship labels and identifiers;
- list public document metadata;
- return a typed blocked state for unsupported binary retrieval;
- keep hidden or empty source arrays visible as limitations.
For ownership interpretation, continue with how to find private-company owners rather than treating one relationship response as a complete control graph.
Agent workflow
- Start with the registered name or Latvian entity code.
- Resolve the exact company and retain source-native identifiers.
- Retrieve the public profile and legal context.
- Request relevant officer, member, shareholder or beneficiary surfaces independently.
- Preserve the relationship type and source field exactly.
- List public document metadata when the assignment needs filing context.
- Do not attempt unsupported binary parsing from metadata alone.
- Report hidden arrays, empty responses and blocked binaries explicitly.
For a regional longlist, the result can be composed with the Czech ARES workflow inside the company research agent pattern.
Evidence and outputs
Strong inputs include:
- Latvian entity code;
- exact registered name;
- requested role or relationship type;
- relevant date;
- whether document metadata is required.
| Output | Research use |
|---|---|
| Resolved legal entity | Anchors all later source calls |
| Public company profile | Supplies registered identity and status context |
| Officer or member row | Provides source-backed role evidence |
| Shareholder or beneficiary row | Preserves the relationship the source actually exposes |
| Document metadata | Identifies public filing buckets without claiming a readable binary |
| Limitation | Separates hidden, empty and blocked evidence states |
When document review is central, use the company-register documents workflow and keep the blocked binary state intact.
Coverage and limitations
- Public relationship rows are returned only where the Latvia Enterprise Register exposes them.
- Hidden member arrays and empty beneficiary arrays are source limitations, not negative ownership facts.
- A public direct shareholder or member is not automatically the ultimate beneficial owner.
- Public document metadata does not guarantee anonymous binary access.
- Direct document binary download is currently blocked in the implemented public-free path.
- Register data can lag private transactions or later filings.
- Similar names require entity-code verification.
- dossaro supplies evidence and limitations, not legal or investment advice.
Run this exact task
Install dossaro, then continue the research
The setup guide lets a capable agent add the remote MCP, start OAuth with the user and return to this task.
Review the dossaro MCP setup guide at https://dossaro.com/agent-setup/prompt.md, configure dossaro when possible, complete OAuth with the user, then perform this task: Resolve this exact Latvian legal entity, retrieve its public profile and relevant officer, member, shareholder or beneficiary evidence, preserve source labels and dates, list public document metadata where useful, and report hidden arrays or blocked binaries without turning missing records into negative ownership findings.Capability graph
Related capabilities
Czech ARES API for company and relationship research
Data sourceResolve Czech companies and review linked-register roles, shareholder or partner rows and filing metadata with an AI agent.
Company register documents for due diligence
Use caseFind, retrieve and review official company-register documents with source references and explicit access limitations.
How to find who owns a private company in Europe
Use caseResearch direct shareholders and ownership evidence for European private companies using official register documents.
Company research agent with official source evidence
Use caseGive an AI agent a repeatable company-research workflow built on official profiles, filings, documents and explicit limitations.
