Install Jentic One Beta

Connect the Nirvartech Patient API to your agent

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

Organise prescriptions and test reports into folders and upload PDF, JPEG, PNG, GIF, or HEIC files with type prescription or test_report

Search a patient's folders and files by a search_data term

Generate a temporary signed URL to share a folder or a single file with a care provider

GET STARTED

Start building with Nirvartech Patient API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Nirvartech Patient API for, with concrete tasks.

★ Health log assistant through Jentic

A personal health agent records home readings without the patient opening the app. It searches Jentic for 'store a blood pressure reading', receives the operation schema, and posts systolic and diastolic values, then reads the past-seven-days endpoint to report the trend. The spec limits each reading type to two submissions per 24-hour period, so the agent checks today's readings first.

Call GET /patient/blood-pressure/today, and if fewer than two readings exist call POST /patient/blood-pressure/store with systolic=125 and diastolic=82, then call GET /patient/blood-pressure/past-seven-days and summarise the trend

Sharing records before a doctor visit

Before an appointment, a patient can send the relevant prescriptions and test reports in one link. GET /patient/folders lists folders, GET /patient/files/{id} lists the files inside one, and GET /patient/folders/{folder}/share returns a temporary signed URL that gives outside access to that folder for a limited time.

Call GET /patient/folders, find the folder named 'Cardiology', then call GET /patient/folders/{folder}/share with its id and return the signed URL

Digitising paper prescriptions and reports

Patients often hold their records as photos and scans. POST /patient/file/upload accepts a multipart file with folder_id, file_name, and a type of prescription or test_report, and POST /patient/search finds files and folders later by a search term, so a patient's history stays in one organised place.

Call POST /patient/folder/create with name='Lab Results 2026', then POST /patient/file/upload with that folder_id, file_name='CBC March', type='test_report', and the scanned PDF

Key Endpoints

43 endpoints — the nirvartech patient api powers the patient side of the nirvartech health app: phone-number registration with otp verification, login, and profile details such as blood group, height, and weight.

METHOD

PATH

DESCRIPTION

POST

/patient/login

Patient login

GET

/patient/folders

List the patient's folders

POST

/patient/file/upload

Upload a file to a folder

GET

/patient/folders/{folder}/share

Generate a signed URL to share a folder

POST

/patient/blood-pressure/store

Store a blood pressure reading

GET

/patient/blood-pressure/past-seven-days

Get seven-day blood pressure averages

POST

/patient/diabetes/store

Store a blood sugar reading

POST

/patient/login

Patient login

GET

/patient/folders

List the patient's folders

POST

/patient/file/upload

Upload a file to a folder

GET

/patient/folders/{folder}/share

Generate a signed URL to share a folder

POST

/patient/blood-pressure/store

Store a blood pressure reading

GET

/patient/blood-pressure/past-seven-days

Get seven-day blood pressure averages

POST

/patient/diabetes/store

Store a blood sugar reading

Why Jentic?

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

Setup

Wiring Nirvartech by hand means running the phone-number OTP and login flow, keeping the Passport bearer token, and handling an API that reports errors inside 200 responses. Through Jentic you install once, import Nirvartech from the API Directory, store the token once, and your agent calls it.

Permission scoping

Several Nirvartech paths carry the folder or file id (/patient/files/{id}, /patient/folders/{folder}/share), so a rule can limit those calls to one folder, but deletes are also GET operations. You choose the operations it may call, so destructive or sharing ones like /patient/folder/delete/{id} or the share-link operations are not included unless you add them.

Credential isolation

The patient's Nirvartech bearer token 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 'store a blood pressure reading' or 'share a medical folder', and Jentic returns the matching Nirvartech operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Nirvartech Patient API through Jentic.

What authentication does the Nirvartech Patient API use?

Per its OpenAPI spec, the Nirvartech Patient API declares a bearer token in Passport format, sent in the Authorization header. The patient obtains it from POST /patient/login with their phone number and password. Signed share URLs served from /image/{fileId} and /file/{filename} carry their own temporary signature. Through Jentic, the token is stored encrypted by your own Jentic One instance and injected at call time.

Can I share medical records with a doctor using the Nirvartech Patient API?

Yes. GET /patient/folders/{folder}/share returns a temporary signed URL for a whole folder, and GET /patient/file/{fileId} returns one for a single file. Both links grant outside access for a limited time without sharing the patient's login.

What are the rate limits for the Nirvartech Patient API?

The OpenAPI spec does not specify a general request limit. It does limit POST /patient/blood-pressure/store and POST /patient/diabetes/store to two submissions per 24-hour period each. Check https://nirvartech.com for other limits.

How do I log a blood sugar reading with the Nirvartech Patient API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add Nirvartech from the Jentic API Directory, and store the patient's bearer token. Your agent searches for 'store a blood sugar reading' and calls POST /patient/diabetes/store with blood_sugar_level, then GET /patient/diabetes/today to confirm. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes, and here it matters which operations you name rather than which methods. Folder and file deletion use GET (/patient/folder/delete/{id} and /patient/file/delete/{id}), so a rule that allows the health-data reads and the two store operations, and nothing else, lets the agent log and review readings without being able to delete records or create share links.

Is there a Nirvartech MCP server?

You don't need an MCP server to give your agent the Nirvartech Patient API. Jentic connects it directly from the API Directory: import it, store the bearer token once, and your agent calls it.

What file types can I upload with the Nirvartech Patient API?

POST /patient/file/upload accepts PDF, JPEG, PNG, JPG, GIF, and HEIC files up to 111MB as multipart form data, with folder_id, file_name, and a type of prescription or test_report.

Nirvartech Patient API

AI ReadinessFoundational (D)45/100

See full scorecard

Community OpenAPI document · agent-readyHealthcareEhr Emrbearer43 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage a Nirvartech patient's medical record folders and files, share them through signed URLs, log blood pressure and blood sugar readings, and read daily, weekly, and monthly health averages.

Use for: I need to log today's blood pressure reading of 125 over 82, Get my blood sugar averages for the past seven days, Upload a new prescription to my Medications folder, Search for my latest blood test report

Not supported: Does not book appointments, issue prescriptions, or connect to hospital EHR systems. Use for a patient's own Nirvartech records, file sharing, and home blood pressure and blood sugar logs only.

The Nirvartech Patient API powers the patient side of the Nirvartech health app: phone-number registration with OTP verification, login, and profile details such as blood group, height, and weight. Patients organise prescriptions and test reports into folders, upload PDF or image files, search them, and generate temporary signed URLs to share a folder or file with a doctor. The API also records blood pressure and blood sugar readings and returns today's values plus seven-day, weekly, and monthly averages, along with patient notifications and a list of doctor specialities.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

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: B+Signals: 4

23%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

46%

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

39%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

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.

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

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Nirvartech Patient API to your agent

Capabilities

Start building with Nirvartech Patient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Nirvartech Patient API

Jentic AI Readiness Score

Nirvartech Patient 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