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.

Capchase’s developer surface includes documentation, API reference, getting-started guide, authentication, engineering blog, signup flow, sandbox, and 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

44.4/100 developing ▬ flat Agent 24/100 agent aware Front door AI 3/6 light saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 published contract 2 Agent Skills

Company Fintech Payments Embedded Finance Financing B2B SaaSRevenue FinancingBuy Now Pay Later KYB Underwriting

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 44.4/100 · developing

Contract Quality 10.0 / 21

Developer Ergonomics 10.4 / 17

Access Clarity 7.2 / 17

Operational Transparency 1.5 / 11

Contract Governance 1.9 / 10

Discoverability 5.6 / 9

Regulatory Posture 3.9 / 15

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 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 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Insurance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/capchase/"><img src="https://apis.io/badge/capchase/card.svg" alt="Capchase on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 47.1 — up to +13.2 composite points
Access Clarity scores 42.1 — up to +11.6 composite points
Operational Transparency scores 13.2 — up to +11.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/capchase/apis.yml: open an issue on github.com/api-evangelist/capchase to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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.

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 COLLECTION

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

ARAZZO

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Qualify a buyer and create a financed subscription

AGENT SKILL

Reconcile subscriptions and pull instalment receipts

AGENT SKILL

OpenAPI 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

3 actions · documentation · capchase-pay-openapi.yml

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Capchase Authentication

http · 1 scheme

SECURITY

Capchase Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Capchase Agentic Access

9 operations · 5 acting · 5 human-in-the-loop

9 operations · 5 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Lifecycle

Lifecycle

Conformance

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

Compliance

Compliance

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Deprecation

Deprecation

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: capchase
name: Capchase
description: '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.'
url: https://raw.githubusercontent.com/api-evangelist/capchase/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- qed-investors
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
image: https://cdn.prod.website-files.com/6146543ab50f167ae088b201/61701898ec2756274d6e8665_256px.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-21
tags:
- Company
- Fintech
- Payments
- Embedded Finance
- Financing
- B2B SaaS
- Revenue Financing
- Buy Now Pay Later
- KYB
- Underwriting
tags_raw:
- Company
- Fintech
- Payments
- Embedded Finance
- Financing
- B2B SaaS
- Revenue Financing
- BNPL
- KYB
- Underwriting
apis:
- aid: capchase:capchase-pay-api
  name: Capchase Pay API
  description: The Pay API from Capchase — 8 operation(s) for pay.
  humanURL: https://capchase.readme.io/reference
  baseURL: https://universe.capchase.com/api/v2
  tags:
  - Pay
  properties:
  - type: OpenAPI
    url: openapi/capchase-pay-api-openapi.yml
  - type: Authentication
    url: authentication/capchase-authentication.yml
  - type: ErrorCatalog
    url: errors/capchase-error-codes.yml
  - type: Conventions
    url: conventions/capchase-conventions.yml
  - type: DataModel
    url: data-model/capchase-data-model.yml
  - type: AgenticAccess
    url: agentic-access/capchase-agentic-access.yml
  - type: Arazzo
    url: arazzo/capchase-buyer-to-subscription.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.capchase.com/blog/rss.xml
  type: BlogRSS
- type: X-MCPServerCandidate
  url: mcp/capchase-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Overlay
  url: overlays/capchase-pay-overlay.yaml
- type: Website
  url: https://www.capchase.com/
- type: DeveloperPortal
  url: https://capchase.readme.io/
- type: Documentation
  url: https://capchase.readme.io/docs
- type: APIReference
  url: https://capchase.readme.io/reference
- type: GettingStarted
  url: https://capchase.readme.io/docs/get-started
- type: Authentication
  url: authentication/capchase-authentication.yml
- type: GitHubOrganization
  url: https://github.com/Capchase
- type: Blog
  url: https://www.capchase.com/blog
- type: SignUp
  url: https://app.capchase.com/login
- type: TermsOfService
  url: https://www.capchase.com/terms-of-use
- type: PrivacyPolicy
  url: https://www.capchase.com/privacy-policy
- type: Deprecation
  url: https://capchase.readme.io/reference/migrating-from-v1
- type: Compliance
  url: https://www.capchase.com/
- type: LLMsTxt
  url: llms/capchase-llms.txt
- type: Sandbox
  url: sandbox/capchase-sandbox.yml
- type: Conventions
  url: conventions/capchase-conventions.yml
- type: Lifecycle
  url: lifecycle/capchase-lifecycle.yml
- type: Conformance
  url: conformance/capchase-conformance.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/capchase-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

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 44.4 out of 100 (developing) and an Agent Readiness score of 23.6 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/capchase"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/capchase/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/capchase/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.