Fincura
Fincura (now part of Abrigo) provides automated financial statement spreading and credit analysis for banks, credit unions, and other lenders. Its Automated Spreading and Analysis API ingests borrower financial documents (PDF, Excel, and images), spreads them into normalized data views, and runs debt-service-coverage-ratio (DSCR) and global cashflow analyses. The REST API (v1) covers borrowers, loans, portfolios, document files, data views, spreading/DSCR/global-cashflow templates, financial requirements, custom attributes, embeddable workflow UIs, and HMAC-signed webhooks. Authentication is a bearer JWT API key issued per Fincura user account. Originally a Techstars-backed startup, Fincura was acquired by Abrigo.
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 Fincura the way a machine reads it — 27 machine-readable artifacts across 20 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 — Fincura scores 36.4/100 (thin), with a separate agent-readiness read of 71/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.
How we profile Fincura
Each block below is one kind of artifact we hold for Fincura. 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 20
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.
Fincura Api-Key API
The Api-Key API from Fincura — 1 operation(s) for api-key.
Fincura Borrowers API
A record in our system to link financials and analyses to.
Fincura CustomAttributes API
The CustomAttributes API from Fincura — 2 operation(s) for customattributes.
Fincura DataViews API
The DataViews API from Fincura — 7 operation(s) for dataviews.
Fincura DscrAnalysis API
The DscrAnalysis API from Fincura — 4 operation(s) for dscranalysis.
Fincura DscrTemplate API
DSCR Templates
Fincura EmbeddedDocument API
Embedded Document Workflows enable a 3rd party user to use the Fincura UI to complete a portion of our document parsing pipeline and then return to the 3rd parties website.
Fincura EmbeddedDscrAnalysis API
Embedded DSCR Analysis allows an API user to authenticate and embedded previously created DSCR analysis into a 3rd party workflow.
Fincura EmbeddedFinancials API
Embedded Financials allows an API user to authenticate and embedded borrower financials into a 3rd party workflow.
Fincura EmbeddedGlobalCashflowAnalysis API
Embedded Global Cashflow Analysis allows an API user to authenticate and embed previously created Global Cashflow analyses into a 3rd party applications.
Fincura Files API
Files serve as the source input data for our insights engine. They are represented by a `DocumentFile` record.
Fincura FinancialStatementSubmission API
The FinancialStatementSubmission API from Fincura — 1 operation(s) for financialstatementsubmission.
Fincura GlobalCashflowAnalysis API
The GlobalCashflowAnalysis API from Fincura — 5 operation(s) for globalcashflowanalysis.
Fincura GlobalCashflowTemplate API
The GlobalCashflowTemplate API from Fincura — 1 operation(s) for globalcashflowtemplate.
Fincura Loans API
A Borrower loan record in our system.
Fincura Portfolios API
Portfolios allow for grouping Borrowers.
Fincura Requirements API
Set rules/covenants for your borrowers
Fincura SpreadingTemplate API
Spreading Templates
Fincura TenantSettings API
The TenantSettings API from Fincura — 1 operation(s) for tenantsettings.
Fincura Webhooks API
## Supported Events The following are events you can listen to via webhooks. | Event Type | Description | | ----------------------------------...
Scroll within the panel for all 20 ·
Arazzo Workflows 2
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.
_Index
ARAZZOSpread a borrower financial statement and run DSCR analysis
Creates a borrower, uploads a financial document for automated spreading, retrieves the normalized data view, then runs a DSCR analysis and downloads it.
ARAZZOMCP 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.
fincura-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.
Fincura Webhooks
ASYNCAPISecurity Posture 2
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 Fincura — 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 1
Portal, sign-up, and the first successful call
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/fincura · machine-readable index on apis.io