Kita
Kita is an AI-native loan origination and underwriting company (Y Combinator W26, San Francisco) building document intelligence and credit decisioning for lenders in emerging and undertapped markets. Kita ships two developer-facing APIs. Kita Capture is a document-intelligence API that turns scanned or photographed bank statements, payslips, government IDs, credit reports, tax filings and 30+ other document types into structured, validated, fraud-checked JSON, with cross-document verification, batch processing, custom extraction schemas and HMAC-signed webhooks. Kita Underwriter is a credit-file API that creates loan applications, ingests borrower documents, computes a deterministic credit picture (adjusted EBITDA, DSCR, margins, debt-to-worth, sensitivity and a policy-engine decision produced by a versioned calculation engine rather than an LLM) and synthesizes a cited credit memo. The platform is region-pinned across Singapore and Mexico deployments and is used by microfinance institutions, SME lenders, CDFIs and community banks across Southeast Asia, Latin America and the United States.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Kita the way a machine reads it — 23 machine-readable artifacts across 14 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 — Kita scores 67.1/100 (strong), with a separate agent-readiness read of 97/100 (agent native). 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 Kita
Each block below is one kind of artifact we hold for Kita. 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 14
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.
Kita Applications API
Loan application records.
Kita Batch API
Process up to 100 documents from URLs in one request.
Kita Conversation API
Borrower message thread.
Kita Credit API
Deterministic credit picture — spread, adjustments, policy decision.
Kita Documents API
Borrower document upload and extraction.
Kita Exports API
PDF and XLSX exports.
Kita Folders API
Group documents into containers.
Kita Memo API
Cited credit memo synthesis and retrieval.
Kita Processing API
Submit documents for extraction.
Kita Results API
Retrieve extraction results, summaries and exports.
Kita Schemas API
Custom extraction schemas.
Kita Transcripts API
Plain-text document transcripts.
Kita Verification API
Cross-document verification checks.
Kita Webhooks API
Register and manage HMAC-signed outbound webhooks.
Scroll within the panel for all 14 ·
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.
kita-mcp.yml
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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Kita Plans
PLANSRate 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.
Kita Rate Limits
RATE LIMITSEvent 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.
Kita Capture Webhooks
ASYNCAPISecurity 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 Kita — 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 6
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/kita · machine-readable index on apis.io