Sensible
Sensible is a document-automation API platform that extracts structured data from PDFs, images, spreadsheets, and emails using a hybrid of deterministic layout-based methods and LLM-based query methods. SenseML, Sensible's config language, lets engineers declare what to pull and where. The platform ships with 150+ open-source pre-built configurations across financial services, insurance, logistics, real estate, and healthcare. Sensible exposes sync and async extraction, classification, portfolio segmentation, CSV/Excel export, human review, coverage statistics, configuration versioning, and webhook delivery, all behind a bearer-auth REST surface plus a Postman collection, an MCP server, and Python / JavaScript SDKs.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Sensible the way a machine reads it — 79 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Sensible scores 62.1/100 (strong), with a separate agent-readiness read of 26/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Sensible's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/sensible-so/"
title="Sensible on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/sensible-so.svg"
alt="Sensible Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/sensible-so/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/sensible-so/"
title="Sensible on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/sensible-so/card.svg"
alt="Sensible Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Sensible
Each block below is one kind of artifact we hold for Sensible. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
sensible-so Configuration API
The Configuration API from sensible-so — 4 operation(s) for configuration.
sensible-so Document API
Classify documents by type
sensible-so Document type API
The Document type API from sensible-so — 2 operation(s) for document type.
sensible-so Get Excel from documents API
Convert extracted document data to spreadsheet
sensible-so Portfolio API
Extract data from multiple documents bundled into single PDF files
sensible-so Reference document API
The Reference document API from sensible-so — 4 operation(s) for reference document.
sensible-so Retrieve extractions API
Retrieve data extracted asynchronously from documents
Scroll within the panel for all 7 ·
Postman Collections 4
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 12
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONSensible Classification API
OPEN COLLECTIONSensible Document Types and Configurations API
OPEN COLLECTIONSensible Extractions API
OPEN COLLECTIONSensible Reference Documents API
OPEN COLLECTIONSensible Classification Configuration API
OPEN COLLECTIONSensible Classification Configuration Document API
OPEN COLLECTIONSensible Classification Configuration Document type API
OPEN COLLECTIONSensible Classification Configuration Portfolio API
OPEN COLLECTIONSensible Classification Configuration Reference document API
OPEN COLLECTIONScroll within the panel for all 12 ·
Arazzo Workflows 15
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Sensible Classify Then Extract
Classify a document to discover its best-fit document type, then submit an asynchronous extraction against that type.
ARAZZOSensible Config Versions Then Get By Version
List the version history of a configuration, then fetch one specific version of that configuration in full.
ARAZZOSensible Create Document Type And Configuration
Create a new document type and then add a SenseML configuration to it in one pass.
ARAZZOSensible Create Reference Document And List
Register a reference document in a document type, then list the type's reference documents to confirm registration.
ARAZZOSensible Extract From URL And Poll
Kick off an asynchronous extraction from a document URL with a chosen config, poll until it completes, then read the parsed results.
ARAZZOSensible Extract From URL Poll Then CSV
Asynchronously extract a document from a URL, poll until complete, then export the extraction as a CSV file.
ARAZZOSensible Extract Reference Text Then List
Pull all standardized text from a reference document, then list the document type's reference documents.
ARAZZOSensible Get Document Type Then List Configurations
Fetch a document type by id and then enumerate the configurations defined inside it.
ARAZZOSensible List Configurations Then Get
List the configurations in a document type, then fetch the full stringified JSON of one named configuration.
ARAZZOSensible List Document Types Then Extract
Confirm a document type exists in the account before submitting an asynchronous extraction against it.
ARAZZOSensible List Extractions Then Retrieve
List recent extractions with filters, then retrieve the full result of the most recent matching extraction.
ARAZZOSensible Portfolio Extract From URL And Poll
Segment and extract a multi-document portfolio at a URL, then poll until every sub-document extraction completes.
ARAZZOSensible Portfolio Upload URL And Poll
Generate a Sensible-signed upload URL for a multi-document portfolio, then poll the portfolio extraction to completion.
ARAZZOSensible Sync Extract Then Spreadsheet
Synchronously extract a document, then convert that extraction to a downloadable Excel spreadsheet.
ARAZZOSensible Upload URL Extract And Poll
Generate a Sensible-signed upload URL for a document type, then poll the extraction id until results are ready.
ARAZZOScroll within the panel for all 15 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Sensible MCP Endpoint
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Sensible So Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Sensible So Finops
FINOPSFeatures 22
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 22 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Sensible So Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Sensible API Rules
SPECTRALSensible API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
SensibleDocumentType
JSON SCHEMASensibleExtraction
JSON SCHEMAExamples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Sensible — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 17
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 17 ·
Build 8
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 8 ·
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sensible-so · machine-readable index on apis.io
This is an independent, third-party profile of Sensible, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.