Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

zopa

Zopa Bank is a UK FCA-authorised, PRA-regulated digital bank offering flexible savings, personal loans, credit cards, car finance and the Biscuit current account. As a registered Account Servicing Payment Service Provider (ASPSP), Zopa exposes UK Open Banking Read/Write v4.0.0 APIs to authorised Third Party Providers: an Account & Transaction API (AIS) for consent-based access to accounts, balances, transactions, statements, standing orders, direct debits, beneficiaries and party data, and a Payment Initiation API (PIS) for domestic payments and standing orders. Access uses OAuth2 (client-credentials for TPPs, authorization-code for PSUs) over mutual TLS with FAPI headers and JWS request signing. Zopa was surfaced as a portfolio company of Balderton Capital, Bessemer Venture Partners, HV Capital, Northzone, QED Investors and SoftBank Vision Fund.

agent native

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles zopa the way a machine reads it — 18 machine-readable artifacts across 12 APIs, 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 — zopa scores 53.3/100 (developing), with a separate agent-readiness read of 81/100 (agent native). 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 53.3/100 · developing
Contract Quality 14.0 / 25
Developer Ergonomics 11.3 / 20
Commercial Clarity 8.4 / 20
Operational Transparency 1.4 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Regulatory · Banking & Open Finance 15.0 / 15
Agent readiness — 81/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3

How we profile zopa

Each block below is one kind of artifact we hold for zopa. 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 12

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.

zopa Account Access API

The Account Access API from zopa — 2 operation(s) for account access.

zopa Accounts API

The Accounts API from zopa — 2 operation(s) for accounts.

zopa Balances API

The Balances API from zopa — 1 operation(s) for balances.

zopa Beneficiaries API

The Beneficiaries API from zopa — 1 operation(s) for beneficiaries.

zopa Direct Debits API

The Direct Debits API from zopa — 1 operation(s) for direct debits.

zopa Domestic Payments API

The Domestic Payments API from zopa — 5 operation(s) for domestic payments.

zopa Domestic Standing Orders API

The Domestic Standing Orders API from zopa — 4 operation(s) for domestic standing orders.

zopa Offers API

The Offers API from zopa — 1 operation(s) for offers.

zopa Parties API

The Parties API from zopa — 2 operation(s) for parties.

zopa Standing Orders API

The Standing Orders API from zopa — 1 operation(s) for standing orders.

zopa Statements API

The Statements API from zopa — 1 operation(s) for statements.

zopa Transactions API

The Transactions API from zopa — 1 operation(s) for transactions.

Scroll within the panel for all 12 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

zopa-mcp.yml

MCP SERVER

Security Posture 3

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.

Zopa Authentication

oauth2 · 2 schemes

SECURITY

Zopa Domain Security

TLSv1.3 · DMARC

SECURITY

Zopa Vulnerability Disclosure

Intigriti · security.txt · contact published

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Zopa Scopes

2 scopes · clientCredentials/authorizationCode

2 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Zopa Agentic Access

23 operations · 6 acting

23 operations · 6 acting

AGENTIC

Resources

Every other property we hold for zopa — 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 3

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/zopa · machine-readable index on apis.io