Install Jentic One Beta

Connect the Tenovi Hardware Integration (HWI) API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tenovi Hardware Integration (HWI) 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%2Ftenovi.com%2Ftenovi" | 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%2Ftenovi.com%2Ftenovi" | 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 Tenovi Hardware Integration (HWI) API.

Activate (request) an HWI device

List HWI devices

Get a specific HWI device

Delete/deactivate an HWI device

Create a patient record

GET STARTED

Start building with Tenovi Hardware Integration (HWI) API

Explore with Jentic One

View OpenAPI Document

Automated Devices Management

Automate devices operations by combining multiple Tenovi Hardware Integration (HWI) API endpoints. Agents can list hwi devices and then get a specific hwi device in a single workflow.

Call GET /hwi/hwi-devices to list hwi devices, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tenovi Hardware Integration (HWI) 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 apiKey tokens manually.

Search Jentic for 'activate (request) an hwi device', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — the tenovi hardware integration (hwi) api allows third-party clients to interact with remote patient monitoring (rpm) devices, gateways, fulfillment workflows, supplies, and more.

METHOD

PATH

DESCRIPTION

POST

/hwi/hwi-devices

Activate (request) an HWI device

GET

/hwi/hwi-devices

List HWI devices

GET

/hwi/hwi-devices/{id}

Get a specific HWI device

DELETE

/hwi/hwi-devices/{id}

Delete/deactivate an HWI device

POST

/hwi/patients

Create a patient record

GET

/hwi/patients

List patient records

GET

/hwi/hwi-device-types

List available device types

POST

/hwi/webhooks

Create a webhook

POST

/hwi/hwi-devices

Activate (request) an HWI device

GET

/hwi/hwi-devices

List HWI devices

GET

/hwi/hwi-devices/{id}

Get a specific HWI device

DELETE

/hwi/hwi-devices/{id}

Delete/deactivate an HWI device

POST

/hwi/patients

Create a patient record

GET

/hwi/patients

List patient records

GET

/hwi/hwi-device-types

List available device types

POST

/hwi/webhooks

Create a webhook

Why Jentic?

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

Setup

Wiring the Tenovi Hardware Integration API by hand means learning its X-API-Key header auth against the api2.tenovi.com host and handling device, patient, and webhook calls yourself. Through Jentic you install once, import the Tenovi Hardware Integration (HWI) API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

This API puts the device id in the URL path (/hwi/hwi-devices/{id}), so a rule can pin your agent to one device: it can read that device and nothing else. You choose the operations it may call, so deleting a device is not included unless you add it.

Credential isolation

Your Tenovi 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 'register a hardware device' or 'list patients', and Jentic returns the matching Tenovi Hardware Integration API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Tenovi Hardware Integration (HWI) API through Jentic.

What authentication does the Tenovi Hardware Integration (HWI) API use?

The Tenovi Hardware Integration (HWI) API uses an API key passed in the `X-API-Key` header. 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 activate (request) an hwi device with the Tenovi Hardware Integration (HWI) API?

Yes. Use the POST /hwi/hwi-devices endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Tenovi Hardware Integration (HWI) 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 activate (request) an hwi device through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'activate (request) an hwi device'. Jentic returns the matching Tenovi Hardware Integration (HWI) API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Tenovi Hardware Integration (HWI) API have?

The Tenovi Hardware Integration (HWI) API exposes 9 endpoints covering devices, patients, webhooks operations.

Can I limit what my agent is allowed to do with the Tenovi Hardware Integration (HWI) API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. The device id sits in the URL path (/hwi/hwi-devices/{id}), so you can pin the agent to a single device and let it only read that one, for example allowing GET /hwi/hwi-devices/{id} while excluding everything else. You choose the operations it may call, so destructive calls like DELETE /hwi/hwi-devices/{id} or creating patient records are off limits unless you add them.

Tenovi Hardware Integration (HWI) API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyIOTDevice ManagementapiKey9 EndpointsREST

For Agents

Programmatically activate (request) an hwi device, list hwi devices. Covers 9 operations with apiKey authentication.

Use for: I need to activate (request) an hwi device, I want to hwi devices, Search for a specific hwi device, Find all delete/deactivate an hwi device

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

The Tenovi Hardware Integration (HWI) API allows third-party clients to interact with remote patient monitoring (RPM) devices, gateways, fulfillment workflows, supplies, and more. Clients can receive measurement data from Tenovi devices via webhooks, activate/deactivate devices, manage patients, and handle fulfillment workflows. The API exposes 9 endpoints secured with apiKey authentication.

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: BSignals: 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: C-Signals: 4

41%

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.

64%

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

50%

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

88%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Tenovi Hardware Integration (HWI) API to your agent

Capabilities

Start building with Tenovi Hardware Integration (HWI) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tenovi Hardware Integration (HWI) API

Jentic AI Readiness Score

Tenovi Hardware Integration (HWI) 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