CRB
CRB (Cross River Bank) is a New Jersey-chartered, FDIC-insured bank and financial technology infrastructure provider founded in 2008 and headquartered in Fort Lee, New Jersey. Cross River pairs a regulated bank with an API-driven core it calls the Cross River Operating System (COS), letting fintech companies, neobanks, lenders, and platforms embed banking, payments, cards, and lending products directly into their applications. Its developer platform exposes Accounts and Payments APIs spanning ACH, RTP, FedNow, wires, international payments, push-to-card, card issuing and processing, subledgers, lending origination, and onchain/stablecoin rails, secured with OAuth2 client credentials and delivered with an isolated sandbox, Postman collection, webhooks, and a dated changelog. Cross River is known for powering leading fintech partners including Stripe, Coinbase, Affirm, Upgrade, and Intuit, and was surfaced in the API Evangelist network as a Battery Ventures portfolio company.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles CRB the way a machine reads it — 3 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — CRB scores 28.6/100 (emerging), with a separate agent-readiness read of 15/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile CRB
Each block below is one kind of artifact we hold for CRB. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Cross River Operating System (COS) API
The Cross River Operating System (COS) API is Cross River's API-driven bank core, exposing Accounts and Payments products (ACH, RTP, FedNow, wires, international payments, cards...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for CRB — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/crb · machine-readable index on apis.io