Install Jentic One Beta

Connect the GlobalEntity API to your agent

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

Resolve a company name and country to a single normalized golden record

Search a company register and fetch a stored golden record by id

Verify a VAT, EORI, or LEI identifier

Deduplicate a list of company names against canonical records

Retrieve an ownership graph with ultimate beneficial owner candidates

GET STARTED

Start building with GlobalEntity API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GlobalEntity API for, with concrete tasks.

★ Agent-Driven KYB Resolution

An AI agent onboards a business customer and needs one trustworthy company record before it proceeds. It resolves the company name and country to a golden record, verifies the VAT and LEI, and pulls the ownership graph to flag ultimate beneficial owners. Jentic exposes each GlobalEntity operation with its input schema so the agent sends the name, country, or identifier correctly on the first call.

Resolve a company by name and country to a golden record, verify its VAT and LEI, then retrieve its ownership graph

VAT and Identifier Verification

A billing system must confirm a counterparty's tax and legal identifiers before invoicing cross-border. The GlobalEntity API verifies VAT, EORI, and LEI values and can verify a bank account or IBAN, returning a normalized result regardless of the source register. The system records the verification against its own customer record.

Verify a company's VAT and EORI identifiers, then verify its IBAN before invoicing

Entity Monitoring

A compliance team watches a portfolio of companies for status changes rather than re-checking by hand. The GlobalEntity API creates monitoring subscriptions, lists them, updates or pauses them, and sends a test ping to a subscription's webhook so the team confirms delivery. Insolvency state can be checked on demand alongside the monitoring feed.

Create a monitoring subscription for a company with a webhook, then send a test ping to confirm the webhook receives events

Key Endpoints

15 endpoints — the globalentity api resolves a company name and country, or a registration number, to a single normalized company record drawn from european business registers and the global gleif lei index.

METHOD

PATH

DESCRIPTION

POST

/api/company/resolve

Resolve a company to a golden record

GET

/api/registry/search

Search a company register

GET

/api/verify

Verify VAT, EORI, or LEI

POST

/api/company/match

Deduplicate a list of company names

GET

/api/company/ownership

Retrieve an ownership graph with UBO candidates

GET

/api/company/insolvency

Check bankruptcy and insolvency state

POST

/api/monitor/subscriptions

Create an entity-monitoring subscription

POST

/api/company/resolve

Resolve a company to a golden record

GET

/api/registry/search

Search a company register

GET

/api/verify

Verify VAT, EORI, or LEI

POST

/api/company/match

Deduplicate a list of company names

GET

/api/company/ownership

Retrieve an ownership graph with UBO candidates

GET

/api/company/insolvency

Check bankruptcy and insolvency state

POST

/api/monitor/subscriptions

Create an entity-monitoring subscription

Why Jentic?

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

Setup

Wiring the GlobalEntity API by hand means managing its x-api-key header and learning the resolve, verify, ownership, and monitoring operations that unify dozens of per-country registers. Through Jentic you install once, import GlobalEntity from the API Directory, store the key once, and your agent calls it.

Permission scoping

GlobalEntity's lookups take the company name, country, or identifier in the request body or query, so a rule bounds which operations your agent may call, such as resolve and verify, not which company. You choose the operations it may call, so creating or deleting a monitoring subscription is not included unless you add them.

Credential isolation

Your GlobalEntity API 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 'resolve a company' or 'verify a VAT number', and Jentic returns the matching GlobalEntity operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using GlobalEntity API through Jentic.

What authentication does the GlobalEntity API use?

The GlobalEntity API authenticates with an API key sent in the x-api-key header on every request per its OpenAPI spec. Through Jentic that key is stored encrypted by your own Jentic One instance and injected at call time, so it never sits in your agent's prompt or logs.

Can I resolve a company with the GlobalEntity API?

Yes. You send a company name and country, or a registration number, to the resolve operation and get back a single normalized golden record with legal name, registration number, address, legal form, status, VAT, and LEI. The data comes back the same shape regardless of which European register it was drawn from.

What are the rate limits for the GlobalEntity API?

The GlobalEntity OpenAPI spec does not publish fixed rate limits. Responses are cached for speed, so repeated lookups of the same entity are inexpensive; pace fresh resolutions and back off on errors rather than assume an unlimited quota.

Is there a GlobalEntity MCP server?

You do not need an MCP server to give your agent the GlobalEntity API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls its operations. Operations are discovered on demand, so your agent's context stays lean instead of loading a full tool list up front.

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

Yes. Write a rule that allows only the search, resolve, and verify read operations, so the agent can look up and verify companies but cannot create or delete monitoring subscriptions, and every call it makes is logged. Subscription writes stay out of the allowed set until you add them.

How do I resolve a company with the GlobalEntity API through Jentic?

Search Jentic for 'resolve a company to a golden record', and it returns the GlobalEntity resolve operation with its input schema. Your agent sends the name and country and reads the normalized record back. To run it on your own infrastructure, install Jentic One from its GitHub repo.

GlobalEntity API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany DataapiKey15 EndpointsREST

For Agents

Resolve and normalize official company data across European registers and GLEIF, verify VAT, EORI, and LEI, deduplicate names, and monitor entity changes.

Use for: Resolve a company by name and country, Verify a VAT number, Search a business register for a company, Deduplicate a list of company names

Not supported: Does not run payments, score credit, or file documents with registers. Use for looking up and resolving official company data and monitoring entity changes only.

The GlobalEntity API resolves a company name and country, or a registration number, to a single normalized company record drawn from European business registers and the global GLEIF LEI index. It searches registers, verifies VAT, EORI, and LEI identifiers, deduplicates company-name lists, and returns ownership graphs with ultimate beneficial owner candidates. Insolvency checks, bank and IBAN verification, exportable KYB reports, and webhook-driven entity monitoring round out the surface.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

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: B+Signals: 4

24%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: D+Signals: 4

40%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

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

81%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the GlobalEntity API to your agent

Capabilities

Start building with GlobalEntity API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

GlobalEntity API

Jentic AI Readiness Score

GlobalEntity 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