Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 醫藥通 2.0 API Documentation, 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.johnnywork%2F20-api-documentation" | shStep 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.johnnywork%2F20-api-documentation" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with 醫藥通 2.0 API Documentation API.
取得指定專案的基本設定 [1-1]
取得指定專案的註冊與同意書欄位設定 [1-7]
取得指定專案的紀錄頁欄位設定 [1-8]
取得病患(自己)的贈藥紀錄 [8-1]
HCP贈藥紀錄頁 - 病人清單頁籤 [8-2-3]
GET STARTED
HCP取得病患的贈藥紀錄 [8-3]
取得上傳記錄 [11-1]
Patterns agents use 醫藥通 2.0 API Documentation API for, with concrete tasks.
★ Developer Tools Operations
Use the 醫藥通 2.0 API Documentation to perform developer tools operations programmatically. The API provides 13 endpoints covering core functionality including 取得指定專案的基本設定 [1-1], 取得指定專案的註冊與同意書欄位設定 [1-7], 取得指定專案的紀錄頁欄位設定 [1-8].
Call GET /config/project/{hash_id} to 取得指定專案的基本設定 [1-1]
Automated PAP 標準 Management
Automate pap 標準 operations by combining multiple 醫藥通 2.0 API Documentation endpoints. Agents can 取得指定專案的註冊與同意書欄位設定 [1-7] and then 取得指定專案的紀錄頁欄位設定 [1-8] in a single workflow.
Call GET /v1/projects/{hash_id}/form-configs to 取得指定專案的註冊與同意書欄位設定 [1-7], then verify the result
AI Agent Integration via Jentic
AI agents discover and call 醫藥通 2.0 API Documentation 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 bearer tokens manually.
Search Jentic for '取得指定專案的基本設定 [1-1]', load the operation schema, and execute with Jentic-managed credentials
13 endpoints — 醫藥通 2.
METHOD
PATH
DESCRIPTION
/config/project/{hash_id}
取得指定專案的基本設定 [1-1]
/v1/projects/{hash_id}/form-configs
取得指定專案的註冊與同意書欄位設定 [1-7]
/v1/projects/{hash_id}/record-configs
取得指定專案的紀錄頁欄位設定 [1-8]
/getPTMedicationRecord
取得病患(自己)的贈藥紀錄 [8-1]
/getHCPPatientList
HCP贈藥紀錄頁 - 病人清單頁籤 [8-2-3]
/hcpGetPTMedicationRecord
HCP取得病患的贈藥紀錄 [8-3]
/salesforce/upload-record
取得上傳記錄 [11-1]
/medicine/settings
儲存用藥提醒設定
/config/project/{hash_id}
取得指定專案的基本設定 [1-1]
/v1/projects/{hash_id}/form-configs
取得指定專案的註冊與同意書欄位設定 [1-7]
/v1/projects/{hash_id}/record-configs
取得指定專案的紀錄頁欄位設定 [1-8]
/getPTMedicationRecord
取得病患(自己)的贈藥紀錄 [8-1]
/getHCPPatientList
HCP贈藥紀錄頁 - 病人清單頁籤 [8-2-3]
/hcpGetPTMedicationRecord
HCP取得病患的贈藥紀錄 [8-3]
/salesforce/upload-record
取得上傳記錄 [11-1]
/medicine/settings
儲存用藥提醒設定
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the 醫藥通 2.0 API by hand means implementing its bearer token auth, pointing at the sandbox host, and writing your own retry handling around the project config, medication record, and appointment reminder calls. Through Jentic you install once, import the 醫藥通 2.0 API from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
This API puts the project id in the URL path (/config/project/{hash_id}, /v1/projects/{hash_id}/...), so a rule can pin your agent to one project and the operations around it. You choose the operations it may call, so writes like uploading a Salesforce record are not included unless you add them.
Credential isolation
Your 醫藥通 2.0 API 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 'get a project's form config' or 'fetch a patient medication record', and Jentic returns the matching 醫藥通 2.0 API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using 醫藥通 2.0 API Documentation API through Jentic.
What authentication does the 醫藥通 2.0 API Documentation use?
The 醫藥通 2.0 API Documentation uses a Bearer token in the Authorization 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 取得指定專案的基本設定 [1-1] with the 醫藥通 2.0 API Documentation?
Yes. Use the GET /config/project/{hash_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the 醫藥通 2.0 API Documentation?
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 取得指定專案的基本設定 [1-1] through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for '取得指定專案的基本設定 [1-1]'. Jentic returns the matching 醫藥通 2.0 API Documentation operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the 醫藥通 2.0 API Documentation have?
The 醫藥通 2.0 API Documentation exposes 13 endpoints covering pap 標準, 提醒小幫手 operations.
Can I limit what my agent is allowed to do with the 醫藥通 2.0 API?
Yes. Because you run Jentic One yourself, your own rules decide which 醫藥通 2.0 operations and which stored bearer token the agent may use. Since this API carries the project id in the URL path (/config/project/{hash_id}, /v1/projects/{hash_id}/...), a rule can pin the agent to a single project and only the read calls around it, such as GET /config/project/{hash_id} or GET /getPTMedicationRecord. You choose the operations it may call, so writes like POST /medicine/settings or /salesforce/upload-record stay off unless you add them.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically 取得指定專案的基本設定 [1-1], 取得指定專案的註冊與同意書欄位設定 [1-7]. Covers 13 operations with bearer authentication.
Use for: I need to 取得指定專案的基本設定 [1-1], I want to 取得指定專案的註冊與同意書欄位設定 [1-7], Search for 取得指定專案的紀錄頁欄位設定 [1-8], Find all 取得病患(自己)的贈藥紀錄 [8-1]
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
醫藥通 2.0 API Documentation. The API exposes 13 endpoints secured with bearer authentication.