Bridgewater Bank
Bridgewater Bank is a Canadian Schedule I chartered bank, a wholly-owned subsidiary of the Alberta Motor Association (AMA), headquartered in Calgary, Alberta and established in 1997. It is a member of the Canada Deposit Insurance Corporation (CDIC) and operates a broker-distributed, deposit-and-lending model rather than a direct-to-consumer retail branch network — residential mortgages, Guaranteed Investment Certificates (GICs), and high-interest savings accounts sold through a select network of trusted mortgage and deposit brokers, with roughly $3.3 billion in mortgages and deposits across approximately 53,000 customer accounts nationwide. Bridgewater Bank exposes NO public first-party developer API or developer portal. Its only dedicated digital surface beyond the corporate site is a partner-gated broker information portal (bwbbrokerinfo.ca). Canada's Consumer-Driven Banking (open-banking) framework is legislated but not yet operational, so any consumer data access from a bank of this size is voluntary and today would be aggregator/screen-scraping based rather than through a documented first-party API. No Interac, Real-Time Rail (RTR), FDX, or consumer-driven-banking API participation is publicly documented by the institution.
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 Bridgewater Bank the way a machine reads it — 1 machine-readable artifact, 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 — Bridgewater Bank scores 16.1/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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 Bridgewater Bank
Each block below is one kind of artifact we hold for Bridgewater Bank. 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.
Security Posture 1
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 Bridgewater Bank — 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 1
Portal, sign-up, and the first successful call
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/bridgewater-bank · machine-readable index on apis.io