Install Jentic One Beta

Connect the FUSE Brand API (External) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FUSE Brand API (External), 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%2Ffusehealth.com%2Ffusehealth" | 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%2Ffusehealth.com%2Ffusehealth" | 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 FUSE Brand API (External) API.

List and inspect medication orders with their fee breakdown and event timeline

Read an order's lab-kit lifecycle status and telehealth visit status

Create and update treatment programs and their per-product patient pricing

Read the patient directory with order counts, revenue, and tags

GET STARTED

Start building with FUSE Brand API (External) API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use FUSE Brand API (External) API for, with concrete tasks.

★ Agent-Driven Order Monitoring

An AI agent connected through Jentic keeps a brand on top of fulfilment by reading orders, checking each one's lab-kit and telehealth visit status, and walking the order's event timeline, so staff see what needs attention without opening the admin UI. Because orders carry a full fee waterfall, the agent can also surface the revenue behind each order in the same read.

List orders awaiting a lab kit, check each one's lab status and visit status, and flag the ones stuck in processing

Treatment Program Management

A brand operator manages what it offers by creating programs, setting each program's product set and per-product patient pricing, and re-syncing programs derived from a source template, so the catalog stays current across the clinic. Programs expose activation and visibility status per product, so the operator can see exactly what a patient will be offered.

Create a program, set its product set with patient pricing, and confirm each product's activation status

Patient and Billing Overview

A reporting workflow reads the patient directory with order counts and revenue, then checks the clinic's subscription plan and billing basics, so a brand owner sees patient activity and account standing together. Because data is auto-scoped to one clinic, the workflow only ever sees the brand's own patients and billing.

Pull the patient directory with order counts and report the clinic's current subscription plan

Key Endpoints

220 endpoints — the fuse brand api exposes a telehealth clinic's admin surface so a single brand can run its own medication programs, orders, and patients from its own frontend.

METHOD

PATH

DESCRIPTION

GET

/api/v1/orders

List orders with fee breakdown

GET

/api/v1/orders/{id}

Get order detail with the fee waterfall

GET

/api/v1/orders/{id}/lab-status

Get an order's lab-kit lifecycle status

GET

/api/v1/orders/{id}/visit-status

Get an order's telehealth visit status

GET

/api/v1/customers

Read the patient directory

GET

/api/v1/programs

List the clinic's treatment programs

POST

/api/v1/programs

Create a treatment program

GET

/api/v1/me

Identify the key's clinic, name, and scopes

GET

/api/v1/orders

List orders with fee breakdown

GET

/api/v1/orders/{id}

Get order detail with the fee waterfall

GET

/api/v1/orders/{id}/lab-status

Get an order's lab-kit lifecycle status

GET

/api/v1/orders/{id}/visit-status

Get an order's telehealth visit status

GET

/api/v1/customers

Read the patient directory

GET

/api/v1/programs

List the clinic's treatment programs

POST

/api/v1/programs

Create a treatment program

GET

/api/v1/me

Identify the key's clinic, name, and scopes

Why Jentic?

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

Setup

Wiring the FUSE Brand API by hand means managing a clinic-scoped x-api-key for the external surface and a brand-admin JWT for key management, and respecting that data is auto-scoped to one clinic. Through Jentic you install once, import FUSE from the API Directory, store the key once, and your agent calls it.

Permission scoping

You choose which operations your agent may call, so you can allow reading orders and the patient directory while leaving destructive ones like deleting a program or cancelling billing out. Because a key is also clinic-scoped, the agent can only ever reach one clinic's data, and rules bound which operations it runs on top of that.

Credential isolation

Your FUSE 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 'check an order's lab status' or 'create a treatment program', and Jentic returns the matching FUSE operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using FUSE Brand API (External) API through Jentic.

Is there a FUSE Health MCP server?

You don't need an MCP server to give your agent the FUSE Brand API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can read orders, manage programs, and check patients straight away, with no extra server to run and no tool definitions sitting in the agent's context.

Can I limit what my agent is allowed to do with the FUSE Brand API?

Yes. Issue a clinic-scoped key with read-only scope and write a rule that allows only the operations the agent needs, such as reading orders and the patient directory, while leaving program edits and billing changes out. Every call the agent makes is logged, so you can see exactly what it touched.

What authentication does the FUSE Brand API use?

The external FUSE Brand API authenticates with a clinic-scoped API key sent in the x-api-key header per its OpenAPI spec. A separate brand-admin JWT, obtained from the sign-in operation and presented as a bearer token, is used only by the key-management endpoints. Through Jentic the key is stored encrypted by your own instance and added at call time, so it never appears in the agent's prompt or logs.

Can I track order status with the FUSE Brand API?

Yes. An order's detail includes its full fee waterfall, and dedicated operations return its chronological event timeline, its lab-kit lifecycle status, and its telehealth visit status. An agent can poll these to know exactly where each order stands.

What are the rate limits for the FUSE Brand API?

The OpenAPI spec does not state request rate limits for the FUSE Brand API. For current limits and fair-use guidance, check the provider documentation at https://api.fusehealth.com.

How do I check an order's status through Jentic?

Import the FUSE Brand API from the Jentic API Directory, then have your agent issue a request such as 'show the lab status for this order'. Jentic matches the intent to the lab-status operation and returns its input schema so the agent builds the correct request, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Fusehealth FUSE Brand API (External)

AI ReadinessFoundational (C-)50/100

See full scorecard

Official vendor OpenAPI document · agent-readyHealthcarePharmacyapiKey, bearer220 EndpointsREST

For Agents

Read and manage a clinic's medication orders, treatment programs, products, patients, and billing in FUSE. Authenticates with a clinic-scoped API key in the x-api-key header, with a brand-admin bearer JWT for key management.

Use for: List the clinic's recent orders with their fee breakdown, Get the lab-kit status for a specific order, Check the telehealth visit status on an order, Create a treatment program for the clinic

Not supported: Does not handle clinical charting, e-prescribing, or insurance claims. Use for a telehealth brand's orders, programs, patients, and billing admin only.

The FUSE Brand API exposes a telehealth clinic's admin surface so a single brand can run its own medication programs, orders, and patients from its own frontend. You list and inspect orders with their fee breakdown, lab-kit status, and telehealth visit status, manage treatment programs and their product pricing, and read a patient directory with order counts and tags. Billing, product catalog, page-builder, CRM, and SMS endpoints round out the brand surface, and every request is scoped to one clinic so its data never reaches another brand's.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

76%

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

Example Density

How richly the API is illustrated with examples.

80%

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

34%

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.

55%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

62%

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

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the FUSE Brand API (External) to your agent

Capabilities

Start building with FUSE Brand API (External) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Fusehealth FUSE Brand API (External)

Jentic AI Readiness Score

FUSE Brand API (External)

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