bunq API

{
  "service_type": "platform",
  "base_url": "https://public-api.bunq.com",
  "auth_method": "api_key",
  "auth_config": {
    "notes": "bunq uses API keys created in the bunq app, combined with device registration and session tokens. Requests are signed with an RSA key pair registered during installation. Sandbox base URL: https://public-api.sandbox.bunq.com"
  },
  "endpoints": [],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "note": "API access requires a bunq account; bunq is a paid neobank with subscription plans. Sandbox is free for developers."
    }
  },
  "rate_limits": {
    "note": "bunq enforces rate limits per API key/session; specifics are documented at https://doc.bunq.com"
  },
  "capabilities": [
    "Open banking / neobank API",
    "Monetary account management (balances, IBANs)",
    "Payments and transfers (SEPА, international)",
    "Payment requests and drafts",
    "Card management (order, freeze, details)",
    "User and session management",
    "Webhooks / callbacks",
    "Sandbox environment for testing",
    "OAuth support for third-party access"
  ],
  "raw_analysis": "bunq is a European (Dutch) neobank offering a public REST API aimed at developers, fintechs, and businesses that want programmatic access to banking features. The API allows managing monetary accounts, payments, cards, payment requests, and user sessions, and includes a sandbox for testing. Authentication is non-trivial: it involves creating an API key in the bunq app, registering a device with an RSA key pair, and establishing a session; requests must be signed. The developer portal is at bunq.com/developer, with documentation migrated to beta.doc.bunq.com. The service is mature (bunq founded 2012, API available for years) but the API is only usable with a bunq account. The sandbox base URL has been updated to https://public-api.sandbox.bunq.com, and production is https://public-api.bunq.com. There is no public REST API for non-bunq users; the platform is a banking platform with a developer API rather than a generic collaboration tool. Integration ecosystem includes OAuth for third-party apps and webhooks for event notifications. No public endpoint list is provided in the snippet; endpoints must be retrieved from the official documentation."
}

0/3 tests passed

{
  "overall": 68,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 5.5,
    "response_parseability": 9.0,
    "error_clarity": 7.0,
    "doc_quality": 7.5,
    "auth_simplicity": 4.5,
    "latency": 5.0,
    "consistency": 5.0
  },
  "pricing_normalized": {
    "model": "subscription",
    "note": "API requires a paid bunq account; sandbox is free for developers.",
    "barrier": "medium",
    "value_prop": "Full neobank + open banking API (accounts, IBANs, SEPA/intl payments, cards, webhooks) with a free sandbox."
  },
  "issues": [
    "Auth is gated behind a bunq account/subscription — not a simple magic-link or agent-onboardable flow; significant friction for trial.",
    "Automated checks failed with DNS resolution errors (Name or service not known) for website_uptime, robots_txt, and llms_txt — no status page, robots, or llms.txt confirmed reachable.",
    "No API key / developer quickstart confirmed without signup; onboarding likely multi-step (account -> API key -> device registration).",
    "Region/governance constraints on payments (EU PSD2 context) may limit availability for some users."
  ],
  "recommendations": [
    "Provide a self-serve sandbox quickstart with an instant API key and sample requests (curl) — lowers first_try_success dramatically.",
    "Add llms.txt / a machine-readable API spec (OpenAPI) and a public status page to improve parseability and consistency signals.",
    "Document signed-request / device-registration requirements clearly up front to reduce auth friction errors.",
    "Publish an agent-friendly auth path (e.g., OAuth with sandbox demo credentials) so agents can demo value without a paid plan.",
    "Ensure DNS/hostnames for docs, status, and robots endpoints are stable and resolvable to avoid failed automated checks."
  ]
}