Install Jentic One Beta

Connect the Klarix Intelligence API to your agent

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

Write a competitor battlecard with SWOT, positioning seams, landmines, and talk tracks from a competitor_domain

Score a prospect's ICP fit on five axes with a 7+/10 pursue threshold and cited rationales

Search pre-profiled B2B companies for lookalike prospects with filters such as headcount, revenue, countries, and required_tech

Detect account triggers like leadership changes, funding, and hiring surges within a chosen timeframe_days

GET STARTED

Start building with Klarix Intelligence API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Klarix Intelligence API for, with concrete tasks.

★ AI agent sales research through Jentic

A sales agent preparing for a call searches Jentic for 'build a competitor battlecard', loads the Klarix battlecard operation with its input schema, and passes the competitor_domain plus your own company details. Your own Jentic One instance injects the Klarix key at call time, and every claim in the returned battlecard carries a source URL the rep can check.

Call POST /v1/intelligence/battlecard with competitor_domain 'competitor.com', our_company_name 'Acme', and our_domain 'acme.com', then summarise the landmines and talk tracks

ICP fit scoring before outreach

Before a rep invests time, the agent scores the account on five ICP axes from 1 to 10 with cited rationales, using company_name and domain plus your icp_description. Accounts at or above the 7/10 pursue threshold go into an outreach sequence that opens on a researched, dated fact and writes to a role rather than a named person.

Call POST /v1/intelligence/prospect-fit with company_name 'Globex' and domain 'globex.com'; if the score passes the pursue threshold, call POST /v1/intelligence/outreach with buyer_role 'VP Engineering'

Lookalike prospect discovery

A team expanding into a new segment describes its ideal customer in plain language and filters by headcount, revenue, countries, and required_tech. The prospect match operation returns ranked accounts with their tech stack, growth signals, and a suggested next move, and can exclude domains already in the pipeline.

Call POST /v1/prospects/match with icp_or_query 'mid-market logistics SaaS using Snowflake', countries ['US'], and exclude_domains from the current pipeline

Account trigger monitoring

An account team checks named accounts for inflection points such as leadership changes, funding, hiring surges, product updates, or regulatory events within a set number of days, then pulls a tech-stack teardown for any account that shows a trigger.

Call POST /v1/intelligence/triggers with target_domain 'initech.com' and timeframe_days 90, then POST /v1/intelligence/tech-stack for the same domain if any trigger is found

Key Endpoints

18 endpoints — the klarix intelligence api produces competitive and account intelligence for sales teams from public web sources, with a resolvable source url on every factual claim.

METHOD

PATH

DESCRIPTION

POST

/v1/intelligence/battlecard

Competitor battlecard

POST

/v1/intelligence/prospect-fit

5-axis ICP fit score

POST

/v1/prospects/match

Semantic lookalike prospect search

POST

/v1/intelligence/triggers

Detect account triggers

POST

/v1/intelligence/tech-stack

Tech-stack teardown

POST

/v1/intelligence/company

Company one-pager from cited sources

GET

/v1/whoami

Key, plan, credits, and callable tools

POST

/v1/intelligence/battlecard

Competitor battlecard

POST

/v1/intelligence/prospect-fit

5-axis ICP fit score

POST

/v1/prospects/match

Semantic lookalike prospect search

POST

/v1/intelligence/triggers

Detect account triggers

POST

/v1/intelligence/tech-stack

Tech-stack teardown

POST

/v1/intelligence/company

Company one-pager from cited sources

GET

/v1/whoami

Key, plan, credits, and callable tools

Why Jentic?

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

Setup

Wiring Klarix by hand means choosing between bearer and X-Api-Key auth, tracking which operations need a PRO plan, and passing your own company context on every request. Through Jentic you install once, import Klarix from the API Directory, store the key once, and your agent calls it.

Permission scoping

Klarix carries its targets, such as competitor_domain and target_domain, in the request body, so limit the agent to the operations it needs, such as battlecards and fit scores. Rules bound which operations your agent may call, not which company it researches, so credit-spending operations you have not picked are not included unless you add them.

Credential isolation

Your Klarix 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 'build a competitor battlecard' or 'find lookalike prospects', and Jentic returns the matching Klarix operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Klarix Intelligence API through Jentic.

What authentication does the Klarix Intelligence API use?

Per its OpenAPI spec, the Klarix Intelligence API accepts the same Klarix key either as a bearer token in the Authorization header or in the X-Api-Key header, for callers behind a proxy that strips Authorization. Keys on the query string are rejected. GET /v1/health and GET /v1/tools are open, and GET /v1/whoami works with or without a key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

Does every Klarix call cost credits?

The intelligence and prospect operations each spend one credit per call, and some need a minimum plan: the battlecard works on FREE, while prospect match and prospect fit need PRO. GET /v1/whoami shows your plan, remaining credits, and the tools your key can call.

What are the rate limits for the Klarix Intelligence API?

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

Is there a Klarix MCP server?

You don't need an MCP server to give your agent the Klarix Intelligence API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the battlecard, prospect, and research operations on demand without loading another server's tool definitions into its context.

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

Yes. For example, write a rule that allows only POST /v1/intelligence/battlecard and GET /v1/whoami, so the agent can produce battlecards and check remaining credits but cannot run PRO-plan prospect searches that spend credits elsewhere. Every call it makes through your instance is logged.

How do I score a prospect's ICP fit through Jentic?

Search Jentic for 'score prospect fit', load the Klarix prospect fit operation, and call POST /v1/intelligence/prospect-fit with the required company_name and domain, plus an icp_description if you have one. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Does the Klarix Intelligence API return contact details?

No. Klarix works from public web sources and returns no emails, phone numbers, or licensed contact rows. Buying committee maps and outreach sequences describe roles and title patterns, not named people.

Klarix Intelligence API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer, apiKey18 EndpointsREST

For Agents

Generate cited battlecards, SWOTs, ICP fit scores, account trigger reports, tech-stack teardowns, and lookalike prospect lists from public web sources with Klarix.

Use for: Build a battlecard against a competitor's domain, Score whether this company fits our ICP, Find companies similar to our best customers, Check whether a target account has had any funding or leadership changes recently

Not supported: Does not return contact emails or phone numbers, send outreach, or store CRM records. Use for cited competitive, account, and prospect research only.

The Klarix Intelligence API produces competitive and account intelligence for sales teams from public web sources, with a resolvable source URL on every factual claim. It writes competitor battlecards, head-to-head analyses, SWOTs, market landscapes, and displacement playbooks, scores a prospect's ICP fit on five axes, maps buying committees, detects account triggers such as funding or leadership changes, and tears down a company's tech stack. A semantic prospect search returns ranked lookalike accounts, and responses contain no emails, phone numbers, or licensed contact rows.

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

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

67%

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

52%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

83%

OperationId Quality

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

51%

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: CSignals: 1

55%

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

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Klarix Intelligence API to your agent

Capabilities

Start building with Klarix Intelligence API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Klarix Intelligence API

Jentic AI Readiness Score

Klarix Intelligence 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