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

# Dabradata Dabra API

The Dabra API is a Brazilian data-lookup service that resolves people and companies by CPF or CNPJ and returns registration, compliance, credit, and public-record data. It covers federal and state registries, domestic and international sanctions lists, politically exposed person and anti-money-laundering checks, credit scores and history, court processes, and reference data such as postal codes and vehicles. Every account has a test key that returns each endpoint's example response at zero cost, marked with a response header, using the same parameter validation as production.

## For AI agents

Resolve Brazilian people and companies by CPF or CNPJ and return registration, compliance, credit, and public-record data, including sanctions, PEP, AML, credit scores, and court processes.

## Scope

Does not handle payments, document signing, or accounting. Use for Brazilian registry, compliance, and background data lookups only.

## Capabilities

- Look up personal and company registration data by CPF or CNPJ
- Screen individuals and companies against domestic and international sanctions lists
- Check politically exposed person, anti-money-laundering, and adverse-media exposure
- Retrieve credit scores and credit history
- Query court processes, debt certificates, and regulatory sanctions
- Validate reference data such as postal codes, vehicles, and driver licenses

## Use cases

### Agent-driven background checks

An AI agent running due diligence on a Brazilian counterparty can resolve a CPF or CNPJ and pull registration, sanctions, PEP, and credit data in one workflow. Because the Dabra API offers a test key that returns example responses at zero cost with the same validation as production, the agent's integration can be built and exercised before any paid call is made.

Example prompt: Resolve a CNPJ to its company registration, then screen the company against sanctions lists and read any adverse-media exposure

### Sanctions and PEP screening

Compliance teams must screen counterparties against sanctions and politically exposed person lists. The Dabra API checks OFAC, the UN consolidated list, EU and UK sanctions, Interpol, and PEP exposure, so an agent can run a full screen against several authorities from one integration rather than wiring each list separately.

Example prompt: Screen a person against the OFAC and UN sanctions lists and check their politically exposed person status

### Credit risk lookups

Lenders assessing a Brazilian applicant need credit scores and history tied to a CPF or CNPJ. The Dabra API returns credit scores, credit history summaries, and negative records, so a risk workflow can pull the figures it needs and record which registry each came from. Reference lookups like vehicle and postal data round out an applicant profile.

Example prompt: Retrieve the credit score and credit history for a CPF and read any negative records attached

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/consulta/dados-cadastrais-basicos` | Basic registration lookup by CPF |
| GET | `/api/v1/consulta/cadastro-pj-basica` | Basic company registration lookup by CNPJ |
| GET | `/api/v1/consulta/receita-federal-pj` | Company data at the federal revenue service |
| GET | `/api/v1/consulta/ofac-sancoes` | OFAC sanctions screening |
| GET | `/api/v1/consulta/pep-exposicao` | Politically exposed person exposure |
| GET | `/api/v1/consulta/score-credito-quod` | Credit score |
| GET | `/api/v1/consulta/processos-completa` | Full court process records |
| GET | `/api/v1/consulta/cep` | Postal code lookup |

## Key resources

- **Registration** — Resolve people and companies by CPF or CNPJ against federal and state registries
- **Compliance** — Screen against domestic and international sanctions, PEP, AML, and adverse media
- **Credit** — Credit scores, credit history, and negative records
- **Public records and reference** — Court processes, debt certificates, postal codes, and vehicle data

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 78 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 74 / 100
  - Security: 50 / 100
  - AI Discoverability: 83 / 100
- **View full report:** https://jentic.com/apis/dabradata.com/dabradata/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 Dabra API by hand means handling its X-API-Key header auth, the test-key-versus-production flow, and the many distinct lookup shapes across registries yourself. Through Jentic you install once, import Dabra from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The CPF or CNPJ travels as a request parameter, not in the URL path, so a rule bounds which operations your agent may call rather than which identifier it queries. You choose the operations it may call, such as specific registry and sanctions lookups, so the SMS and OTP sending operations are not included unless you add them.
- **Credential handling:** Your Dabra key 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 'look up a company by CNPJ' or 'screen a person against sanctions', and Jentic returns the matching Dabra operation with its input schema so the agent calls the right endpoint without browsing the full lookup list.

## Related APIs

- **OpenSanctions** — OpenSanctions provides global sanctions and watchlist data, where Dabra combines sanctions with Brazilian registry and credit data.
- **Clearbit** — Clearbit adds international firmographic data alongside Dabra's Brazilian records.
- **FullContact** — FullContact resolves a contact's identity across email and social profiles to complement Dabra's registry data.

## FAQ

### What authentication does the Dabra API use?

The Dabra API authenticates with an API key sent in the X-API-Key header, as declared in its OpenAPI spec. A test key prefixed dabra_test_ returns each endpoint's example response at zero cost with the same parameter validation as production. Through Jentic the key is stored once and injected at call time, so it never appears in your agent's prompt or logs.

### Which sanctions lists can I screen against with the Dabra API?

The Dabra API screens against several authorities, including OFAC, the UN consolidated list, EU and UK sanctions, Interpol, and politically exposed person exposure, so an agent can run a broad screen from a single integration.

### What are the rate limits for the Dabra API?

The OpenAPI spec does not state numeric rate limits for the Dabra API. Check the vendor documentation at https://dabradata.com for current limits before running high-volume lookups.

### How do I look up a company through Jentic with the Dabra API?

Search Jentic for 'look up a company by CNPJ', which returns the GET `/api/v1/consulta/cadastro-pj-basica` operation with its input schema, then call it with the identifier. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the Dabra API?

Yes. Write a rule that allows only the lookup operations your workflow needs, such as company registration and sanctions checks, so the agent can query that data but cannot send SMS or OTP messages, and every call it makes is logged. The CPF or CNPJ travels as a request parameter, so the rule bounds which operations run rather than which identifier is queried.