Install Jentic One Beta

Connect the Textkernel Parser API to your agent

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

Parse a document

Manage hr recruiting data programmatically

Integrate Textkernel Parser API into automated workflows

Query and filter Textkernel Parser API records by parameters

Monitor Textkernel Parser API operational status and events

GET STARTED

Start building with Textkernel Parser API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Textkernel Parser API for, with concrete tasks.

★ HR and Recruiting Operations

Use the Textkernel Parser API to perform hr recruiting operations programmatically. The API provides 1 endpoints covering core functionality including parse a document.

Call POST /match/extract.do to parse a document

Data Retrieval and Monitoring

Query Textkernel Parser API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary Textkernel Parser API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Textkernel Parser API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'parse a document', load the operation schema, and execute with Jentic-managed credentials

Why Jentic?

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

Setup

Wiring the Textkernel Parser by hand means setting up its HTTP basic auth against rest.textkernel.com and handling the document extraction call yourself. Through Jentic you install once, import Textkernel from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The Textkernel Parser exposes a single extraction operation at /match/extract.do, so you limit the agent to just that operation and nothing else. Because that is the only call you grant, the agent can parse a document but cannot reach any other functionality.

Credential isolation

Your Textkernel basic auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'parse a resume document', and Jentic returns the matching Textkernel operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Textkernel Parser API through Jentic.

What authentication does the Textkernel Parser API use?

The Textkernel Parser API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I parse a document with the Textkernel Parser API?

Yes. Use the POST /match/extract.do endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Textkernel Parser API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I parse a document through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'parse a document'. Jentic returns the matching Textkernel Parser API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Textkernel Parser API have?

The Textkernel Parser API exposes 1 endpoints covering parsing operations.

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

Yes. Because you run Jentic One yourself, you decide which operations and credentials your agent may use. The Textkernel Parser API exposes a single document-extraction operation at POST /match/extract.do, so you can grant the agent only that call and nothing more. With just that operation allowed, the agent can parse a CV, resume, or job document but cannot reach any other functionality, and your basic auth credentials stay stored on your own instance rather than in the agent's context.

Textkernel Parser API

AI ReadinessNon-Ready (F)40/100

See full scorecard

Official vendor OpenAPI document · agent-readyHR recruitingRecruiting Atsbasic1 EndpointsREST

For Agents

Programmatically parse a document. Covers 1 operations with basic authentication.

Use for: I need to parse a document, Find available hr recruiting operations, Get the current status of Textkernel Parser API resources, List all records from Textkernel Parser API

Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.

CV/Resume and job document parsing API that extracts structured data from documents. The API exposes 1 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

75%

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

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

22%

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.

50%

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

10%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Textkernel Parser API to your agent

Capabilities

Start building with Textkernel Parser API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Textkernel Parser API

Jentic AI Readiness Score

Textkernel Parser 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