Install Jentic One Beta

Connect the Limitguard.ai to your agent

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

Verify a Dutch or Belgian sales lead against the KVK or KBO register and return a verdict, lead score, and flags

Run a KYB check across registry, sanctions, VAT/VIES, and domain from a registration number and country

Screen a name against the OFAC, EU, and UN sanctions lists

Score an entity's risk from 0 to 100 from its name and country

GET STARTED

Start building with Limitguard.ai API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Limitguard.ai API for, with concrete tasks.

★ Agent-run lead qualification through Jentic

A sales or lead generation agent can check each inbound lead before it reaches the CRM: Limitguard confirms the company in the KVK or KBO register, validates the VAT number with VIES, checks the email domain's mail server, and screens the name for sanctions, then returns a verdict and a 0-100 lead score. Through Jentic the agent finds the lead verify operation by intent and loads its schema, so it qualifies leads without the developer wiring the call by hand.

Search Jentic for 'verify a sales lead', then verify a lead with country NL, company_number 12345678, name 'Acme B.V.', and email 'info@acme.nl', and report the verdict, lead score, and any flags.

KYB onboarding for business customers

Before onboarding a business customer or supplier, a compliance step runs a KYB check from the entity_id, registration_number, and country, covering the registry, sanctions lists, VAT/VIES, and the domain, and returns a kyb_status and trust_score. A deep check adds PEP ties, insolvency, and adverse media, and a compliance report on the entity can be built and later re-fetched by its check_id.

Run a KYB check with entity_id 'cust-001', registration_number '0123456789', and country BE, report the kyb_status and trust_score, then build a compliance report on the same entity by passing its entity_name and country.

Ongoing sanctions monitoring

Sanctions lists change daily. Limitguard's compliance alerts return changes to the OFAC, EU, and UN lists plus alerts when an entity or wallet your key already checked becomes listed, filterable by jurisdiction and severity, so a scheduled agent can poll for new hits.

Poll compliance alerts with severity set to high and a limit of 50, and list any hits on entities this key has checked.

Agent wallet trust checks

For agent-to-agent commerce, the agent check screens a wallet against sanctions, reads its balance, and confirms its ERC-8004 identity, and a separate operation returns an ERC-8004 agent's USDC balance on Base.

Check the wallet 0xabc123 with agent_id 'agent-42' and report its sanctions status and ERC-8004 identity.

Key Endpoints

20 endpoints — the limitguard api verifies the company behind a b2b sales lead against official business registers, with full coverage of the dutch kvk and belgian kbo registers, and cross-checks vat numbers with vies, mail servers, ibans, and the ofac, eu, and un sanctions lists.

METHOD

PATH

DESCRIPTION

POST

/v1/leads/verify

Verify a sales lead

POST

/v1/kyb/check

Run a KYB check

POST

/v1/entity/check

Verify an entity across registries and risk layers

POST

/v1/sanctions/screen

Screen a name against sanctions lists

POST

/v1/risk/score

Score an entity's risk

GET

/v1/compliance/alerts

Get sanctions changes and hits

POST

/v1/agent/check

Check an agent wallet

POST

/v1/keys/create

Create an API key

POST

/v1/leads/verify

Verify a sales lead

POST

/v1/kyb/check

Run a KYB check

POST

/v1/entity/check

Verify an entity across registries and risk layers

POST

/v1/sanctions/screen

Screen a name against sanctions lists

POST

/v1/risk/score

Score an entity's risk

GET

/v1/compliance/alerts

Get sanctions changes and hits

POST

/v1/agent/check

Check an agent wallet

POST

/v1/keys/create

Create an API key

Why Jentic?

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

Setup

Wiring Limitguard by hand means sending the X-API-Key header on the right operations, choosing between a prepaid key and x402 payment, and mapping each check's request body. Through Jentic you install once, import Limitguard from the API Directory, store the key once, and your agent calls it.

Permission scoping

Limitguard carries the company, name, and wallet in the request body, so rules bound which operations your agent may call, not which entity it checks. You choose the operations it may call, so ones that spend your balance, like the four key top-ups, are not included unless you add them.

Credential isolation

Your Limitguard 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 sales lead' or 'run a KYB check', and Jentic returns the matching Limitguard operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Limitguard.ai API through Jentic.

What authentication does the Limitguard API use?

Per its OpenAPI spec the Limitguard API takes an API key in the X-API-Key header, an lg_live_ key whose prepaid balance is debited per call. On the check and scoring operations the key is optional because an x402 payment can be sent instead, the balance top-up operations require the key, and key creation needs no authentication. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at request time.

Is there a Limitguard MCP server?

You don't need an MCP server to give your agent the Limitguard API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent discovers the lead, KYB, and sanctions operations on demand instead of loading a set of tool definitions into its context.

Can I verify a sales lead with the Limitguard API?

Yes, for Dutch and Belgian leads. The lead verify operation requires a country and checks the KVK or KBO register for status, legal form, start date, main activity, staff, and registered address, then cross-checks whatever else you send: VAT number with VIES, the email's mail server and disposable domain, IBAN country and bank, and the name against the OFAC, EU, and UN sanctions lists. Inputs you leave out are not checked and never count against the lead.

How much does the Limitguard API cost?

The spec describes pay-per-call pricing: lead verify at $0.27 per lead, the agent check at $0.75 per wallet, and entity and risk checks at $0.88 to $1.05 fresh or $0.11 cached, with KYB at $1.50 fresh. A free sandbox key from the key creation operation with tier set to sandbox returns mock data for entity, risk, and KYB checks at no charge.

What are the rate limits for the Limitguard API?

The OpenAPI spec does not specify rate limits. Check the Limitguard documentation at https://docs.limitguard.ai for current limits.

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

Yes. For example, write a rule that allows only the lead verify and sanctions screen operations, so the agent can qualify leads and screen names while the balance top-up operations, which spend money on your key, stay out of reach. Every call it makes is logged.

How do I screen a company for sanctions with the Limitguard API through Jentic?

Search Jentic for 'screen a name against sanctions lists', load the sanctions screen operation, and pass the name with an optional country. Jentic injects your X-API-Key at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Limitguard.ai

AI ReadinessFoundational (D)46/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthIdentity VerificationapiKey20 EndpointsREST

For Agents

Verify NL and BE sales leads, run KYB and entity trust checks, screen names against sanctions lists, and score entity risk and reputation.

Use for: I need to verify this lead is a real, active Dutch company, Screen this company name against sanctions lists, Run a KYB check on a Belgian supplier, Get the risk score for an entity in the Netherlands

Not supported: Does not verify individual identity documents, enrich contact records with phone numbers, or send outreach. Use for company lead verification, KYB, and sanctions screening only.

The Limitguard API verifies the company behind a B2B sales lead against official business registers, with full coverage of the Dutch KVK and Belgian KBO registers, and cross-checks VAT numbers with VIES, mail servers, IBANs, and the OFAC, EU, and UN sanctions lists. Each lead check returns a verdict, a 0-100 lead score, and flags with one action per flag. Beyond leads it runs KYB checks, entity risk and reputation scores, deep checks for PEP ties, insolvency, and adverse media, sanctions screening by name, and agent wallet checks, and it can be paid per call with a prepaid key or an x402 payment in USDC.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

97%

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: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

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: FSignals: 4

41%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

49%

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: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Limitguard.ai to your agent

Capabilities

Start building with Limitguard.ai API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Limitguard.ai

Jentic AI Readiness Score

Limitguard.ai

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