Sensible So Sensible API

Name: Sensible API
Brand: Sensible API
Availability: InStock

✓ Official Vendor SpecMarketingEmail Marketingbearer11 EndpointsREST

For Agents

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

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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 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

GET STARTED

Start building with Sensible API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Sensible API for, with concrete tasks.

★ Marketing Operations

Use the Sensible API to perform marketing operations programmatically. The API provides 11 endpoints covering core functionality including extract data from a document (sync), extract with specified config, extract document at sensible url (async).

Call POST /extract/{document_type} to extract data from a document (sync)

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

Why Jentic?

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

Credential isolation

Sensible API bearer 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., 'extract data from a document (sync)') and Jentic returns the matching Sensible API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

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

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

Sensible So Sensible API

Connect the Sensible API to your agent

Capabilities

Start building with Sensible API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs