Install Jentic One Beta

Connect the HebrewCore API to your agent

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

Translate text or a batch of strings into Hebrew, English, or Russian with a quality tier of fast, balanced, or smartest

Protect prices, dates, codes, and listed protected_terms so they survive translation exactly as written

Keep an account list of protected terms such as drug and brand names, added by upsert and removed by id

Detect the language of code-switched Hebrew and English input and analyse its text direction

GET STARTED

Start building with HebrewCore API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HebrewCore API for, with concrete tasks.

★ Agent-run Hebrew localisation

An AI agent localising an app's interface strings into Hebrew needs translations that leave placeholders, prices, and product names untouched. Through Jentic the agent searches for 'translate text into Hebrew', loads the HebrewCore batch operation, and sends the strings with target_lang he and protect enabled, with the bearer key injected at call time. The response carries direction metadata, so the agent can flag strings that need RTL layout.

Call POST /v1/translate/batch with items Welcome to your account and Your order total is $49.99, target_lang he, and protect true, then return the Hebrew strings

Clinical content for Hebrew-speaking patients

A health product generating English discharge notes needs Hebrew versions it can rely on. The Clinical API translates clinical English into verified Hebrew with an audience of clinician or patient and a patient_gender option, keeps protected and redacted terms, and the verify operation checks a Hebrew translation against its English source with strict or standard verification.

Call POST /v1/medical/translate with text Take one tablet twice daily after meals and audience patient, then call POST /v1/medical/verify with the English source and the returned Hebrew translation

Bidirectional text rendering

A messaging app showing mixed Hebrew and English lines needs them to render in the right order. The wrap operation returns a display-ready line as html, isolate, or marks output with a base direction of auto, ltr, or rtl, and the detect operation identifies code-switched input before it is displayed.

Call POST /v1/wrap with a mixed Hebrew and English line, format html, and base auto, and return the wrapped output

Hebrew for speech and search

A voice assistant reading Hebrew aloud needs vowel points to pronounce words correctly, and a search index needs Latin spellings of Hebrew names. HebrewCore adds nikud to Hebrew text, strips it again for matching, and transliterates in either direction between Hebrew and Latin script.

Call POST /v1/nikud with a Hebrew sentence, then POST /v1/transliterate with the same text and direction he-to-latin

Key Endpoints

18 endpoints — the hebrewcore api translates text between hebrew, english, russian, and other languages and returns rtl and ltr metadata for both sides.

METHOD

PATH

DESCRIPTION

POST

/v1/translate

Translate text

POST

/v1/translate/batch

Translate a batch of strings

POST

/v1/detect

Detect language

POST

/v1/nikud

Add nikud

POST

/v1/transliterate

Transliterate Hebrew and Latin script

POST

/v1/wrap

Wrap a line for display

POST

/v1/medical/translate

Verified clinical translation

POST

/v1/terms

Upsert protected terms

POST

/v1/translate

Translate text

POST

/v1/translate/batch

Translate a batch of strings

POST

/v1/detect

Detect language

POST

/v1/nikud

Add nikud

POST

/v1/transliterate

Transliterate Hebrew and Latin script

POST

/v1/wrap

Wrap a line for display

POST

/v1/medical/translate

Verified clinical translation

POST

/v1/terms

Upsert protected terms

Why Jentic?

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

Setup

Wiring HebrewCore by hand means sending the bearer key, keeping hc_live_ and hc_test_ keys apart, and handling 429 rate_limited and quota_exceeded answers with their usage headers. Through Jentic you install once, import HebrewCore from the API Directory, store the key once, and your agent calls it.

Permission scoping

HebrewCore carries the text and options in the request body, so rules bound which operations your agent may call, such as translate and detect, not which text. You choose the operations it may call, so account changes like DELETE /v1/terms/{id} or the Clinical API are not included unless you add them.

Credential isolation

Your HebrewCore 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 'translate text into Hebrew' or 'add nikud', and Jentic returns the matching HebrewCore operation with its input schema, including the quality and protect options, so the agent calls the right endpoint.

FAQs

Specific to using HebrewCore API through Jentic.

What authentication does the HebrewCore API use?

Per its OpenAPI spec, every operation except GET /v1/health takes a bearer token: Authorization: Bearer with an hc_live_ key for production or an hc_test_ key for the sandbox. Through Jentic the key is stored by your own instance and attached at call time, so the agent never sees it.

What are the rate limits for the HebrewCore API?

The spec states 600 requests per minute per account across all its keys on every plan, answered with 429 rate_limited and Retry-After when exceeded. Monthly characters depend on your plan, and request size is capped at 20,000 characters, or 5,000 for transliterate and 10,000 for nikud. See https://hc.itsbaba.com/docs for details.

Can HebrewCore keep numbers and product names unchanged in a translation?

Yes. Set protect on POST /v1/translate and HebrewCore keeps prices, quantities, dates, codes, product names, and interface variables exactly as written. Pass protected_terms per request, or store them on the account with POST /v1/terms so every protected translation keeps them.

Is there a HebrewCore MCP server?

You don't need an MCP server to give your agent HebrewCore. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the translation and language operations it needs without loading another server's tool definitions into its context.

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

Yes. Write a rule that allows only POST /v1/translate and POST /v1/detect, for example, and the agent can translate and detect language but cannot change or delete your account's protected terms or spend the higher-cost Clinical API characters. Every call it makes is logged.

How do I translate text into Hebrew through Jentic?

Search Jentic for 'translate text into Hebrew', load the POST /v1/translate operation, and execute it with text and target_lang he, adding quality or protect as needed. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Itsbaba HebrewCore API

AI ReadinessAI-Aware (A-)74/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLLanguage Modelsbearer18 EndpointsREST

For Agents

Translate to and from Hebrew with protected numbers, dates, and terms, detect language, transliterate, add nikud, wrap bidirectional text for display, and run verified clinical translation.

Use for: Translate this product description into Hebrew, I need to translate a price list without changing the numbers, Detect whether a message is Hebrew, English, or both, Add nikud to a Hebrew sentence for text-to-speech

Not supported: Does not handle speech-to-text, document file conversion, or translation project management. Use for Hebrew-centred text translation and language processing only.

The HebrewCore API translates text between Hebrew, English, Russian, and other languages and returns RTL and LTR metadata for both sides. Protected translation keeps prices, quantities, dates, codes, product names, and interface variables exactly as written and verifies every sentence, with an account-level list of protected terms such as drug or brand names. Beyond translation it detects language in code-switched input, transliterates between Hebrew and Latin script, adds or strips nikud vowel points, and wraps mixed Hebrew and English lines for display. A Clinical API adds verified clinical English-to-Hebrew translation, streaming over Server-Sent Events or a WebSocket, Hebrew-to-English record queries, and translation verification.

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

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

53%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

69%

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

54%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

67%

OperationId Quality

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

93%

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

60%

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

98%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the HebrewCore API to your agent

Capabilities

Start building with HebrewCore API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Itsbaba HebrewCore API

Jentic AI Readiness Score

HebrewCore 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