Install
npm install increaseTry itExperimental
See what an agent can do with Increase before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si https://api.increase.com/accounts | head -3 # keyless → 401recorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Account provisioning — stories about account provisioning in this arenaAccount provisioningevidence →
Stories about account provisioning in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Banking agent access — stories about banking agent access in this arenaBanking agent accessevidence →
Stories about banking agent access in this arena
Banking cards — stories about banking cards in this arenaBanking cardsevidence →
Stories about banking cards in this arena
Banking ledger — stories about banking ledger in this arenaBanking ledgerevidence →
Stories about banking ledger in this arena
Banking onboarding — stories about banking onboarding in this arenaBanking onboardingevidence →
Stories about banking onboarding in this arena
Banking risk controls — stories about banking risk controls in this arenaBanking risk controlsevidence →
Stories about banking risk controls in this arena
Money movement — stories about money movement in this arenaMoney movementevidence →
Stories about money movement in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Sponsor model — stories about sponsor model in this arenaSponsor modelevidence →
Stories about sponsor model in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Increase stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Account provisioning — stories about account provisioning in this arenaAccount provisioning
Stories about account provisioning in this arena
Open a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launch
✓7/10
The account structure is transparent — whether funds sit in FBO pools or individual accounts, where FDIC insurance actually attaches, and who can see the ledger, all documented plainly
~5/10
Issue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structure
~6/10
Idle balances can earn — interest-bearing accounts or documented sweep options, with the rate mechanics and who keeps the spread spelled out
—–
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓9/10
unlocks → Official SDKs · Scoped API keys · MCP server · Versioning policy · Full data export · An agent can operate an account within policy — scoped credentials that let it read balances and initiate transfers under amount caps and counterparty allowlists, a use the vendor documents by name · The product ships its own AI for banking operations — natural-language search over transactions, drafted responses to disputes and alerts, anomaly summaries — built in, not bolted on
Subscribe to events via webhooks
✓8/10
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
—–
Download a machine-readable API spec (OpenAPI or equivalent)
✓9/10
unlocks → Interactive API docs · Official SDKs · MCP server
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
✓8/10
Explore an interactive API reference with runnable examples
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
—–
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
~5/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Banking agent access — stories about banking agent access in this arenaBanking agent access
Stories about banking agent access in this arena
An agent can operate an account within policy — scoped credentials that let it read balances and initiate transfers under amount caps and counterparty allowlists, a use the vendor documents by name
—0/10
An agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboard
~6/10
The product ships its own AI for banking operations — natural-language search over transactions, drafted responses to disputes and alerts, anomaly summaries — built in, not bolted on
—–
Banking cards — stories about banking cards in this arenaBanking cards
Stories about banking cards in this arena
Accounts come with cards — issue virtual and physical debit cards tied to the account through the same API, with spend controls and digital wallet support
~4/10
Card and ACH disputes are handled properly — Reg E investigation timelines, provisional credit mechanics, and my operational responsibilities documented and tooled
—–
Banking ledger — stories about banking ledger in this arenaBanking ledger
Stories about banking ledger in this arena
The ledger is real-time and event-driven — balance reads that reflect holds and pending activity, and webhooks for every transaction state change so my system mirrors the bank exactly
~6/10
Transaction data is rich enough to build on — counterparty details, rail-specific metadata, stable identifiers, and enrichment that makes a raw bank feed usable in-product
~6/10
The paper obligations are automated — monthly statements generated per account, and tax documents (1099-INT) produced and retrievable through the API
—–
Banking onboarding — stories about banking onboarding in this arenaBanking onboarding
Stories about banking onboarding in this arena
Customer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application states
~3/10
Work the onboarding queue — see why an application is pending, supply additional documents, and understand which decisions are mine versus the bank's
—0/10
Banking risk controls — stories about banking risk controls in this arenaBanking risk controls
Stories about banking risk controls in this arena
Set risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement paths
~4/10
Fraud economics are explicit — who eats ACH return fraud, card disputes, and account takeover losses, with the platform's prevention tooling documented alongside the liability split
—–
Growth doesn't hit invisible walls — program-level limits, approval stages, and the path to raising them are documented rather than discovered in an email from the bank
~3/10
Money movement — stories about money movement in this arenaMoney movement
Stories about money movement in this arena
Originate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhooks
~4/10
Checks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paper
~5/10
The faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documented
✓8/10
Money can cross borders — international wires or SWIFT, FX with transparent rates, and the coverage map of currencies and corridors documented
—0/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Sponsor model — stories about sponsor model in this arenaSponsor model
Stories about sponsor model in this arena
Exactly who holds the charter — whether the platform is a bank, a direct program with a named partner bank, or middleware between me and someone else's sponsor — and what happens to my customers if the platform fails
~5/10
The compliance workload is tooled — transaction monitoring, sanctions screening, case management for alerts, and SAR-filing support with a clear split of duties between me, the platform, and the bank
~3/10
The platform ledger reconciles to the bank core — documented daily reconciliation between what the API reports and what the bank holds, the failure that sank Synapse-era programs
—0/10
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | full | 8/10 | Cclaimed | |
Open a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launch C Account opening | developer | Account provisioning — stories about account provisioning in this arenaAccount provisioning | 3 | full | 7/10 | Xcommunity | |
The ledger is real-time and event-driven — balance reads that reflect holds and pending activity, and webhooks for every transaction state change so my system mirrors the bank exactly C Balances events | developer | Banking ledger — stories about banking ledger in this arenaBanking ledger | 3 | partial | 6/10 | Cclaimed | |
Exactly who holds the charter — whether the platform is a bank, a direct program with a named partner bank, or middleware between me and someone else's sponsor — and what happens to my customers if the platform fails C Charter clarity | founder | Sponsor model — stories about sponsor model in this arenaSponsor model | 3 | partial | 5/10 | Xcommunity | |
The account structure is transparent — whether funds sit in FBO pools or individual accounts, where FDIC insurance actually attaches, and who can see the ledger, all documented plainly C Fbo structures | finance lead | Account provisioning — stories about account provisioning in this arenaAccount provisioning | 3 | partial | 5/10 | Xcommunity | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 4/10 | Cclaimed | |
Originate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhooks C Ach | developer | Money movement — stories about money movement in this arenaMoney movement | 3 | partial | 4/10 | Cclaimed | |
Customer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application states C Kyc kyb | developer | Banking onboarding — stories about banking onboarding in this arenaBanking onboarding | 3 | partial | 3/10 | Cclaimed | |
An agent can operate an account within policy — scoped credentials that let it read balances and initiate transfers under amount caps and counterparty allowlists, a use the vendor documents by name C Agent operations | ai-native user | Banking agent access — stories about banking agent access in this arenaBanking agent access | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | 0/10 | ||
The platform ledger reconciles to the bank core — documented daily reconciliation between what the API reports and what the bank holds, the failure that sank Synapse-era programs C Reconciliation | finance lead | Sponsor model — stories about sponsor model in this arenaSponsor model | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | full | 8/10 | Tprobed | |
The faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documented C Instant rails | developer | Money movement — stories about money movement in this arenaMoney movement | 2 | full | 8/10 | Xcommunity | |
An agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboard C Agent visibility | ai-native user | Banking agent access — stories about banking agent access in this arenaBanking agent access | 2 | partial | 6/10 | Tprobed | |
Issue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structure C Virtual accounts | developer | Account provisioning — stories about account provisioning in this arenaAccount provisioning | 2 | partial | 6/10 | Cclaimed | |
Transaction data is rich enough to build on — counterparty details, rail-specific metadata, stable identifiers, and enrichment that makes a raw bank feed usable in-product C Data quality | developer | Banking ledger — stories about banking ledger in this arenaBanking ledger | 2 | partial | 6/10 | Cclaimed | |
Checks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paper C Checks | ops user | Money movement — stories about money movement in this arenaMoney movement | 2 | partial | 5/10 | Cclaimed | |
Accounts come with cards — issue virtual and physical debit cards tied to the account through the same API, with spend controls and digital wallet support C Card issuance | developer | Banking cards — stories about banking cards in this arenaBanking cards | 2 | partial | 4/10 | Tprobed | |
Set risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement paths C Limits holds | ops user | Banking risk controls — stories about banking risk controls in this arenaBanking risk controls | 2 | partial | 4/10 | Cclaimed | |
Growth doesn't hit invisible walls — program-level limits, approval stages, and the path to raising them are documented rather than discovered in an email from the bank C Program scaling | founder | Banking risk controls — stories about banking risk controls in this arenaBanking risk controls | 2 | partial | 3/10 | Cclaimed | |
The compliance workload is tooled — transaction monitoring, sanctions screening, case management for alerts, and SAR-filing support with a clear split of duties between me, the platform, and the bank C Compliance tooling | ops user | Sponsor model — stories about sponsor model in this arenaSponsor model | 2 | partial | 3/10 | Cclaimed | |
Money can cross borders — international wires or SWIFT, FX with transparent rates, and the coverage map of currencies and corridors documented C International | founder | Money movement — stories about money movement in this arenaMoney movement | 2 | none | 0/10 | ||
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Work the onboarding queue — see why an application is pending, supply additional documents, and understand which decisions are mine versus the bank's C Review queues | ops user | Banking onboarding — stories about banking onboarding in this arenaBanking onboarding | 2 | none | 0/10 | ||
Card and ACH disputes are handled properly — Reg E investigation timelines, provisional credit mechanics, and my operational responsibilities documented and tooled C Disputes | ops user | Banking cards — stories about banking cards in this arenaBanking cards | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Fraud economics are explicit — who eats ACH return fraud, card disputes, and account takeover losses, with the platform's prevention tooling documented alongside the liability split C Loss allocation | finance lead | Banking risk controls — stories about banking risk controls in this arenaBanking risk controls | 2 | none | untested | none yet | |
Idle balances can earn — interest-bearing accounts or documented sweep options, with the rate mechanics and who keeps the spread spelled out C Yield | finance lead | Account provisioning — stories about account provisioning in this arenaAccount provisioning | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
The paper obligations are automated — monthly statements generated per account, and tax documents (1099-INT) produced and retrievable through the API C Statements | ops user | Banking ledger — stories about banking ledger in this arenaBanking ledger | 2 | none | untested | none yet | |
The product ships its own AI for banking operations — natural-language search over transactions, drafted responses to disputes and alerts, anomaly summaries — built in, not bolted on C Builtin ai | ops user | Banking agent access — stories about banking agent access in this arenaBanking agent access | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 37 stories with headroom
What would move Increase’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
Increase is a banking-API platform, so publishing an official MCP server for agent connectivity is a fair question, but the evidence pack shows only REST API docs, an OpenAPI spec, a CLI, and webhooks—no mention of an MCP server or MCP integration anywhere.
Banking agent access — stories about banking agent access in this arenaAn agent can operate an account within policy — scoped credentials that let it read balances and initiate transfers under amount caps and counterparty allowlists, a use the vendor documents by name
nonemoves PA Scoreimpact 30
Increase's docs show general transfer APIs, holds, and optional human approval for transfers, but there is no evidence of a named feature for AI-agent scoped credentials with amount caps and counterparty allowlists — the story's specific banking-agent-access capability is unevidenced.
Sponsor model — stories about sponsor model in this arenaThe platform ledger reconciles to the bank core — documented daily reconciliation between what the API reports and what the bank holds, the failure that sank Synapse-era programs
nonemoves PA Scoreimpact 30
Missing: documented reconciliation cadence/process, bank-core balance verification API or report, any third-party audit or attestation of ledger accuracy.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
The evidence shows Increase exposes account, transfer, and entity data via a REST/JSON API and webhooks, but there is no documented bulk data-export feature, open-format data dump, or migration/offboarding tooling that would let a customer pull all their data and leave.
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
Evidence shows Increase is a REST/JSON banking API with docs, OpenAPI spec, and a CLI, but nothing indicates a natural-language command interface, chat/agent layer, or NL-to-API translation capability.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Missing: scoped API key creation, permission/role-based access controls, agent-specific credential issuance documentation.
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
Evidence shows an OpenAPI spec, a CLI, and llms.txt/docs, but nothing in the pack documents official client SDKs (e.g., Python, Ruby, Node libraries) that AI-native developers could build against beyond the CLI tool.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
Evidence shows only static markdown documentation and a raw OpenAPI spec, with no mention of an interactive API reference or runnable/try-it-out examples anywhere in the pack.
Showing the top 8 of 37 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map5 surfaces · 25 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Documentation docs24 stories
- Open a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launch
- The account structure is transparent — whether funds sit in FBO pools or individual accounts, where FDIC insurance actually attaches, and who can see the ledger, all documented plainly
- Issue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structure
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Download a machine-readable API spec (OpenAPI or equivalent)
- Test against a sandbox environment without touching production data
- Define rules that trigger actions automatically on events
- An agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboard
- Accounts come with cards — issue virtual and physical debit cards tied to the account through the same API, with spend controls and digital wallet support
- The ledger is real-time and event-driven — balance reads that reflect holds and pending activity, and webhooks for every transaction state change so my system mirrors the bank exactly
- Transaction data is rich enough to build on — counterparty details, rail-specific metadata, stable identifiers, and enrichment that makes a raw bank feed usable in-product
- Customer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application states
- Set risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement paths
- Growth doesn't hit invisible walls — program-level limits, approval stages, and the path to raising them are documented rather than discovered in an email from the bank
- Originate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhooks
- Checks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paper
- The faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documented
- Do everything through the API that I can do in the UI
- Exactly who holds the charter — whether the platform is a bank, a direct program with a named partner bank, or middleware between me and someone else's sponsor — and what happens to my customers if the platform fails
- The compliance workload is tooled — transaction monitoring, sanctions screening, case management for alerts, and SAR-filing support with a clear split of duties between me, the platform, and the bank
OpenAPI spec6 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Download a machine-readable API spec (OpenAPI or equivalent)
- An agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboard
- Do everything through the API that I can do in the UI
Hacker News5 stories
- Open a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launch
- The account structure is transparent — whether funds sit in FBO pools or individual accounts, where FDIC insurance actually attaches, and who can see the ledger, all documented plainly
- Drive the product through a documented public API
- The faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documented
- Exactly who holds the charter — whether the platform is a bank, a direct program with a named partner bank, or middleware between me and someone else's sponsor — and what happens to my customers if the platform fails
GitHub README3 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si https://api.increase.com/accounts | head -3 # keyless → 401reproduced$ curl -si https://api.increase.com/accounts | head -3 # [redacted]less → 401 HTTP/2 401 content-type: application/problem+json x-request-id: e97b153f030ce5aa100ec92687425670
$curl -s https://increase.com/openapi.json | head -c 120reproduced$ curl -s https://increase.com/openapi.json | head -c 120
{
"components": {
"responses": {
"errorResponse": {
"content": {
"application/json": {
$curl -sL https://increase.com/llms.txt | head -3reproduced$ curl -sL https://increase.com/llms.txt | head -3 # Increase > Increase builds modern banking APIs that enable technology companies to programmatically store, move, and reconcile money.
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
3 of 10 testable claims verified · 0 contradicted → integrity 30/100
15 distinct capability claims found in Increase’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
3
Verified
7
Unverified
0
Contradicted
15
Undersold
Verified (6)
“Send domestic wire transfers via a POST /wire_transfers API call”
The faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documentedfullproof ↗
“Send Real-Time Payments (RTP) any time of day with instant settlement”
The faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documentedfullproof ↗
“Routing Numbers API lets you confirm whether an institution supports Real-Time Payments”
The faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documentedfullproof ↗
“Send FedNow transfers, checking reachability via Routing Number endpoint and falling back to ACH or wire”
The faster rails are there when I need them — domestic wires, RTP, and FedNow origination and receipt through the same API, with per-rail capabilities documentedfullproof ↗
“Access multi-million-dollar FDIC insurance through participating IntraFi network banks directly in Increase”
The account structure is transparent — whether funds sit in FBO pools or individual accounts, where FDIC insurance actually attaches, and who can see the ledger, all documented plainlypartialproof ↗
“Real-time card authorization decisions are exposed as an API object with a real-time webhook for you to approve/decline”
Accounts come with cards — issue virtual and physical debit cards tied to the account through the same API, with spend controls and digital wallet supportpartialproof ↗
Unverified (9)
“Originate ACH transfers via a POST /ach_transfers API call”
Originate ACH through the API — credits and debits, same-day windows, and the unhappy paths (returns, NOCs, reversals) modeled as first-class objects with webhookspartialproof ↗
“Issue physical checks programmatically; Increase prints, mails, and tracks them through deposit/return”
Checks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paperpartialproof ↗
“Webhooks notify your application of transaction events so you can trigger actions like user alerts”
The ledger is real-time and event-driven — balance reads that reflect holds and pending activity, and webhooks for every transaction state change so my system mirrors the bank exactlypartialproof ↗
“Full sandbox parity with production API/dashboard, plus special Simulation APIs only in sandbox”
Test against a sandbox environment without touching production datafullproof ↗
“Instantly create and manage multiple account numbers for a single account programmatically”
Issue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structurepartialproof ↗
“Optionally require approval from another team member before a transfer executes”
Set risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement pathspartialproof ↗
“Issue each investor/customer a unique account number for automatic reconciliation across Wire, RTP, ACH, or Check funds”
Issue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structurepartialproof ↗
“Entity validation results are exposed via the API for each data version, flagging data issues to follow up on”
Customer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application statespartialproof ↗
“Place holds on an account to reserve funds for known future activity without moving money”
Set risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement pathspartialproof ↗
Undersold (15)
Open a real, insured deposit account through the API — application to active account fully programmatic, with sandbox parity so the flow is tested before launchfullproof ↗
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
An agent can read the full banking picture — accounts, transactions, pending activity, documents — through a clean API or MCP surface without screen-scraping a dashboardpartialproof ↗
Transaction data is rich enough to build on — counterparty details, rail-specific metadata, stable identifiers, and enrichment that makes a raw bank feed usable in-productpartialproof ↗
Growth doesn't hit invisible walls — program-level limits, approval stages, and the path to raising them are documented rather than discovered in an email from the bankpartialproof ↗
Do everything through the API that I can do in the UIfullproof ↗
Exactly who holds the charter — whether the platform is a bank, a direct program with a named partner bank, or middleware between me and someone else's sponsor — and what happens to my customers if the platform failspartialproof ↗
The compliance workload is tooled — transaction monitoring, sanctions screening, case management for alerts, and SAR-filing support with a clear split of duties between me, the platform, and the bankpartialproof ↗
Business model
The arena's only published rate card: per-transaction fees (wires $15, RTP/FedNow $2.50, per-item ACH) at increase.com/fees, custom pricing for platforms; banking via its own Increase Bank (Jul 2026) plus partner banks.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
