Install Jentic One Beta

Connect the Dabra API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dabra 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%2Fdabradata.com%2Fdabradata" | sh

Step 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%2Fdabradata.com%2Fdabradata" | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Dabra API.

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

GET STARTED

Start building with Dabra API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Dabra API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

132 endpoints — 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.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Dabra API through Jentic.

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.

Dabradata Dabra API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany DataapiKey132 EndpointsREST

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

Use for: Look up a company by its CNPJ, Screen a person against sanctions lists, Check whether an individual is a politically exposed person, Retrieve a credit score for a CPF

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

39%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

71%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

96%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

74%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

83%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Dabra API to your agent

Capabilities

Start building with Dabra API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Dabradata Dabra API

Jentic AI Readiness Score

Dabra API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness