canonical: https://jentic.com/apis/kintoolkit.com/kintoolkit

# KinToolkit Public Catalog and MCP HTTP API

The KinToolkit API looks up published US liquid medicine label references for educational use, not personalised prescriptions. A public discovery document lists the calculators, label references, manufacturer sources, and Markdown alternatives, and a JSON-RPC tool endpoint answers three tool calls: find_label_references, list_calculator_bottles, and get_label_directions. It needs no API key and accepts no patient details; results keep the age restrictions, directions, maximum, and source together so the full package label can be checked.

## For AI agents

Look up public US liquid medicine label references, list calculator-supported bottles, and read published label directions for an exact bottle and concentration, without sending patient details.

## Scope

Does not provide personalised dosing, prescriptions, drug interaction checks, or patient records. Use for educational lookup of published US liquid medicine label references only.

## Capabilities

- Read the public discovery document of calculators, label references, and manufacturer sources from `/api/catalog.json`
- Find label references for a public brand, ingredient, and bottle audience with the find_label_references tool
- List the exact bottles and concentrations the calculators support with list_calculator_bottles
- Return the published label directions, age restrictions, and maximum for an exact listed bottle with get_label_directions
- Link each answer back to its manufacturer source so the full package label can be verified

## Use cases

### AI agent label reference lookup through Jentic

A family health assistant needs to point a parent to the published label for a liquid medicine without giving personalised dosing. Through Jentic the agent finds the KinToolkit tool operation, sends only the public brand, ingredient, and bottle audience to find_label_references, and returns the matching reference with its manufacturer source. The agent never forwards names, measurements, or medical history, and it asks which bottle is meant when matches are ambiguous.

Example prompt: Call POST `/api/mcp` with a tools/call request for find_label_references using only the brand name and bottle audience, then return the reference title, url, and manufacturer source

### Published directions for an exact bottle

Once the exact bottle is known, list_calculator_bottles confirms it is calculator-supported and get_label_directions returns the published label band with its age restrictions, maximum, and source kept together. Store-brand entries are reference-only and are not treated as substitutes, and the API does not interpolate or convert concentrations.

Example prompt: Call list_calculator_bottles through POST `/api/mcp`, confirm the user's exact bottle and concentration are listed, then call get_label_directions for that bottle and show the directions with the source

### Discovery for health content sites

A health content site can read the public discovery document to list every KinToolkit calculator and label reference, with links to the calculator page, its Markdown alternative, and the manufacturer source. The document accepts no patient data or dosing inputs.

Example prompt: Call GET `/api/catalog.json` and return the title, url, and manufacturerSource for every entry in calculators

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/catalog.json` | Read the public calculator and label-reference catalog |
| POST | `/api/mcp` | Send one JSON-RPC tool call or protocol message |

## Key resources

- **Discovery catalog** — Read-only list of calculators, label references, manufacturer sources, and Markdown alternatives
- **Label tools** — JSON-RPC tool calls for find_label_references, list_calculator_bottles, and get_label_directions

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 84 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 50 / 100
- **View full report:** https://jentic.com/apis/kintoolkit.com/kintoolkit/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring KinToolkit by hand means building JSON-RPC envelopes, negotiating the protocol version headers, and respecting its per-IP firewall window. Through Jentic you install once, import KinToolkit from the API Directory, and your agent calls it with no credential to manage.
- **Permission scoping:** KinToolkit has one read-only discovery operation and one JSON-RPC operation, and the tool name travels in the request body. Limit the agent to the operations it needs, such as reading the discovery document: rules bound which operations your agent may call, not which tool inside the JSON-RPC call.
- **Credential handling:** KinToolkit needs no credential, so there is nothing to store, and calls run through your own Jentic One instance rather than from inside the agent's context.
- **Discovery method:** Agents search Jentic by intent such as 'find a medicine label reference' or 'list calculator bottles', and Jentic returns the matching KinToolkit operation with its input schema so the agent sends a well-formed request without browsing the reference docs.

## Related APIs

- **openFDA API** — Public FDA data on drug labels, adverse events, and recalls
- **National Library of Medicine API** — Public medical and drug reference data from the US National Library of Medicine

## FAQ

### What authentication does the KinToolkit API use?

None. Per its OpenAPI spec, both operations are public and need no API key or token, and no persistent protocol session is required. Never send patient names, exact measurements, or medical history in a request.

### Does the KinToolkit API give personalised dosing advice?

No. It returns educational references to published US liquid medicine labels. get_label_directions works only for an exact listed calculator bottle, concentration, and published label band, and the answer keeps the age restrictions, directions, maximum, and source together. Verify the full package label and ask a clinician when unsure.

### What are the rate limits for the KinToolkit API?

Per the OpenAPI spec, the hosting firewall limits `/api/mcp` to 120 HTTP requests per IP per 60-second fixed window in each region, counting every protocol message. Over the cap the firewall rejects requests; honor a valid Retry-After value when present, otherwise wait at least 60 seconds and back off with jitter.

### Is there a KinToolkit MCP server?

KinToolkit publishes its tools on a JSON-RPC endpoint at `/api/mcp`, and you don't need to install a separate server to give your agent access. Jentic connects the API directly from the API Directory: import it and your agent calls the label tools on demand without loading another server's tool definitions into its context.

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

Yes. For example, write a rule that allows only GET `/api/catalog.json`, so the agent can read the discovery document of calculators and label references but cannot send tool calls. Because the tool name travels in the request body, allowing POST `/api/mcp` allows every tool on that endpoint. Every call the agent makes through your instance is logged.

### How do I look up a label reference through Jentic?

Search Jentic for 'find a medicine label reference', load the KinToolkit tool-call operation, and send a tools/call request naming find_label_references with only the public brand, ingredient, and bottle audience. To run it on your own infrastructure, install Jentic One from its GitHub repo.