canonical: https://jentic.com/apis/fusehealth.com/fusehealth

# Fusehealth FUSE Brand API (External)

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.

## For AI 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.

## Scope

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

## Capabilities

- 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
- Manage the product catalog and a product's pharmacy coverages
- Handle brand billing: plans, coupons, upgrades, and cancellations

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Orders** — Medication orders with fee breakdown, event timeline, lab-kit, and visit status
- **Programs** — Treatment programs with product sets, per-product pricing, and template sync
- **Customers** — Patient directory with order counts, revenue, and tags
- **Billing** — Brand subscription plans, coupons, upgrades, and cancellations

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 50 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 44 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 43 / 100
  - Security: 63 / 100
  - AI Discoverability: 69 / 100
- **View full report:** https://jentic.com/apis/fusehealth.com/fusehealth/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **DrChrono API** — EHR and practice-management platform covering patients, scheduling, and clinical records
- **athenahealth API** — Cloud practice-management and EHR platform for clinical and billing workflows
- **Stripe API** — Payment processing for cards, wallets, and subscriptions

## FAQ

### 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.