Try itExperimental
See what an agent can do with Column 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.column.com/bank-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
n/a
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 Column 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
✓8/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
✓8/10
Idle balances can earn — interest-bearing accounts or documented sweep options, with the rate mechanics and who keeps the spread spelled out
~3/10
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 · Official CLI · 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
!3/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
—0/10
Download a machine-readable API spec (OpenAPI or equivalent)
✓9/10
unlocks → 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
~5/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
—–
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
~7/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
~5/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
—–
Work the onboarding queue — see why an application is pending, supply additional documents, and understand which decisions are mine versus the bank's
—–
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
~2/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
—–
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
~5/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
~4/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
~6/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
—–
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 | 0/10 | ||
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 | 9/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 | 6/10 | Tprobed | |
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 | 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 | disputed | 3/10 | Dcontradicted | |
Use an official CLI G Agent access | 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 | |
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 | 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 | Xcommunity | |
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 | 8/10 | Xcommunity | |
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 | 6/10 | Tprobed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 6/10 | Cclaimed | |
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 | |
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 | 5/10 | Cclaimed | |
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 | |
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 | ||
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | 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 | ||
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 | none | untested | none yet | |
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 | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
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 | full | 8/10 | Xcommunity | |
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 | Tprobed | |
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 | 7/10 | Xcommunity | |
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 | 7/10 | Xcommunity | |
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 | |
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 | 5/10 | Xcommunity | |
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 | Xcommunity | |
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 | partial | 4/10 | Cclaimed | |
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 | partial | 3/10 | Xcommunity | |
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 | 2/10 | Xcommunity | |
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 | n/a | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | 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 | |
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 | 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 | |
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 | 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 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 | 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 | |
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 | 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 33 stories with headroom
What would move Column’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
Missing: any mention of an MCP server, agent integration, or AI-native tooling.
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
Missing: any mention of 'agent' or AI-native access patterns, documented amount-cap/allowlist controls tied to agent credentials, and a named agent-banking product or guide.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
Missing: any documented in-product rule/trigger definition, conditional action execution, or automation workflow builder.
Banking onboarding — stories about banking onboarding in this arenaCustomer verification is programmatic — KYC for individuals and KYB for businesses with document collection, watchlist screening, and clearly modeled application states
nonemoves PA Scoreimpact 30
The evidence pack covers Column's payments, accounts, cards, checks, wires, and reporting APIs, but nowhere mentions KYC/KYB identity verification, document collection, watchlist/OFAC screening, or application state modeling for onboarding customers programmatically.
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: any explicit reconciliation SLA/process documentation, third-party audit or attestation of ledger-to-bank-balance matching, and any commentary addressing the Synapse-style failure mode directly.
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
nonemoves Built-in AIimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
Column is a banking API platform with no evidence of an official CLI; in fact a Column engineer explicitly states they don't even provide SDKs, only HTTP APIs, and no CLI is mentioned anywhere in docs or community evidence.
Showing the top 8 of 33 — 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 · 24 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Markdown docs20 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
- Idle balances can earn — interest-bearing accounts or documented sweep options, with the rate mechanics and who keeps the spread spelled out
- 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
- Explore an interactive API reference with runnable examples
- Test against a sandbox environment without touching production data
- 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
- 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
- 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
- Money can cross borders — international wires or SWIFT, FX with transparent rates, and the coverage map of currencies and corridors documented
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- 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
Hacker News14 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
- Idle balances can earn — interest-bearing accounts or documented sweep options, with the rate mechanics and who keeps the spread spelled out
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Test against a sandbox environment without touching production data
- 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
- Set risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement paths
- Checks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paper
- 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
docs.column.com11 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
- Build against official SDKs
- Explore an interactive API reference with runnable examples
- 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
- 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 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
- Export all of my data in open formats and leave
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
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- 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
llms.txt4 stories
- Point an agent at llms.txt or agent-oriented docs
- Drive the product through a documented public API
- Explore an interactive API reference with runnable examples
- 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
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.column.com/bank-accounts | head -3 # keyless → 401reproduced$ curl -si https://api.column.com/bank-accounts | head -3 # [redacted]less → 401 HTTP/2 401 date: Tue, 15 Sep 2026 09:12:28 GMT content-length: 0
$curl -sL https://column.com/llms.txt | head -3reproduced$ curl -sL https://column.com/llms.txt | head -3 # Column > Column N.A. is a nationally chartered bank built for developers. Access banking infrastructure including ACH, wires, real-time payments, checks, lending, and card issuing through a modern API.
$curl -s https://docs.column.com/openapi.yaml | head -4reproduced$ curl -s https://docs.column.com/openapi.yaml | head -4 # This file is auto-generated by: columnctl releases generate-openapi-spec # Do not edit manually. openapi: 3.0.3
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
6 of 13 testable claims verified · 1 contradicted → integrity 31/100
12 distinct capability claims found in Column’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
6
Verified
6
Unverified
1
Contradicted
11
Undersold
Verified (7)
“Supports building payment workflows combining wires, book transfers, and ACH credits”
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 ↗
“Open and manage FDIC-insured bank accounts programmatically, including FBO, sweep, clearing, and custom account types”
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 ↗
“Sandbox endpoints to simulate incoming wires and ACH credits/debits for testing”
Test against a sandbox environment without touching production datafullproof ↗
“Issue and deposit checks programmatically via API”
Checks still work — programmatic check issuance and check deposit with image capture, because real businesses still receive and send paperpartialproof ↗
“Send, receive, and request payments instantly via FedNow and RTP networks”
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 ↗
“OpenAPI spec (JSON) available to generate type-safe client SDKs in any language”
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
“Build a card program offering virtual and physical cards, working with all major networks and issuer processors”
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 (7)
“Supports building payment workflows combining wires, book transfers, and ACH credits”
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 ↗
“Send and receive international transfers over the SWIFT network”
Money can cross borders — international wires or SWIFT, FX with transparent rates, and the coverage map of currencies and corridors documentedpartialproof ↗
“Configurable webhook endpoints (via API or Dashboard) for event notifications”
“Configurable webhook endpoints (via API or Dashboard) for event notifications”
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 ↗
“Bank account transaction and summary reports available in CSV, JSON, and Parquet formats”
Export all of my data in open formats and leavepartialproof ↗
“Single unified endpoint to query transfers across all payment types”
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 ↗
“Full raw message data for domestic and international wires, accessible via get wire transfer API endpoint”
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 ↗
Contradicted (1)
“OpenAPI spec (JSON) available to generate type-safe client SDKs in any language”
Undersold (11)
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 ↗
Issue unique account and routing numbers at scale — virtual accounts for reconciliation, per-customer collection accounts, and sub-accounts under a master structurefullproof ↗
Idle balances can earn — interest-bearing accounts or documented sweep options, with the rate mechanics and who keeps the spread spelled outpartialproof ↗
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 ↗
Explore an interactive API reference with runnable examplespartialproof ↗
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 ↗
Set risk controls per account and per program — transaction and velocity limits, holds on suspicious activity, and account freezes with documented reinstatement pathspartialproof ↗
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 ↗
Business model
Contact-sales as of Sept 2026 — column.com/pricing was removed this week (now redirects home); the only published fees left are international wire fees in the docs. A nationally chartered bank selling direct, no middleware.
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
