canonical: https://jentic.com/apis/datocapital.com/datocapital

# DatoCapital API

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.

## For AI 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.

## Scope

Does not handle credit scoring, payments, or sanctions screening. Use for looking up company, director, and filing records across registries only.

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Resolve a country and local registry number to a canonical company profile and confirm the entity

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v3/companies` | List or search companies |
| GET | `/v3/companies/{uec}` | Single company profile |
| GET | `/v3/companies/{uec}/filings` | Filings for a company |
| GET | `/v3/individuals` | Full-text person search |
| GET | `/v3/individuals/{id}` | Single individual profile |
| GET | `/v3/suggest` | Typeahead suggestions |
| GET | `/v3/reference/countries` | Country catalog |

## Key resources

- **Companies** — Search or list companies, fetch a profile by identifier, and resolve registry ids.
- **Filings** — Retrieve a company's filings, most recent first.
- **Individuals** — Full-text search for individuals and fetch a single profile by id.
- **Reference** — Read the supported country catalog and typeahead suggestions.

## AI readiness

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.

- **Score:** 56 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 34 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 61 / 100
- **View full report:** https://jentic.com/apis/datocapital.com/datocapital/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Acuris** — Compliance and company search across global registries and watchlists.
- **6sense** — B2B company firmographic and intent data for sales and marketing.
- **AgentFilings** — US company registration and registered-agent filings data.

## FAQ

### 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.