Kensho
Kensho Technologies is the AI innovation hub of S&P Global, building machine learning and AI systems that structure, connect, and extract meaning from the world's financial and business data. Kensho's developer platform exposes a suite of production APIs: Scribe for speech-to-text transcription of audio and video, Extract for turning PDF documents into structured JSON, NERD for named-entity recognition and disambiguation against Wikimedia and S&P Capital IQ knowledge bases, and the LLM-ready API (kfinance) that connects LLMs, agents, and AI applications to S&P Global's trusted data through Adaptive Retrieval and a hosted, OAuth-secured Model Context Protocol (MCP) server. Authentication is bearer-token based, issued from Kensho's services platform via personal tokens or production key pairs, with OAuth 2.0 (authorization code, client credentials, and refresh token flows, PKCE, and dynamic client registration) for the MCP surface.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Kensho the way a machine reads it — 11 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 — Kensho scores 41.6/100 (thin), with a separate agent-readiness read of 46/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Kensho
Each block below is one kind of artifact we hold for Kensho. 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 4
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.
Kensho Scribe
Asynchronous speech-to-text transcription API that turns audio and video into text with high accuracy. Supports batch, real-time, and human-in-the-loop transcription, multipart ...
Kensho Extract
Document intelligence API that transforms PDF documents into structured JSON, with hierarchical extraction, optical character recognition (OCR), enhanced table extraction, and b...
Kensho NERD
Named Entity Recognition and Disambiguation API that identifies and links concepts in text to knowledge bases (Wikimedia for general entities, S&P Capital IQ for financial organ...
Kensho LLM-ready API (kfinance)
LLM-ready API that connects LLMs, agents, and AI applications to S&P Global's trusted data through flexible retrieval, Adaptive Retrieval data agents, a Python library (kensho-k...
MCP Servers 2
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.
mcp
MCP SERVERkensho-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Kensho Scribe Webhooks
ASYNCAPISecurity Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Kensho — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/kensho · machine-readable index on apis.io