$HEADLESS SYSTEMS
03 / Scorecard / Payments

Increase

C
Headless Index
44/100
denominator 80
JAIRF
74.3/100
AI-Aware
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Editorial verdict
Increase is partially headless and partly UI-led. The Headless Index thesis-fit score of 44/100 puts it mid-table on the index, and JAIRF v1.0.0 puts it at 74.3/100 (Level 2, AI-Aware). In practice, vendors at this tier are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where Increase lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Increase is a modern banking API for fintech builders, positioned as the bank-of-record alternative to traditional BIN sponsors. Stainless-generated SDKs across Node, Python, Java, Go, Ruby, and Kotlin. The Stainless toolchain implies a maintained OpenAPI source-of-truth. Bearer auth, idempotency keys, and dated API versioning are first-class.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? Stainless-generated SDKs mean an OpenAPI source-of-truth exists; the spec is referenced through docs and SDK builds. Schema discoverability is reference-class for fintech.[2] An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Accounts, account numbers, transactions, transfers (ACH, wire, real-time payments), checks, cards, files, and physical card programs are all programmable. The Increase dashboard handles configuration that requires compliance review; the API does everything else. Sandbox plus production parity is explicit.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Increase MCP server has been published. The Stainless-style spec posture and clean SDK ecosystem make agent integration straightforward when downstream tooling adopts it.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. On webhooks and events, the docs crawler did not locate a webhooks reference page or events catalog. Editorial review should confirm whether the vendor publishes events at all, and if so whether signing and replay are documented. Net assessment: integrators can build agent flows against Increase, but the rough edge to plan around is MCP posture[5]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent5/20
scored

Increase is a modern banking API for fintech builders, positioned as the bank-of-record alternative to traditional BIN sponsors. Stainless-generated SDKs across Node, Python, Java, Go, Ruby, and Kotlin. The Stainless toolchain implies a maintained OpenAPI source-of-truth. Bearer auth, idempotency keys, and dated API versioning are first-class.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPI specPublished, 238 operations
  • GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
  • SDKs maintainedNone detected in vendor org
cite (3)
  • openapi.url@2026-05-20
  • graphql.probes_tried@2026-05-20
  • github.sdks@2026-05-20
Headless operation15/20
scored

Accounts, account numbers, transactions, transfers (ACH, wire, real-time payments), checks, cards, files, and physical card programs are all programmable. The Increase dashboard handles configuration that requires compliance review; the API does everything else. Sandbox plus production parity is explicit.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +API operations exposed238 operations in OpenAPI spec
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (8)
  • openapi.operations_count@2026-05-20
  • docs.pages_crawled@2026-05-20
  • docs.pages_crawled@2026-05-20
  • docs.topics_found.setup@2026-05-20
  • docs.topics_found.billing@2026-05-20
  • docs.topics_found.teams@2026-05-20
  • docs.topics_found.cli@2026-05-20
  • docs.topics_found.schema@2026-05-20
MCP & agent posture0/20
scored

No first-party Increase MCP server has been published. The Stainless-style spec posture and clean SDK ecosystem make agent integration straightforward when downstream tooling adopts it.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • Official MCP serverNone found in vendor's GitHub org or the official MCP registry
  • Community MCP serversNone found
  • Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)
cite (3)
  • mcp.registry_query@2026-05-20
  • mcp.github_search_query@2026-05-20
  • github.sdks@2026-05-20
Schema observability15/20
scored

Stainless-generated SDKs mean an OpenAPI source-of-truth exists; the spec is referenced through docs and SDK builds. Schema discoverability is reference-class for fintech.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPIPublished at https://increase.com/openapi.json (OpenAPI 3.1.0, 238 operations)
  • GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)
cite (2)
  • openapi.url@2026-05-20
  • graphql.probes_tried@2026-05-20
Webhooks & eventsUnknown
Unknown

Increase webhooks deliver account-lifecycle, transaction, transfer-status, and card events with documented signature header and retry policy. Catalog covers the banking lifecycle in depth and is one of the more substantive webhook products in the fintech category.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • docs.pages_crawled@2026-05-20
JAIRF · 6 dimensions
FCFoundational Compliance
70/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility
37/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience
76.5/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability
100/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity
80/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability
75/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:C band: scores 40-75 range

04 / Embed

Show Increase's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Calibration

How THI compares to external scorers

SourceScoreMeasuresLast checked
Fern Agent Scorenot foundDocumentation completeness and SDK shape (~22 checks)
CLIRank Agent Friendlinessnot foundCLI readiness, docs quality, and overall agent affordances
Cloudflare Is It Agent Ready?blockedCloudflare's manual agent-readiness heuristic per vendor URL
Jentic ScorecardJAIRF-based scorecard requiring a public OpenAPI specification
THI 44 vs external median 0

No external scores available to calibrate against.