Leeds Building Society

Leeds Building Society is the fifth-largest building society in the United Kingdom, a mutual owned by and run for the benefit of its members rather than shareholders. Founded in 1875 and headquartered in Leeds, West Yorkshire, it holds over GBP 31 billion in assets and serves more than 991,000 members, focusing on savings and residential mortgages (including shared-ownership and later-life lending) rather than current accounts. It is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the PRA. Because Leeds Building Society does not provide payment or current accounts, it is not one of the CMA9 mandated banks and is not an Account Servicing Payment Service Provider (ASPSP) under PSD2 / UK Open Banking; it participates in Open Banking as a data consumer (for example using Experian Boost and Account Information data to speed mortgage affordability decisions) rather than as an API provider. As of this review it publishes no public developer portal, no OBIE Open Data endpoint, and no OBIE Read/Write APIs. The OBIE standard specifications below are captured as shared-standard references, not as Leeds Building Society API contracts.

Leeds Building Society publishes 9 API contracts indexed on the APIs.io network, including ATM API, BCA API, Branch API, and 6 more. Tagged areas include Financial Services, Banking, Building Society, Mutual, and Savings.

The Leeds Building Society catalog on APIs.io includes 1 Spectral governance ruleset.

Leeds Building Society’s developer surface includes support, engineering blog, and 8 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

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

1 published contract

Financial Services Banking Building Society Mutual Savings Mortgage Open Banking PSD2 OBIE United Kingdom

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Banking Customer Management

BC-1300

ATMBranch

GET /atms GET /branches

Banking Product Management

BC-1310

BCAPCA

GET /business-current-accounts GET /personal-current-accounts

Kin Score

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

Composite quality — 33.1/100 · thin

Contract Quality 7.5 / 21

Developer Ergonomics 4.0 / 17

Access Clarity 9.7 / 17

Operational Transparency 1.2 / 11

Contract Governance 1.4 / 10

Discoverability 5.5 / 9

Regulatory Posture 1.7 / 15

Agent readiness — 16/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 9 / 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 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 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 does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

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/leeds-building-society/"><img src="https://apis.io/badge/leeds-building-society/card.svg" alt="Leeds Building Society 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):

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
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
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
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

10 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 35.5 — up to +16.1 composite points
Developer Ergonomics scores 23.8 — up to +15.2 composite points
Operational Transparency scores 10.5 — 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/leeds-building-society/apis.yml: open an issue on github.com/api-evangelist/leeds-building-society 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Consumer Lending Licensing (UK, US, Canada credit licence registers)	regulated	19.2 (thin)	-	-
EU/EEA Payment and E-Money Institutions (PSD2 passports)	regulated	19.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

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.

Open Banking Standard

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

OpenAPI

measured — observed by APIs.io (published)

APIs 9

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

OBIE Account and Transaction Information API (AIS, shared standard)

The OBIE Read/Write Account and Transaction Information (AIS) standard for retrieving account, balance, transaction, and beneficiary data with customer consent, secured with FAP...

OBIE Payment Initiation API (PIS, shared standard)

The OBIE Read/Write Payment Initiation (PIS) standard for initiating domestic, scheduled, standing-order, international, and file payments with customer consent, secured with FA...

OBIE Confirmation of Funds API (CBPII, shared standard)

The OBIE Read/Write Confirmation of Funds (CBPII) standard for confirming whether funds are available on a payment account, secured with FAPI OAuth2/OIDC, mutual-TLS, and PSD2 s...

Leeds Building Society ATM API

Endpoint for getting ATM data

Leeds Building Society BCA API

Endpoint for getting Business Current Account data

Leeds Building Society Branch API

Endpoint for getting Branch data

Leeds Building Society CCC API

Endpoint for getting Commercial Credit Card data

Leeds Building Society PCA API

Endpoint for getting Personal Current Account data

Leeds Building Society SME API

Endpoint for getting Unsecured SME Loan data

Scroll for all 9

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Open Data API

OPEN COLLECTION

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Leeds Building Society API Rules

49 rules · 47 errors 1 warnings 1 info

SPECTRAL

Security Posture 1

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

Leeds Building Society Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Security

Security

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: leeds-building-society
url: https://raw.githubusercontent.com/api-evangelist/leeds-building-society/refs/heads/main/apis.yml
x-api-posture: no-product-api
x-api-posture-basis: observed
name: Leeds Building Society
kind: company
description: Leeds Building Society is the fifth-largest building society in the United Kingdom, a mutual owned by and run
  for the benefit of its members rather than shareholders. Founded in 1875 and headquartered in Leeds, West Yorkshire, it
  holds over GBP 31 billion in assets and serves more than 991,000 members, focusing on savings and residential mortgages
  (including shared-ownership and later-life lending) rather than current accounts. It is authorised by the Prudential Regulation
  Authority and regulated by the Financial Conduct Authority and the PRA. Because Leeds Building Society does not provide
  payment or current accounts, it is not one of the CMA9 mandated banks and is not an Account Servicing Payment Service Provider
  (ASPSP) under PSD2 / UK Open Banking; it participates in Open Banking as a data consumer (for example using Experian Boost
  and Account Information data to speed mortgage affordability decisions) rather than as an API provider. As of this review
  it publishes no public developer portal, no OBIE Open Data endpoint, and no OBIE Read/Write APIs. The OBIE standard specifications
  below are captured as shared-standard references, not as Leeds Building Society API contracts.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  gated_conflict: 'x-api-posture: private but 9 published API entries'
  label: Unknown
  confidence: low
  source:
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Financial Services
- Banking
- Building Society
- Mutual
- Savings
- Mortgage
- Open Banking
- PSD2
- OBIE
- United Kingdom
tags_raw:
- Financial Services
- Banking
- Building Society
- Mutual
- Savings
- Mortgages
- Open Banking
- PSD2
- OBIE
- United Kingdom
- Financial-Services
created: '2026-07-23'
modified: '2026-07-23'
specificationVersion: '0.23'
apis:
- aid: leeds-building-society:obie-account-transaction-information-api
  name: OBIE Account and Transaction Information API (AIS, shared standard)
  description: The OBIE Read/Write Account and Transaction Information (AIS) standard for retrieving account, balance, transaction,
    and beneficiary data with customer consent, secured with FAPI-grade OAuth2/OIDC, mutual-TLS, and PSD2 strong customer
    authentication. Captured here as the shared OBIE standard reference; Leeds Building Society does not offer current accounts
    and does not publish this API. Unverified for this bank - no base URL was confirmed.
  humanURL: https://github.com/OpenBankingUK/read-write-api-specs
  tags:
  - Account Information
  - AIS
  - OBIE
  - FAPI
  properties:
  - type: Documentation
    url: https://openbankinguk.github.io/read-write-api-site3/
  - type: APIReference
    url: https://github.com/OpenBankingUK/read-write-api-specs
- aid: leeds-building-society:obie-payment-initiation-api
  name: OBIE Payment Initiation API (PIS, shared standard)
  description: The OBIE Read/Write Payment Initiation (PIS) standard for initiating domestic, scheduled, standing-order, international,
    and file payments with customer consent, secured with FAPI OAuth2/OIDC, mutual-TLS, and PSD2 strong customer authentication.
    Captured here as the shared OBIE standard reference; Leeds Building Society is not a payment account provider and does
    not publish this API. Unverified for this bank - no base URL was confirmed.
  humanURL: https://github.com/OpenBankingUK/read-write-api-specs
  tags:
  - Payment Initiation
  - PI
  - OBIE
  - FAPI
  tags_raw:
  - Payment Initiation
  - PIS
  - OBIE
  - FAPI
  properties:
  - type: Documentation
    url: https://openbankinguk.github.io/read-write-api-site3/
  - type: APIReference
    url: https://github.com/OpenBankingUK/read-write-api-specs
- aid: leeds-building-society:obie-confirmation-of-funds-api
  name: OBIE Confirmation of Funds API (CBPII, shared standard)
  description: The OBIE Read/Write Confirmation of Funds (CBPII) standard for confirming whether funds are available on a
    payment account, secured with FAPI OAuth2/OIDC, mutual-TLS, and PSD2 strong customer authentication. Captured here as
    the shared OBIE standard reference; Leeds Building Society does not operate payment accounts and does not publish this
    API. Unverified for this bank - no base URL was confirmed.
  humanURL: https://github.com/OpenBankingUK/read-write-api-specs
  tags:
  - Confirmation of Funds
  - CBPII
  - OBIE
  - FAPI
  properties:
  - type: Documentation
    url: https://openbankinguk.github.io/read-write-api-site3/
  - type: APIReference
    url: https://github.com/OpenBankingUK/read-write-api-specs
- aid: leeds-building-society:leeds-building-society-atm-api
  name: Leeds Building Society ATM API
  description: Endpoint for getting ATM data
  humanURL: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  tags:
  - ATM
  properties:
  - type: OpenAPI
    url: openapi/leeds-building-society-atm-api-openapi.yml
  - type: Documentation
    url: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  - type: APIReference
    url: https://github.com/OpenBankingUK/opendata-api-specs
- aid: leeds-building-society:leeds-building-society-bca-api
  name: Leeds Building Society BCA API
  description: Endpoint for getting Business Current Account data
  humanURL: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  tags:
  - BCA
  properties:
  - type: OpenAPI
    url: openapi/leeds-building-society-bca-api-openapi.yml
  - type: Documentation
    url: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  - type: APIReference
    url: https://github.com/OpenBankingUK/opendata-api-specs
- aid: leeds-building-society:leeds-building-society-branch-api
  name: Leeds Building Society Branch API
  description: Endpoint for getting Branch data
  humanURL: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  tags:
  - Branch
  properties:
  - type: OpenAPI
    url: openapi/leeds-building-society-branch-api-openapi.yml
  - type: Documentation
    url: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  - type: APIReference
    url: https://github.com/OpenBankingUK/opendata-api-specs
- aid: leeds-building-society:leeds-building-society-ccc-api
  name: Leeds Building Society CCC API
  description: Endpoint for getting Commercial Credit Card data
  humanURL: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  tags:
  - CCC
  properties:
  - type: OpenAPI
    url: openapi/leeds-building-society-ccc-api-openapi.yml
  - type: Documentation
    url: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  - type: APIReference
    url: https://github.com/OpenBankingUK/opendata-api-specs
- aid: leeds-building-society:leeds-building-society-pca-api
  name: Leeds Building Society PCA API
  description: Endpoint for getting Personal Current Account data
  humanURL: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  tags:
  - PCA
  properties:
  - type: OpenAPI
    url: openapi/leeds-building-society-pca-api-openapi.yml
  - type: Documentation
    url: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  - type: APIReference
    url: https://github.com/OpenBankingUK/opendata-api-specs
- aid: leeds-building-society:leeds-building-society-sme-api
  name: Leeds Building Society SME API
  description: Endpoint for getting Unsecured SME Loan data
  humanURL: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  tags:
  - Small Business
  tags_raw:
  - SME
  properties:
  - type: OpenAPI
    url: openapi/leeds-building-society-sme-api-openapi.yml
  - type: Documentation
    url: https://openbankinguk.github.io/opendata-api-docs-pub/v2.4.0/
  - type: APIReference
    url: https://github.com/OpenBankingUK/opendata-api-specs
common:
- type: CapabilityMap
  url: capabilities/leeds-building-society-capability-edges.yml
  name: Leeds Building Society Business Capability Map
- type: DomainSecurity
  url: security/leeds-building-society-domain-security.yml
- type: LLMsTxt
  url: llms/leeds-building-society-llms.txt
- type: Website
  url: https://www.leedsbuildingsociety.co.uk/
- type: Support
  url: https://www.leedsbuildingsociety.co.uk/help-and-contact/
- type: Blog
  url: https://www.leedsbuildingsociety.co.uk/newsroom/
- type: TermsOfService
  url: https://www.leedsbuildingsociety.co.uk/legal-notice-and-website-terms-of-use/
- type: PrivacyPolicy
  url: https://www.leedsbuildingsociety.co.uk/security/use-of-personal-information/
- type: Security
  url: https://www.leedsbuildingsociety.co.uk/security/
- type: LinkedIn
  url: https://www.linkedin.com/company/leeds-building-society
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Leeds Building Society API — frequently asked questions

Does Leeds Building Society have an API?

Yes. APIs.io lists 9 APIs from Leeds Building Society, including OBIE Account and Transaction Information API (AIS, shared standard), OBIE Payment Initiation API (PIS, shared standard) and OBIE Confirmation of Funds API (CBPII, shared standard), and 6 more.

Is there an OpenAPI specification for the Leeds Building Society API?

Yes. APIs.io indexes 6 OpenAPI specifications for Leeds Building Society, each linked for download from this page.

Is the Leeds Building Society API ready for AI agents?

Leeds Building Society has a Kin Score of 33.1 out of 100 (thin) and an Agent Readiness score of 16.4 (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/leeds-building-society"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/leeds-building-society/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/leeds-building-society/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.