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

# Truepill FuzeRx API

FuzeRx (formerly Truepill) provides pharmacy fulfillment APIs for patient management, prescriptions, transfers, and webhook events. The API exposes 12 endpoints secured with apiKey authentication.

## For AI agents

Programmatically find a patient by demographics, create a patient. Covers 12 operations with apiKey authentication.

## Scope

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

## Capabilities

- Find a patient by demographics
- Create a patient
- Update a patient
- Get a patient
- Monitor FuzeRx API operational status and events

## Use cases

### Healthcare Operations

Use the FuzeRx API to perform healthcare operations programmatically. The API provides 12 endpoints covering core functionality including find a patient by demographics, create a patient, update a patient.

Example prompt: Call GET /v1/patient to find a patient by demographics

### Automated Patients Management

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

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

### AI Agent Integration via Jentic

AI agents discover and call FuzeRx 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 by demographics', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/patient | Find a patient by demographics |
| PUT | /v1/patient | Create a patient |
| POST | /v1/patient/{patient_token} | Update a patient |
| GET | /v1/patient/{patient_token} | Get a patient |
| GET | /v1/patient/{patient_token}/prescriptions | Get patient prescriptions |
| GET | /v1/prescription/{prescription_token} | Get a prescription |
| POST | /v1/transfer_request | Create a transfer request |
| GET | /v1/transfer_request | List transfer requests |

## Key resources

- **Patients** — Operations related to Patients
- **Prescriptions** — Operations related to Prescriptions
- **Transfers** — Operations related to Transfers
- **Webhooks** — Operations related to Webhooks

## Why Jentic

- **Setup:** Wiring FuzeRx API by hand means setting its Authorization API key header, tracking patient and prescription tokens across calls, and handling errors and retries yourself. Through Jentic you install once, import FuzeRx API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** FuzeRx API puts the patient token in the URL path (/v1/patient/{patient_token}/...), so a rule can pin your agent to one patient: it can read that patient's record and prescriptions and nothing else. You choose the operations it may call, so updating a patient or opening a transfer request are not included unless you add them.
- **Credential handling:** Your FuzeRx 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 by demographics' or 'list a patient's prescriptions', and Jentic returns the matching FuzeRx 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 API use?

The FuzeRx 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 by demographics with the FuzeRx API?

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

### What are the rate limits for the FuzeRx 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 by demographics 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 by demographics'. Jentic returns the matching FuzeRx API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the FuzeRx API have?

The FuzeRx API exposes 12 endpoints covering patients, prescriptions, transfers operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which FuzeRx API operations and credentials the agent may use. The patient token sits in the URL path (/v1/patient/{patient_token}/...), so you can pin the agent to a single patient and let it only read that patient's record and prescriptions. You also choose the operations it may call, so actions like updating a patient or opening a transfer request stay off limits unless you add them.