Textkernel Parser API
✓ Official Vendor SpecHR 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.
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.
1
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" | sh2
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 instanceJentic 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
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
Key Endpoints
1 endpoints — cv/resume and job document parsing api that extracts structured data from documents.
METHOD
PATH
DESCRIPTION
POST
/match/extract.do
Parse a document
POST
/match/extract.do
Parse a document
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.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
GET STARTED