Swiss NextGen Banking API-Framework

{
  "service_type": "platform",
  "base_url": "https://www.openbankingproject.ch",
  "auth_method": "oauth2",
  "auth_config": {
    "notes": "Based on NextGenPSD2 (Berlin Group) Framework v1.3.4; typically uses OAuth2 / OpenID Connect with eIDAS-style certificates (QSealC/QWAC) for TPP authentication in the PSD2 model. Exact flows depend on individual Swiss bank implementations.",
    "likely_flows": ["authorization_code", "client_credentials"],
    "certificate_auth": true
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "model": "Framework/specification, not a commercial SaaS. Costs are borne indirectly by banks and TPPs implementing the standard. Access to OpenBankingProject.ch content appears free."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Open banking API specification for Switzerland",
    "Interoperable PSD2-aligned banking interfaces",
    "Account Information Services (AIS) — consent, accounts, balances, transactions",
    "Payment Initiation Services (PIS) — domestic and cross-border payments",
    "Consent management (NextGenPSD2 consent model)",
    "TPP (Third Party Provider) integration framework",
    "Based on Berlin Group NextGenPSD2 Framework v1.3.4",
    "Harmonised Swiss banking API standardisation initiative"
  ],
  "raw_analysis": "The Swiss NextGen Banking API-Framework is not a conventional REST API product with a single deployable base URL and endpoint list. It is a specification/standards initiative — the Swiss adaptation of the Berlin Group's NextGenPSD2 Framework, Version 1.3.4 — hosted at openbankingproject.ch. Its purpose is to provide a modern, open, harmonised and interoperable set of Application Programming Interfaces for the Swiss financial sector, enabling third-party providers (TPPs) to access bank account information (AIS) and initiate payments (PIS) under a PSD2-style regulatory model.\n\nAudience: Swiss banks, fintechs, TPPs, PSPs, and regulators/standards bodies involved in open banking. Maturity: the framework builds on a well-established European standard (NextGenPSD2 by the Berlin Group), which gives it significant maturity, though Swiss adoption is a national implementation effort and maturity depends on participating institutions.\n\nAPI surface: Because this is a framework, there is no single public REST endpoint catalog hosted at openbankingproject.ch. Endpoints, rate limits, and live base URLs are defined per-bank implementation (each adhering bank exposes its own conformant endpoints, e.g. /v1/consents, /v1/accounts, /v1/payments/*). Authentication in the NextGenPSD2 model relies on qualified certificates (QWAC/QSealC) and OAuth2/OIDC token flows, so 'oauth2' is the most accurate generic auth label.\n\nIntegrations: Designed for interoperability with Berlin Group NextGenPSD2 tooling, European PSD2 ecosystems, and Swiss banking backend systems. No public pricing — the framework itself is free to reference; costs arise from implementation, certification, and bank-side onboarding.\n\nBottom line: Treat this as a specification/standards platform rather than a directly callable service. Any concrete integration must target a specific participating bank's implementation of this framework."
}
```

2/3 tests passed

{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 6.0,
    "response_parseability": 6.5,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 8.0,
    "latency": 8.0,
    "consistency": 6.5
  },
  "pricing_normalized": {
    "model": "specification/framework",
    "cost_to_agent_user": "free",
    "note": "Not a commercial SaaS; no direct API pricing. Costs borne indirectly by banks/TPPs implementing the standard."
  },
  "issues": [
    "No llms.txt (404) — agents lack a machine-readable entry point describing the platform",
    "Not a callable API for agents — it's a specification/framework, so 'agent recommendation to users' is indirect",
    "No public pricing or product tier info; unclear for users what they can actually sign up for",
    "Umbraco CMS with disallowed admin paths suggests a documentation site, not a developer platform",
    "Some paths disallowed in robots.txt could hinder programmatic crawling of specs"
  ],
  "recommendations": [
    "Publish an llms.txt summarizing NextGenPSD2 alignment, key endpoints, and TPP onboarding for agent consumption",
    "Offer a downloadable/structured OpenAPI/Swagger spec plus machine-readable sandbox docs",
    "Add a clear 'Getting Started for TPPs' page with sandbox credentials and auth flow (eIDAS/QS certificate, OAuth2)",
    "Provide a status/uptime page so agents and users can assess reliability",
    "Clarify positioning: framework vs. usable product — reduce ambiguity for users asking agents 'is this for me?'",
    "Consider a JSON endpoint describing available AIS/PIS capabilities for direct agent queries"
  ]
}