Install Jentic One Beta

Connect the IntelliLynx ICD-10 to your agent

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

Suggest treatment plan steps for a condition from its ICD-10 code

Pass free-text clinical notes alongside the code to give the suggestion more context

Return each plan item as a step with its own notes for display or review

Use Cases

Patterns agents use IntelliLynx ICD-10 API for, with concrete tasks.

★ AI agent drafting care plans through Jentic

A developer building a clinical documentation assistant wants their agent to draft a first-pass treatment outline once a diagnosis is coded. Through Jentic the agent searches for 'suggest a treatment plan for a diagnosis', loads the suggest_treatment operation with its input schema, and sends the ICD-10 code with any notes. The returned plan steps are shown to a clinician as a draft, not applied automatically.

GET STARTED

Start building with IntelliLynx ICD-10 API

Explore with Jentic One

View OpenAPI Document

Care plan templates in an EHR add-on

An electronic health record add-on offers clinicians a starting checklist when they enter a diagnosis code. The add-on calls the IntelliLynx ICD-10 suggestion endpoint with the code and renders the plan array as editable steps. Clinicians keep, edit, or discard each step before saving the plan to the chart.

Send POST /suggest-treatment with code set to J45.909 and render each step from the plan array as an editable checklist item

Coding education and review

Training tools for medical coders and students show what a typical treatment outline looks like for a code they have just assigned. The tool sends the code to the IntelliLynx ICD-10 API and displays the suggested plan steps next to the code. Learners compare the outline with the case notes they were given.

Call POST /suggest-treatment for code I10 and display the step and notes fields of each returned plan item beside the case

Key Endpoints

1 endpoints — the intellilynx icd-10 api suggests treatment plan steps for a diagnosed condition identified by its icd-10 code.

METHOD

PATH

DESCRIPTION

POST

/suggest-treatment

Suggest treatment plan steps for an ICD-10 code

POST

/suggest-treatment

Suggest treatment plan steps for an ICD-10 code

Why Jentic?

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

Setup

Wiring the IntelliLynx ICD-10 API by hand means writing a client for its single POST operation, passing the code as a query parameter, and parsing the plan array yourself. Through Jentic you install once, import it from the API Directory, and your agent calls it with no credential to manage.

Permission scoping

The spec exposes one operation, POST /suggest-treatment, with the ICD-10 code in the query string rather than the URL path, so rules bound which operations your agent may call, not which codes it sends. Allowing that one operation gives the agent exactly the suggestion call and no other route on the host.

Credential isolation

The IntelliLynx ICD-10 spec declares no credential, so there is nothing to store, and your own Jentic One instance still routes the call outside the agent's prompt, logs, and context.

Intent-based discovery

Agents search Jentic by intent such as 'suggest a treatment plan for a diagnosis' or 'treatment steps for an ICD-10 code', and Jentic returns the suggest_treatment operation with its input schema so the agent sends the code correctly.

FAQs

Specific to using IntelliLynx ICD-10 API through Jentic.

What authentication does the IntelliLynx ICD-10 API use?

The OpenAPI spec for the IntelliLynx ICD-10 API declares no security schemes, and the suggest-treatment operation is listed with no auth requirement. If the provider issues keys for production use, check with them directly, since the spec does not describe one.

Can I get treatment suggestions for a diagnosis code with the IntelliLynx ICD-10 API?

Yes. POST /suggest-treatment takes the ICD-10 code as the required code query parameter and an optional JSON body with a notes string. The response holds a plan array where each item has a step and notes. Treat the output as a draft for a clinician to review, since the spec makes no claim about clinical validation.

What are the rate limits for the IntelliLynx ICD-10 API?

The OpenAPI spec does not specify rate limits. Check the provider site at https://www.icd10api.com for current limits before sending a high volume of codes.

Is there an IntelliLynx ICD-10 MCP server?

You don't need an MCP server to give your agent the IntelliLynx ICD-10 API. Jentic connects it directly from the API Directory: import it and your agent calls the treatment suggestion operation when it needs it, discovered on demand without loading extra tool definitions into its context.

Can I limit what my agent is allowed to do with the IntelliLynx ICD-10 API?

Yes. Write a rule that allows only POST /suggest-treatment, the single operation in this spec, and the agent can request plan suggestions and nothing else through this binding. Every call it makes is logged, so you can review which codes it sent.

How do I request a treatment plan through Jentic?

Search Jentic for 'suggest a treatment plan for a diagnosis', load the suggest_treatment operation, and execute it with the code query parameter and an optional notes body. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Icd10api IntelliLynx ICD-10

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Community OpenAPI document · agent-readyHealthcareClinical Datanone1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Send an ICD-10 code, with optional clinical notes, and get back a list of suggested treatment plan steps for that condition.

Use for: Suggest a treatment plan for ICD-10 code E11.9, I want treatment steps for a diagnosed condition, Get the suggested plan for a code and these clinical notes, Retrieve treatment suggestions to draft a care plan for clinician review

Not supported: Does not look up or validate ICD-10 code descriptions, store patient records, or prescribe medication. Use for suggesting treatment plan steps from a known ICD-10 code only.

The IntelliLynx ICD-10 API suggests treatment plan steps for a diagnosed condition identified by its ICD-10 code. A single POST call takes the code as a query parameter and optional free-text notes in the body, and returns a plan array where each item carries a step and its notes. It is a narrow, single-purpose service meant to sit beside a clinical record system rather than replace one.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

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

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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

13%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the IntelliLynx ICD-10 to your agent

Capabilities

Use Cases

Start building with IntelliLynx ICD-10 API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Icd10api IntelliLynx ICD-10

Jentic AI Readiness Score

IntelliLynx ICD-10

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