Install Jentic One Beta

Connect the Jsonpage API to your agent

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

Search companies by name across every served country or find one by registry_id, with active-only filtering

Look up a company by global identifier and add optional include blocks such as officers, owners, financials, sanctions, and legal_events

Resolve up to 100 company identifiers in one batch call, with per-item errors for invalid or unknown ids

Check a company identifier, SIRET, VAT number, and EORI number together and get a single valid result

GET STARTED

Start building with Jsonpage API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Jsonpage API for, with concrete tasks.

★ Agent Supplier Verification via Jentic

An AI agent processing supplier onboarding calls the Jsonpage validate operation with the company identifier and VAT number from the form, and reads back a single valid flag with each check's result and the matching company record. Through Jentic the agent finds the operation by intent and calls it with your stored key, then fetches the sanctions and owners blocks before approving the supplier.

Validate company id 'BE-0417497106' together with its VAT number, then look up the company with include=sanctions,owners and report whether it is safe to onboard

Form Autocomplete for Company Fields

Signup and checkout forms call the autocomplete endpoint with the text a user has typed, optionally limited to active companies, and fill in the company name, identifier, and address from the chosen suggestion. Name search ignores case, accents, punctuation, and legal forms such as SA or LTD, so 'dano' finds DANONE.

Call autocomplete with q 'dano' and status 'active', pick the top suggestion, and return its identifier and registered address

Customer Portfolio Monitoring

Credit and compliance teams add each customer to the monitoring list with a PUT on its identifier, which records today's state as the baseline. Later differences against registers, legal notices, beneficial ownership information, and sanctions lists appear as events, which are read with an after cursor or delivered by signed webhook, and are kept 90 days.

Start monitoring companies 'FR-552032534' and 'GB-00445790', then list events after the last processed event id and summarise any ownership or status changes

Customs Number Checks for Shipping

Logistics teams check an EORI number by calling the EORI endpoint with the number and, optionally, the expected company_name before booking a cross-border shipment. The same check can run inside the validate call alongside the VAT number.

Check the EORI number from a shipping form with company_name 'Danone' and report whether it is valid and matches that company

Key Endpoints

14 endpoints — the jsonpage api returns official company register data for 14 countries, including france, belgium, switzerland, the united kingdom, the nordic and baltic states, ireland, australia, singapore, and japan, in one record format keyed by a global identifier such as fr-552032534.

METHOD

PATH

DESCRIPTION

GET

/companies

Search companies by name or registry number

GET

/companies/{id}

Look up a company by global identifier

POST

/companies/batch

Look up up to 100 companies

GET

/validate

Check identifier, SIRET, VAT, and EORI

GET

/autocomplete

Suggest companies as the user types

PUT

/monitors/{id}

Start monitoring a company

GET

/events

List detected events

GET

/companies

Search companies by name or registry number

GET

/companies/{id}

Look up a company by global identifier

POST

/companies/batch

Look up up to 100 companies

GET

/validate

Check identifier, SIRET, VAT, and EORI

GET

/autocomplete

Suggest companies as the user types

PUT

/monitors/{id}

Start monitoring a company

GET

/events

List detected events

Why Jentic?

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

Setup

Wiring Jsonpage by hand means sending its `X-API-Key` header, learning each country's identifier format and check digits, and handling the plan rate limit where each company in a batch counts as one request. Through Jentic you install once, import Jsonpage from the API Directory, store the key once, and your agent calls it.

Permission scoping

Jsonpage puts the company identifier in the URL path (/companies/{id}, /monitors/{id}), so a rule can pin your agent to the companies and operations you pick. You choose the operations it may call, so changes like adding or removing monitors are not included unless you add them.

Credential isolation

Your Jsonpage 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 'verify a VAT number' or 'look up a company by registry number', and Jentic returns the matching Jsonpage operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Jsonpage API through Jentic.

What authentication does the Jsonpage API use?

The Jsonpage API authenticates with an API key sent in the `X-API-Key` header, per its OpenAPI spec. Keys are created in the Jsonpage dashboard, a rotated key keeps working for 24 hours, and on the Pro plan keys can be restricted to allowed IP addresses. The three health endpoints are open and need no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Is there a Jsonpage MCP server?

You don't need an MCP server to give your agent Jsonpage. Jentic connects it directly from the API Directory: import it, store your key once, and your agent searches, verifies, and monitors companies as it needs to. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

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

Yes. For example, write a rule that allows only the validate, autocomplete, and company lookup operations, so an onboarding agent can check and read companies but cannot add or remove monitors. Because the company identifier sits in the path, a rule on /companies/{id} can also hold an agent to one company, and every call it makes is logged.

Which countries does the Jsonpage API cover?

Per its OpenAPI spec, the Jsonpage API serves company data for 14 countries: France, Belgium, Switzerland, the United Kingdom, Norway, Finland, Latvia, Ireland, Sweden, Estonia, Lithuania, Australia, Singapore, and Japan. Identifiers take the country code, a hyphen, and the national registry number, for example GB-00445790 or JP-1180301018771.

What are the rate limits for the Jsonpage API?

The Jsonpage OpenAPI spec says requests count against a plan rate limit, with each company in a batch call counting as one request, and a free plan has a daily cap; exceeding either returns a rate_limit_exceeded or daily_limit_reached error with a Retry-After delay. The spec does not publish the numbers, so check https://jsonpage.com for your plan's limits.

How do I verify a VAT number with the Jsonpage API through Jentic?

Search Jentic for an intent like 'verify a company VAT number', import Jsonpage from the API Directory, and store your API key once. Your agent then calls GET /validate with the vat parameter, adding id or siret to check them together, and reads the valid flag and the matching company record. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Jsonpage API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany DataapiKey14 EndpointsREST

For Agents

Look up and verify companies in 14 countries from official registers: search by name or registry number, pull officers, owners, financials, and sanctions blocks, validate VAT, SIRET, and EORI numbers, and monitor companies for changes.

Use for: I need to verify this supplier's VAT number before paying the invoice, Find the French company called Danone and get its registry number, Get the officers and owners of company FR-552032534, Check whether this EORI number is valid for customs

Not supported: Does not handle credit scoring, contact enrichment, or company filings documents. Use for company register lookups, identifier validation, and change monitoring only.

The Jsonpage API returns official company register data for 14 countries, including France, Belgium, Switzerland, the United Kingdom, the Nordic and Baltic states, Ireland, Australia, Singapore, and Japan, in one record format keyed by a global identifier such as FR-552032534. A lookup can add optional blocks such as address, establishments, VAT, EORI, officers, financials, owners, sanctions, and legal events, and a batch call resolves up to 100 companies at once. For forms it suggests companies as a user types and checks a company identifier, SIRET, VAT number, and EORI number in one call. Monitoring compares watched companies against the registers, legal notices, beneficial ownership data, and sanctions lists, records each change as an event, and can deliver events as signed webhooks.

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.

Specification Validity

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

100%

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

27%

Example Density

How richly the API is illustrated with examples.

97%

Example Validity

Percentage of examples that conform to their schemas.

66%

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: C-Signals: 4

48%

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.

57%

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 Jsonpage API to your agent

Capabilities

Start building with Jsonpage API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Jsonpage API

Jentic AI Readiness Score

Jsonpage 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