River Financial

River Financial Inc. (river.com) is a regulated U.S.-based Bitcoin brokerage and bank for long-term investors, operating under NMLS ID #1906809. Customers can buy, sell, send, and receive bitcoin, get paid in bitcoin via direct deposit, and earn interest on cash balances paid in bitcoin. River holds 100% of customer bitcoin in full-reserve multisig cold storage, publishes monthly third-party Proof of Reserves attestations, and provides FDIC insurance on cash up to $250,000 through partner bank Lead Bank. River exposes a GraphQL data API at https://river.com/api secured by an OAuth 2.0 authorization-code + PKCE flow with OpenID Connect discovery (balances, transactions, identity, and payment network read scopes). Surfaced as a polychain portfolio company and enriched from River's public well-known, OIDC, and security surfaces.

River Financial is listed with 1 API on the APIs.io network. Tagged areas include Company, Bitcoin Services, Cryptocurrency, Financial Services, and Banking.

River Financial’s developer surface includes support, signup flow, authentication, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

28.2/100 thin ▬ flat Agent 11/100 agent aware Front door AI 1/6 silent Heartbeat 78/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

CompanyBitcoin ServicesCryptocurrency Financial Services Banking OAuth Authentication

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 28.2/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 2.8 / 17

Access Clarity 7.2 / 17

Operational Transparency 3.2 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 6.3 / 15

Agent readiness — 11/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 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 6 / 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

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Banking & Open Finance 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/river-financial/"><img src="https://apis.io/badge/river-financial/card.svg" alt="River Financial 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

11 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 16.7 — up to +16.7 composite points
Access Clarity scores 42.1 — up to +11.6 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/river-financial/apis.yml: open an issue on github.com/api-evangelist/river-financial 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 →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OAuth

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

River API

River's GraphQL data API secured with OAuth 2.0 authorization-code + PKCE and OpenID Connect. Read scopes cover account balances, transactions, identity, and payment networks.

Security Posture 3

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

River Financial Authentication

oauth2/openIdConnect · 2 schemes

SECURITY

River Financial Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

River Financial Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

River Financial Scopes

6 scopes · authorizationCode

6 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Conformance

Conformance

Lifecycle

Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 7

Authentication, authorization, and security posture

Compliance

Security

SecurityTxt

Authentication

OAuthScopes

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Scroll for all 7

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: river-financial
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - 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
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/river-financial.png
name: River Financial
description: 'River Financial Inc. (river.com) is a regulated U.S.-based Bitcoin brokerage and bank for long-term investors,
  operating under NMLS ID #1906809. Customers can buy, sell, send, and receive bitcoin, get paid in bitcoin via direct deposit,
  and earn interest on cash balances paid in bitcoin. River holds 100% of customer bitcoin in full-reserve multisig cold storage,
  publishes monthly third-party Proof of Reserves attestations, and provides FDIC insurance on cash up to $250,000 through
  partner bank Lead Bank. River exposes a GraphQL data API at https://river.com/api secured by an OAuth 2.0 authorization-code
  + PKCE flow with OpenID Connect discovery (balances, transactions, identity, and payment network read scopes). Surfaced
  as a polychain portfolio company and enriched from River''s public well-known, OIDC, and security surfaces.'
url: https://raw.githubusercontent.com/api-evangelist/river-financial/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- polychain
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Bitcoin Services
- Cryptocurrency
- Financial Services
- Banking
- OAuth
- Authentication
tags_raw:
- Company
- Bitcoin Services
- Cryptocurrency
- Financial Services
- Banking
- OAuth
- API
- Financial-Services
- Authentication
apis:
- name: River API
  description: River's GraphQL data API secured with OAuth 2.0 authorization-code + PKCE and OpenID Connect. Read scopes cover
    account balances, transactions, identity, and payment networks.
  humanURL: https://river.com
  baseURL: https://river.com/api
  properties:
  - type: Authentication
    url: authentication/river-financial-authentication.yml
  - type: OAuthScopes
    url: scopes/river-financial-scopes.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: X-MCPServerCandidate
  url: mcp/river-financial-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: Website
  url: https://river.com
- type: Support
  url: https://river.com/support
- type: SignUp
  url: https://river.com/signup
- type: TermsOfService
  url: https://river.com/legal/terms
- type: PrivacyPolicy
  url: https://river.com/legal/privacy
- type: GitHubOrganization
  url: https://github.com/riverfinancial
- type: StatusPage
  url: https://status.river.com
- type: Compliance
  url: https://river.com/security
- type: Security
  url: https://river.com/.well-known/security.txt
- type: SecurityTxt
  url: well-known/river-financial-security.txt
- type: WellKnown
  url: well-known/river-financial-well-known.yml
- type: Authentication
  url: authentication/river-financial-authentication.yml
- type: OAuthScopes
  url: scopes/river-financial-scopes.yml
- type: Conventions
  url: conventions/river-financial-conventions.yml
- type: Conformance
  url: conformance/river-financial-conformance.yml
- type: Lifecycle
  url: lifecycle/river-financial-lifecycle.yml
- type: DomainSecurity
  url: security/river-financial-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/river-financial-vulnerability-disclosure.yml
- type: LLMsTxt
  url: llms/river-financial-llms.txt
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 13
  pass: local-v1

River Financial API — frequently asked questions

Does River Financial have an API?

Yes. APIs.io lists 1 API from River Financial, including River API.

How do I authenticate with the River Financial API?

River Financial documents its authentication (oauth2/openIdConnect · 2 schemes). The details are profiled on APIs.io as River Financial Authentication.

Is the River Financial API ready for AI agents?

River Financial has a Kin Score of 28.2 out of 100 (thin) and an Agent Readiness score of 10.8 (agent-aware), scored by API Evangelist on 2026-11-06.

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/river-financial"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/river-financial/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.