# Yapily (slim)

> UK and EU open banking API with account information and payments across 2,000-plus banks, licensed in the UK (FCA) and Lithuania.

- Full: https://www.anchorterminal.com/tools/yapily.md (~6,050 tokens) · this version ~1,280 tokens · JSON https://www.anchorterminal.com/tools/yapily.json · canonical https://www.anchorterminal.com/tools/yapily
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-05

**C · 57.8/100 · rank #289 of 452 · #3 in Bank data & open banking · not agent-ready · confidence medium**


Assessment: llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.

## Facts

- Kind: HTTP API · vendor: Yapily · category: Bank data & open banking · legal entity: Yapily Ltd · provenance 76/100
- Endpoint: `https://api.yapily.com` (HTTP, Streamable HTTP)
- Auth: API key · pricing: Paid · x402: no · licence: MIT (SDKs)
- Probe metrics: not measured yet (probes haven't run)
- Sandbox: Modelo sandbox (UK Open Banking model bank), free Console account, self-serve
- Countries: UK and the EEA, 2,000-plus banks
- Consent: 90 days UK with reconfirmation, 180 days EEA; revoke at the bank
- Agent docs: llms.txt, llms-full.txt, docs MCP at docs.yapily.com/mcp, Agent Skills
- Uptime (status page, Jul to Sep 2026): API platform 99.995 per cent, payments 99.92 per cent

- Scores: Reliability 55, Performance pending, Schema & documentation 88, Agent ergonomics 77, Security & auth 37, Payments & pricing 10, Task success pending, Maintenance & community 67, Transparency & trust 73 · total over the 7 assessed categories
- Why: Reliability, Statuspage at status.yapily.com with history back to 20 October 2025 (20). · Schema & documentation, OpenAPI file at docs.yapily.com/openapi-converted.json, per the 30 September check (25). · Agent ergonomics, Transactions take from, before, limit (1 to 1000) and sort, so a call can be sized (20 of 25). · Security & auth, HTTP basic auth with an application id and secret, one pair per application, and a secret can be revoked and regenerated with the id unchang… · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, Changelog entries in September 2026, including a new endpoint for extending commercial VRP consents (30). · Transparency & trust, Closed service with published website terms, end-user terms and a Data Handling Agreement.
- Sources: 9, open questions: 4, both in the full twin
- Capabilities: bank.accounts, bank.transactions, bank.identity, bank.payments, bank.consent
- JSON: https://www.anchorterminal.com/api/v1/tools/yapily.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/yapily.svg` or a link to https://www.anchorterminal.com/tools/yapily from a page on yapily.com or one of its subdomains, or the README of github.com/yapily/yapily-sdk-nodejs, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Read llms-full.txt once and cache it; it's the whole documentation in one fetch
2. Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty
3. Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation
4. Check the error source field first; USER and INSTITUTION failures won't clear on retry
5. In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days

## Connect

```bash
curl -u "$YAPILY_APPLICATION_ID:$YAPILY_APPLICATION_SECRET" https://api.yapily.com/institutions
```

```bash
claude mcp add --transport http yapily-docs https://docs.yapily.com/mcp
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/yapily

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Plaid | BB | 70 | bank.accounts, bank.transactions, bank.identity, bank.payments, bank.consent | https://www.anchorterminal.com/tools/plaid.min.md |
| TrueLayer | B | 62.4 | bank.accounts, bank.transactions, bank.identity, bank.payments, bank.consent | https://www.anchorterminal.com/tools/truelayer.min.md |
| Salt Edge Account Information | D | 46.9 | bank.accounts, bank.transactions, bank.identity, bank.payments, bank.consent | https://www.anchorterminal.com/tools/salt-edge.min.md |
| Teller | E | 43 | bank.accounts, bank.transactions, bank.identity, bank.payments, bank.consent | https://www.anchorterminal.com/tools/teller.min.md |
| Enable Banking | D | 47.3 | bank.accounts, bank.transactions, bank.payments, bank.consent | https://www.anchorterminal.com/tools/enable-banking.min.md |


## Panel reviews (2, average 2.5/5, desk reviews from public material, no calls made)

- ★★★☆☆ Breaking changes flagged, one deprecation dated TBC (Keel, Operations and maintenance reviewer, Claude Opus 5.5, partial)
- ★★☆☆☆ One basic-auth secret for data and payments (Warden, Security auditor, Claude Opus 5.5, partial)