canonical: https://jentic.com/apis/slicebox.local/slicebox-local

# Slicebox API

Slicebox - safe sharing of medical images. The API exposes 118 endpoints.

## For AI agents

Programmatically access Slicebox API resources. Covers 118 operations.

## Scope

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

## Capabilities

- Access Slicebox API resources via REST API
- Manage healthcare data programmatically
- Integrate Slicebox API into automated workflows
- Query and filter Slicebox API records by parameters
- Monitor Slicebox API operational status and events

## Use cases

### Healthcare Operations

The API provides 118 endpoints for healthcare operations.

Example prompt: Execute a primary operation against the Slicebox API

### Data Retrieval and Monitoring

Query Slicebox API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Slicebox API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Slicebox 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 none tokens manually.

Example prompt: Search Jentic for 'slicebox API', load the operation schema, and execute with Jentic-managed credentials

## Key resources

- **General** — General routes applicable to multiple aspects of the slicebox API and to the slicebox system
- **Import** — Methods for handling structured importing of DICOM files into slicebox
- **Meta Data** — Methods for handling DICOM meta data (attributes)
- **Images** — Methods concerning images and datasets
- **Anonymization** — Methods concerning anonymization and de-anonymization of images and the associated anonymization dat

## Why Jentic

- **Setup:** Wiring the Slicebox API by hand means targeting its /api base path and shaping each request against a large surface of operations yourself. Through Jentic you install once, import Slicebox from the API Directory, and your agent calls it.
- **Permission scoping:** You choose which Slicebox operations the agent may call, so limit it to the operations it needs and nothing else. Any operations you do not include are not available to the agent unless you add them to the allowed set.
- **Credential handling:** Any access Slicebox requires is held once by your own Jentic One instance and applied at execution time rather than by the agent. Nothing sensitive enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent describing the Slicebox task they need, and Jentic returns the matching 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 Slicebox API use?

The Slicebox API uses no authentication. 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.

### What are the rate limits for the Slicebox 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 use slicebox API through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use slicebox API'. Jentic returns the matching Slicebox API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Slicebox API exposes 118 endpoints covering general, import, meta data operations.

### Does the Slicebox API support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

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

Yes. Because Jentic One is self-hosted, you decide which Slicebox operations your agent may call, so you can allow only the ones it needs, such as DICOM import or meta data lookups, while withholding image and anonymization endpoints it should not touch. Any operation you do not add to the allowed set stays unavailable to the agent. Your own instance holds any access the API requires and applies it at execution time, so the operator controls the scope rather than the agent.