Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Kanmon website screenshot

Kanmon

Kanmon is an embedded-lending platform that lets vertical SaaS and business-management software offer working capital to their customers without becoming a lender themselves. Through the Kanmon Public V2 REST API and the embeddable Kanmon Connect UI, platforms can originate term loans, lines of credit, invoice financing, Accounts Payable financing, and integrated merchant cash advances. Kanmon is the licensed lender and owns underwriting, compliance, and credit risk, while partners integrate financing directly into their existing product with API keys, official SDKs, prebuilt borrower UI components, and outbound webhooks.

agent native

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Kanmon the way a machine reads it — 19 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 — Kanmon scores 45.2/100 (developing), 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.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 45.2/100 · developing
Contract Quality 15.3 / 25
Developer Ergonomics 13.9 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 1.7 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 71/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Kanmon

Each block below is one kind of artifact we hold for Kanmon. 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.

Kanmon Bank Accounts API

The Bank Accounts API from Kanmon — 2 operation(s) for bank accounts.

Kanmon Businesses API

The Businesses API from Kanmon — 3 operation(s) for businesses.

Kanmon Connect Tokens API

The Connect Tokens API from Kanmon — 1 operation(s) for connect tokens.

Kanmon Documents API

The Documents API from Kanmon — 1 operation(s) for documents.

Kanmon Draw Requests API

The Draw Requests API from Kanmon — 2 operation(s) for draw requests.

Kanmon Embedded Sessions API

The Embedded Sessions API from Kanmon — 1 operation(s) for embedded sessions.

Kanmon Integrated MCA API

The Integrated MCA API from Kanmon — 2 operation(s) for integrated mca.

Kanmon Invoices API

The Invoices API from Kanmon — 3 operation(s) for invoices.

Kanmon Issued Products API

The Issued Products API from Kanmon — 2 operation(s) for issued products.

Kanmon Offers API

The Offers API from Kanmon — 2 operation(s) for offers.

Kanmon Payments API

The Payments API from Kanmon — 3 operation(s) for payments.

Kanmon Prequalifications API

The Prequalifications API from Kanmon — 1 operation(s) for prequalifications.

Kanmon Sandbox Utilities API

The Sandbox Utilities API from Kanmon — 2 operation(s) for sandbox utilities.

Kanmon Users API

The Users API from Kanmon — 3 operation(s) for users.

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.

kanmon-mcp.yml

MCP SERVER

Event 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.

Kanmon Webhooks

ASYNCAPI

Security 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.

Kanmon Authentication

apiKey · 1 scheme

SECURITY

Kanmon Domain Security

TLSv1.3 · DMARC

SECURITY

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.

Kanmon Agentic Access

35 operations · 14 acting · 1 human-in-the-loop

35 operations · 14 acting

AGENTIC

Resources

Every other property we hold for Kanmon — 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 2

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

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/kanmon · machine-readable index on apis.io