canonical: https://jentic.com/apis/rx.fuzehealth.com/rx-fuzehealth

# Rx Fuzehealth FuzeRx Pharmacy & Telehealth API

The FuzeRx API provides access to pharmacy and telehealth infrastructure including patient management, prescription handling, fill requests, transfers, insurance, copay requests, coverage requests, and prior authorizations. The API exposes 28 endpoints secured with apiKey authentication.

## For AI agents

Programmatically find a patient, create a patient. Covers 28 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for healthcare only.

## Capabilities

- Find a patient
- Create a patient
- Update a patient
- Get a patient
- Monitor FuzeRx Pharmacy & Telehealth API operational status and events

## Use cases

### Healthcare Operations

Use the FuzeRx Pharmacy & Telehealth API to perform healthcare operations programmatically. The API provides 28 endpoints covering core functionality including find a patient, create a patient, update a patient.

Example prompt: Call GET /patient to find a patient

### Automated Patients Management

Automate patients operations by combining multiple FuzeRx Pharmacy & Telehealth API endpoints. Agents can create a patient and then update a patient in a single workflow.

Example prompt: Call PUT /patient to create a patient, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call FuzeRx Pharmacy & Telehealth 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 apiKey tokens manually.

Example prompt: Search Jentic for 'find a patient', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/patient` | Find a patient |
| PUT | `/patient` | Create a patient |
| POST | `/patient/{patient_token}` | Update a patient |
| GET | `/patient/{patient_token}` | Get a patient |
| GET | `/patient/{patient_token}/prescriptions` | Get patient prescriptions |
| GET | `/patient/{patient_token}/patient_survey` | Get a patient survey |
| GET | `/prescription/{prescription_token}` | Get a prescription |
| GET | `/prescription/{prescription_token}/fill/{fill_number}/claims` | Get insurance claim details |

## Key resources

- **Patients** — Patient record management
- **Prescriptions** — Prescription retrieval and management
- **Fill Requests** — Medication fill request operations
- **Transfers** — Prescription transfer requests
- **Direct Transfers** — Direct prescription transfers between pharmacies

## 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:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 73 / 100
- **View full report:** https://jentic.com/apis/rx.fuzehealth.com/rx-fuzehealth/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 FuzeRx Pharmacy & Telehealth API by hand means managing its API key, attaching it to each call against rxapi.fuzehealth.com, and handling your own retries. Through Jentic you install once, import the FuzeRx Pharmacy & Telehealth API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** FuzeRx puts the patient token in the URL path (`/patient/{patient_token}/...`), so a rule can pin your agent to one patient: it can read that patient's record, prescriptions, and survey and nothing else. You choose the operations it may call, so updating patient data is not included unless you add it.
- **Credential handling:** Your FuzeRx Pharmacy & Telehealth API 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 'find a patient' or 'list a patient's prescriptions', and Jentic returns the matching FuzeRx Pharmacy & Telehealth API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Oystehr** — Alternative healthcare API
- **Athenahealth** — Alternative healthcare API

## FAQ

### What authentication does the FuzeRx Pharmacy & Telehealth API use?

The FuzeRx Pharmacy & Telehealth API uses an API key passed 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 find a patient with the FuzeRx Pharmacy & Telehealth API?

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

### What are the rate limits for the FuzeRx Pharmacy & Telehealth 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 find a patient through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'find a patient'. Jentic returns the matching FuzeRx Pharmacy & Telehealth API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the FuzeRx Pharmacy & Telehealth API have?

The FuzeRx Pharmacy & Telehealth API exposes 28 endpoints covering patients, prescriptions, fill requests operations.

### Can I limit what my agent is allowed to do with the FuzeRx Pharmacy & Telehealth API?

Yes. Jentic One is self-hosted, so your own rules decide which FuzeRx operations and credentials the agent may use. Because FuzeRx puts the patient token in the URL path (for example `/patient/{patient_token}/prescriptions`), you can pin the agent to a single patient and let it read only that patient's record, prescriptions, and survey. You also choose the operations it may call, so write actions like updating patient data (POST `/patient/{patient_token}`) are excluded unless you explicitly allow them.