Install Jentic One Beta

Connect the Sensible API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sensible 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsensible.so%2Fsensible-so" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsensible.so%2Fsensible-so" | 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 Sensible API.

Extract data from a document (sync)

Retrieve extraction by ID

Integrate Sensible API into automated workflows

Query and filter Sensible API records by parameters

Monitor Sensible API operational status and events

GET STARTED

Start building with Sensible API

Explore with Jentic One

View OpenAPI Document

Automated Export Management

Automate export operations by combining multiple Sensible API endpoints. Agents can extract with specified config and then extract document at sensible url (async) in a single workflow.

Call POST /extract/{document_type}/{config_name} to extract with specified config, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'extract data from a document (sync)', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

11 endpoints — sensible is an intelligent document processing platform.

METHOD

PATH

DESCRIPTION

POST

/extract/{document_type}

Extract data from a document (sync)

POST

/extract/{document_type}/{config_name}

Extract with specified config

POST

/generate_upload_url/{document_type}

Extract document at Sensible URL (async)

POST

/extract_from_url/{document_type}

Extract document at your URL (async)

POST

/generate_upload_url

Extract portfolio at Sensible URL

POST

/extract_from_url

Extract portfolio at your URL

GET

/documents/{id}

Retrieve extraction by ID

GET

/documents

List extractions

POST

/extract/{document_type}

Extract data from a document (sync)

POST

/extract/{document_type}/{config_name}

Extract with specified config

POST

/generate_upload_url/{document_type}

Extract document at Sensible URL (async)

POST

/extract_from_url/{document_type}

Extract document at your URL (async)

POST

/generate_upload_url

Extract portfolio at Sensible URL

POST

/extract_from_url

Extract portfolio at your URL

GET

/documents/{id}

Retrieve extraction by ID

GET

/documents

List extractions

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Sensible by hand means obtaining a bearer token and carrying the document type through the URL path on every extraction call yourself. Through Jentic you install once, import Sensible from the API Directory, store the token once, and your agent calls it.

Permission scoping

Sensible puts the document type and id in the URL path (/extract/{document_type}, /documents/{id}), so a rule can pin your agent to one document type: it can extract and read documents of that type and nothing else. You choose the operations it may call, so it holds only the ones you grant.

Credential isolation

Your Sensible token 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.

Intent-based discovery

Agents search Jentic by intent such as 'extract data from a document' or 'get a processed document', and Jentic returns the matching Sensible operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Sensible API through Jentic.

What authentication does the Sensible API use?

The Sensible API uses a Bearer token 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 extract data from a document (sync) with the Sensible API?

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

What are the rate limits for the Sensible 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 extract data from a document (sync) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'extract data from a document (sync)'. Jentic returns the matching Sensible API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Sensible API have?

The Sensible API exposes 11 endpoints covering export, extraction, portfolio operations.

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

Yes. Because Sensible puts the document type and id in the URL path (POST /extract/{document_type}, GET /documents/{id}), a rule in your self-hosted Jentic One instance can pin your agent to a single document type so it only extracts and reads documents of that kind. You decide which operations the agent may call, so it might hold extraction rights while you withhold portfolio or async URL operations. Your own rules govern which Sensible operations and which stored credentials the agent is permitted to use.

Sensible So Sensible API

Name: Sensible API
Brand: Sensible API
Availability: InStock

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail Marketingbearer11 EndpointsREST

For Agents

Programmatically extract data from a document (sync), extract with specified config. Covers 11 operations with bearer authentication.

Use for: I need to extract data from a document (sync), I want to extract with specified config, Search for extract document at sensible url (async), Find all extract document at your url (async)

Not supported: Does not handle payments, communications, or crm - use for marketing only.

Sensible is an intelligent document processing platform. The API provides document extraction, classification, and portfolio segmentation capabilities. The API exposes 11 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

38%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Sensible API to your agent

Capabilities

Start building with Sensible API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sensible So Sensible API

Jentic AI Readiness Score

Sensible API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness