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

# Runsensible API

API for legal practice management. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a new case, list legal cases. Covers 3 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create a new case
- List legal cases
- Upload a legal document
- Query and filter Runsensible API records by parameters
- Monitor Runsensible API operational status and events

## Use cases

### Developer Tools Operations

Use the Runsensible API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including create a new case, list legal cases, upload a legal document.

Example prompt: Call POST /cases to create a new case

### Automated cases Management

Automate cases operations by combining multiple Runsensible API endpoints. Agents can list legal cases and then upload a legal document in a single workflow.

Example prompt: Call GET /cases to list legal cases, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Runsensible 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 'create a new case', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/cases` | Create a new case |
| GET | `/cases` | List legal cases |
| POST | `/documents` | Upload a legal document |

## Key resources

- **cases** — Operations related to cases
- **documents** — Operations related to documents

## Why Jentic

- **Setup:** Wiring the Runsensible API by hand means passing your key in the Authorization header against api.runsensible.com and building your own request handling for case and document calls. Through Jentic you install once, import the Runsensible API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Runsensible takes case and document details in the request body, so scope the agent to the operations it needs, such as listing legal cases or creating a case. You pick that allowed set, so uploading documents stays out unless you include it.
- **Credential handling:** Your Runsensible 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 'create a new case' or 'list legal cases', and Jentic returns the matching Runsensible operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Runsensible API use?

The Runsensible 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 create a new case with the Runsensible API?

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

### What are the rate limits for the Runsensible 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 create a new case through Jentic?

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

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

The Runsensible API exposes 3 endpoints covering cases, documents operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which Runsensible operations your agent may call, so you can allow it to list legal cases with GET /cases while withholding case creation via POST /cases and document uploads via POST /documents. You pick that allowed set, so uploading a legal document stays out of reach unless you explicitly include it. Your Runsensible API key is held encrypted by your own instance and injected only when a permitted operation runs, so the agent never sees the raw credential.