Capchase
Capchase provides embedded financing and B2B payment infrastructure for software and hardware vendors. Its Capchase Pay API lets vendors offer buyers flexible installment payment terms at checkout while the vendor is paid the full contract value upfront. Vendors create buyer companies, run automated KYB/underwriting qualification, create subscriptions that generate hosted payment links, list and retrieve subscription status, and pull instalment receipts. The v2 REST API is served from universe.capchase.com, uses HTTP Basic authentication (clientId / clientSecret), ships a Playground environment, and is documented on a ReadMe developer portal with an OpenAPI reference and an AI-agent llms.txt index. Sector: fintech; backed by QED Investors.
Capchase publishes 1 API contract indexed on the APIs.io network: Pay API. Tagged areas include Company, Fintech, Payments, Embedded Finance, and Financing.
The Capchase catalog on APIs.io includes 1 Spectral governance ruleset.
Capchase’s developer surface includes documentation, API reference, getting-started guide, authentication, engineering blog, signup flow, sandbox, and 22 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Stripe App Marketplace and Partner Ecosystem (builders on Stripe) | standard | 40.9 (thin) | - | - |
| Consumer Lending Licensing (UK, US, Canada credit licence registers) | standard | 40.9 (thin) | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Capchase Pay API
The Pay API from Capchase — 8 operation(s) for pay.
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Capchase Pay API
OPEN COLLECTIONArazzo Workflows 1
Multi-step API workflows described with the Arazzo specification.
Capchase Qualify a Buyer and Create a Financed Subscription
Create a buyer, confirm qualification, then create a financed subscription and read its status.
ARAZZOAgent Skills 2
Packaged agent skills for driving this provider's APIs from an AI assistant.
Terms of Service 1
What its API terms permit and prohibit, quoted from its own page.
Privacy & Data 1
Its role, the data it processes, retention and transfers, quoted from its own privacy page.
Deprecation Policy 1
Notice periods, support windows and the headers it sends, quoted from its own page.
Compliance 1
Attestations the provider states (SOC 2, ISO 27001 and others), quoted from its own trust page. APIs.io verifies none of them.
Eligibility 1
Who may sign up and where, quoted from its own terms.
AI Preferences 1
Its stance on AI training, inference and agents, quoted from its own pages.
Spectral Rules 1
Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.
Capchase API Rules
SPECTRALOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Capchase Pay Overlay
DERIVEDSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access (API Evangelist recommendations) 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
Source (apis.yml)
Capchase API — frequently asked questions
Does Capchase have an API?
Yes. APIs.io lists 1 API from Capchase, including Capchase Pay API.
Is there an OpenAPI specification for the Capchase API?
Yes. APIs.io indexes 1 OpenAPI specification for Capchase, each linked for download from this page.
How do I authenticate with the Capchase API?
Capchase uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Capchase Authentication.
Is the Capchase API ready for AI agents?
Capchase has a Kin Score of 47.0 out of 100 (developing) and an Agent Readiness score of 23.6 (agent-aware), scored by API Evangelist on 2026-11-13.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.