Runsensible API

Name: Runsensible API API
Brand: Runsensible API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey3 EndpointsREST

For Agents

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

Use for: I need to a new case, I want to legal cases, Search for upload a legal document, List all records from Runsensible API

Connect the Runsensible API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Runsensible API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Runsensible API API.

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

GET STARTED

Start building with Runsensible API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Runsensible API API for, with concrete tasks.

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

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.

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.

Search Jentic for 'create a new case', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — api for legal practice management.

METHOD

PATH

DESCRIPTION

POST

/cases

Create a new case

GET

/cases

List legal cases

POST

/documents

Upload a legal document

POST

/cases

Create a new case

GET

/cases

List legal cases

POST

/documents

Upload a legal document

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Runsensible API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a new case') and Jentic returns the matching Runsensible API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Runsensible API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Runsensible API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.