For Agents
Look up companies, directors, and filings across European and offshore business registries: search companies, fetch a profile by identifier, and list filings. Includes full-text individual search and typeahead suggestions.
Use for: I want to search for a company by name, Get a company's profile by its identifier, List a company's filings, Search for a director by name
Not supported: Does not handle credit scoring, payments, or sanctions screening. Use for looking up company, director, and filing records across registries only.
The DatoCapital API provides read-only access to companies, directors, and filings across major European business registries and a long tail of offshore jurisdictions. It searches and lists companies, returns a single company profile by its canonical identifier, and retrieves that company's filings. Full-text individual search, a typeahead suggest endpoint, and a country catalog support company and director research.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DatoCapital API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdatocapital.com%2Fdatocapital" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdatocapital.com%2Fdatocapital" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with DatoCapital API.
Search and list companies across European and offshore business registries
Fetch a single company profile by its canonical identifier
Retrieve a company's filings, most recent first
Run full-text search for individuals and directors
Resolve a registry id and country to a canonical company profile
Offer typeahead suggestions for companies and individuals
Read the supported country catalog
Patterns agents use DatoCapital API for, with concrete tasks.
★ Agent-Driven Company Due Diligence
An AI agent connected through Jentic can assemble a company dossier without a developer wiring the calls: it searches for a company by name, fetches the matching profile by its canonical identifier, and lists the company's filings most recent first. Because every endpoint is read-only, the agent can gather the records it needs to summarise an entity.
Search for a company by name, fetch its profile by identifier, and list its most recent filings
Director and Individual Lookup
Research and compliance workflows often start from a person rather than a company. The DatoCapital API runs a full-text search for individuals and returns a single individual's profile by opaque id. An agent can find a director and then pivot to the companies and filings connected to them.
Run a full-text search for a director's name and fetch the matching individual's profile
Cross-Registry Resolution
The same company can appear under different local registry numbers across jurisdictions. DatoCapital resolves a country and local registry number to a single canonical company profile, so an agent can normalise references from multiple sources onto one entity before enriching it with filings.
Resolve a country and local registry number to a canonical company profile and confirm the entity
11 endpoints — the datocapital api provides read-only access to companies, directors, and filings across major european business registries and a long tail of offshore jurisdictions.
METHOD
PATH
DESCRIPTION
/v3/companies
List or search companies
/v3/companies/{uec}
Single company profile
/v3/companies/{uec}/filings
Filings for a company
/v3/individuals
Full-text person search
/v3/individuals/{id}
Single individual profile
/v3/suggest
Typeahead suggestions
/v3/reference/countries
Country catalog
/v3/companies
List or search companies
/v3/companies/{uec}
Single company profile
/v3/companies/{uec}/filings
Filings for a company
/v3/individuals
Full-text person search
/v3/individuals/{id}
Single individual profile
/v3/suggest
Typeahead suggestions
/v3/reference/countries
Country catalog
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the DatoCapital API by hand means handling its bearer token prefixed dc_ and the problem-document error format it returns for failures. Through Jentic you install once, import DatoCapital from the API Directory, store the token once, and your agent calls it.
Permission scoping
The DatoCapital API is read-only and puts the company identifier in the URL path, so a rule can pin your agent to one company's profile and filings or to the search endpoints it needs. No operation can write, so a scoped agent can only read.
Credential isolation
Your DatoCapital token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find a company' or 'list filings', and Jentic returns the matching DatoCapital operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using DatoCapital API through Jentic.
What authentication does the DatoCapital API use?
The DatoCapital API authenticates with a bearer token per its OpenAPI spec: you send an Authorization header carrying a token prefixed dc_. A couple of health and readiness endpoints are public, while company, filing, and individual lookups require the token. Through Jentic it is stored once, encrypted, by your own Jentic One instance and injected at call time.
Can I look up company filings with the DatoCapital API?
Yes. You can search or list companies, fetch a single company profile by its canonical identifier, and retrieve that company's filings most recent first. Full-text individual search and a typeahead suggest endpoint round out the lookups.
What are the rate limits for the DatoCapital API?
The OpenAPI spec does not define rate limits for the DatoCapital API. Check the DatoCapital documentation at https://datocapital.com for current limits and plan entitlements.
Is there a DatoCapital MCP server?
You don't need an MCP server to connect your agent to the DatoCapital API. Jentic imports it directly from the API Directory: store your token once and your agent can search companies, read filings, and look up individuals. Operations are discovered on demand without loading another server's tool definitions into context.
Can I limit what my agent is allowed to do with the DatoCapital API?
Yes. The API is read-only, so a rule can allow just the company and filing reads your agent needs and nothing can modify data. Because lookups are read-only, the worst an over-broad rule allows is reading more records. Every call the agent makes is logged.
How do I search for a company with the DatoCapital API through Jentic?
Search Jentic for 'search for a company', and it returns the matching DatoCapital operations with their input schemas. Your agent searches companies, fetches a profile by identifier, and lists the filings in one run. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED