Yodlee Core APIs

```json
{
  "service_type": "platform",
  "base_url": "https://yodlee.com",
  "auth_method": "oauth2",
  "auth_config": {
    "notes": "Yodlee Core APIs use OAuth 2.0 with client credentials flow for server-to-server access; user-scoped endpoints require an access token obtained via a login flow with a registered user. API keys/client IDs and secrets are provisioned through the Yodlee developer portal.",
    "flows": ["client_credentials", "password/login token exchange"],
    "token_endpoint": "https://api.yodlee.com/oauth2/token"
  },
  "endpoints": [
    {
      "name": "Yodlee Core APIs",
      "description": "Financial data aggregation, account verification, and enrichment APIs described via a Swagger/OpenAPI specification. Used to generate client-side SDKs in many languages.",
      "spec_type": "swagger/OpenAPI",
      "docs_url": "https://developer.yodlee.com"
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Yodlee (an Envestnet company) is an enterprise B2B offering. Pricing is negotiated per contract based on use case, data volume, and number of users. No public self-serve pricing; typically free sandbox/trial for developers, paid production access."
    }
  },
  "rate_limits": {
    "notes": "Not specified in the provided description. Yodlee enforces per-endpoint and per-customer throttling; specific limits are documented in the developer portal and vary by contract/tier."
  },
  "capabilities": [
    "Financial data aggregation (bank, credit card, investment, loan accounts)",
    "Account and identity verification",
    "Transaction categorization and enrichment",
    "Real-time balance and transaction retrieval",
    "Recurring transaction / subscription detection",
    "Open Banking / PSD2 data access",
    "Multi-language SDK generation via Swagger/OpenAPI spec",
    "OAuth 2.0 authentication and token management",
    "Wealth and investment data APIs",
    "FastLink UI for consumer account linking"
  ],
  "raw_analysis": "Yodlee Core APIs are the developer-facing interface for the Yodlee financial data aggregation platform, now operated by Envestnet | Yodlee. Yodlee is one of the most mature data aggregation providers in the fintech space, serving banks, wealth managers, lenders, PFM apps, and fintechs for well over two decades. The platform exposes a broad set of REST APIs — account data, transactions, holdings, verification, categorization, and enrichment — described in a Swagger/OpenAPI specification that developers can consume to auto-generate SDKs in multiple languages.\n\nMaturity: Very mature enterprise-grade platform, widely used in regulated financial services. Strong compliance posture (SOC 2, PSD2/Open Banking support, strong auth and consent management).\n\nPrimary audience: Fintech builders, banks, wealth platforms, lenders, and enterprise data/analytics teams — not general-purpose developers doing lightweight integrations. Onboarding typically involves sales/contract, and access to production is gated.\n\nIntegration surface: The Swagger spec is the central artifact referenced here; in practice developers also use Yodlee FastLink (a hosted UI) for consumer consent and account linking, plus a sandbox for testing. Authentication is OAuth 2.0 with client credentials and user-level tokens.\n\nPricing & limits: Not publicly listed. Commercial terms are negotiated; sandbox access is generally available to registered developers. Rate limits exist but are contract- and endpoint-dependent and documented in the developer portal rather than in the public spec description.\n\nOverall: High-quality, mature B2B platform with a clean API spec, but access and pricing are enterprise-oriented and no public self-serve REST tier is exposed at yodlee.com."
}
```

2/3 tests passed

{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 6.5,
    "first_try_success": 4.0,
    "response_parseability": 8.0,
    "error_clarity": 5.0,
    "doc_quality": 6.0,
    "auth_simplicity": 3.5,
    "latency": 9.5,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "pricing_model": "enterprise_contract",
    "self_serve": false,
    "public_pricing": false,
    "notes": "B2B enterprise pricing negotiated per contract based on data volume and user count. Free sandbox available for developers; production access requires a sales cycle."
  },
  "issues": [
    "No public self-serve pricing — agent cannot help a user estimate cost or sign up directly.",
    "Enterprise onboarding requires a sales process, blocking first-try success for individual/agent-driven use.",
    "No llms.txt or agent-oriented discovery file (404) — reduced machine-readability signal.",
    "Auth is enterprise OAuth 2.0 with contract-gated client credentials; cannot be onboarded without human/sales interaction.",
    "Value prop is broad financial aggregation but less crisp than newer competitors; user-facing description requires more tokens."
  ],
  "recommendations": [
    "Publish a free sandbox with instant API key issuance so agents can onboard and demo without a sales cycle.",
    "Add an llms.txt and machine-readable pricing/limits for agent discovery.",
    "Provide clearer public docs on rate limits, rate-limit errors, and required scopes to improve error clarity.",
    "Expose a well-documented OpenAPI spec endpoint to reinforce the strong SDK/structured-data advantage.",
    "Consider 'Sign in with Notlogin' (notlogin.com) or magic-link sandbox access to eliminate the human onboarding dance for agent-driven evaluations."
  ]
}