Install Jentic One Beta

Connect the Docman SCI Gateway API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Docman SCI Gateway 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%2Fswaggerhub.advancedcomputersoft%2Fdocman-sci-gateway-api" | 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%2Fswaggerhub.advancedcomputersoft%2Fdocman-sci-gateway-api" | 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 Docman SCI Gateway API.

Get Patients

Add a Document Reference

Update notes for a Document Reference

Query and filter Docman SCI Gateway API records by parameters

GET STARTED

Start building with Docman SCI Gateway API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Docman SCI Gateway API for, with concrete tasks.

★ Developer Tools Operations

Use the Docman SCI Gateway API to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including get patients, get patient, add a document reference.

Call GET /{tenantId}/Patient to get patients

Automated DocumentReference Management

Automate documentreference operations by combining multiple Docman SCI Gateway API endpoints. Agents can get patient and then add a document reference in a single workflow.

Call GET /{tenantId}/Patient/{patientId} to get patient, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Docman SCI Gateway 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 oauth2 tokens manually.

Search Jentic for 'get patients', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — integration between sci gateway and dm10.

METHOD

PATH

DESCRIPTION

GET

/{tenantId}/Patient

Get Patients

GET

/{tenantId}/Patient/{patientId}

Get Patient

POST

/{tenantId}/DocumentReference

Add a Document Reference

GET

/{tenantId}/DocumentReference

Get Document References

GET

/{tenantId}/DocumentReference/{documentId}

Get Document Reference

PATCH

/{tenantId}/DocumentReference/{documentId}

Update notes for a Document Reference

POST

/{tenantId}

Get Many Responses for SCI Gateway

GET

/{tenantId}/ValueSet/national-folder-structure

Get Folder Structure

GET

/{tenantId}/Patient

Get Patients

GET

/{tenantId}/Patient/{patientId}

Get Patient

POST

/{tenantId}/DocumentReference

Add a Document Reference

GET

/{tenantId}/DocumentReference

Get Document References

GET

/{tenantId}/DocumentReference/{documentId}

Get Document Reference

Why Jentic?

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

Setup

Wiring the Docman SCI Gateway API by hand means setting up its OAuth2 flow, choosing among its SwaggerHub host variants, and threading the tenant id through each patient and document call yourself. Through Jentic you install once, import the Docman SCI Gateway API from the API Directory, store the OAuth credentials once, and your agent calls it.

Permission scoping

The SCI Gateway API puts the tenant id in the URL path (/{tenantId}/...), so a rule can pin your agent to one tenant for its patient and document-reference operations. You choose the operations it may call, so writes like patching a document reference are not included unless you add them.

Credential isolation

Your Docman SCI Gateway OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find patients for a tenant' or 'create a document reference', and Jentic returns the matching Docman SCI Gateway operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Docman SCI Gateway API through Jentic.

What authentication does the Docman SCI Gateway API use?

The Docman SCI Gateway API uses OAuth 2.0 for authorization. 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 get patients with the Docman SCI Gateway API?

Yes. Use the GET /{tenantId}/Patient endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Docman SCI Gateway 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 get patients through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get patients'. Jentic returns the matching Docman SCI Gateway API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Docman SCI Gateway API have?

The Docman SCI Gateway API exposes 8 endpoints covering documentreference, folder, patient operations.

Can I limit what my agent is allowed to do with the Docman SCI Gateway API?

Yes. Jentic One is self-hosted, so your own rules decide which Docman SCI Gateway operations and credentials the agent may use. Because the tenant id lives in the URL path (/{tenantId}/...), you can pin the agent to a single tenant for its patient and document-reference calls, and you choose exactly which operations it may run. That means read-only work like GET /{tenantId}/Patient can be allowed while writes such as POST /{tenantId}/DocumentReference or PATCH /{tenantId}/DocumentReference/{documentId} stay off unless you add them.

Advancedcomputersoft Docman SCI Gateway API

Name: Docman SCI Gateway API
Brand: Docman SCI Gateway API
Availability: InStock

Browse all Swaggerhub Advancedcomputersoft APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource Controloauth28 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically get patients, get patient. Covers 8 operations with oauth2 authentication.

Use for: I need to patients, I want to patient, Search for add a document reference, Find all document references

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Integration between SCI Gateway and DM10. The API exposes 8 endpoints secured with oauth2 authentication.

Jentic One on Github View OpenAPI Document