Wealth Reader API

{
  "service_type": "platform",
  "base_url": "https://wealthreader.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "Aggregation of wealth and asset information beyond PSD2-regulated bank account data",
    "Access to non-bank financial sources (e.g., investment funds, pensions, real estate, alternative assets)",
    "Financial data enrichment and consolidation",
    "Likely developer API for integrating wealth data into apps (Spanish market focus)"
  ],
  "raw_analysis": "Wealth Reader (wealthreader.com) appears to be a Spanish fintech platform positioned as an extension of PSD2-based open banking data aggregation. The description highlights a gap in regulatory APIs: PSD2 grants access to bank account balances and transactions, but does not cover broader wealth/patrimonial information such as investment portfolios, pension plans, real estate, or other assets. Wealth Reader appears to bridge this gap by aggregating wealth data from sources beyond standard PSD2 bank APIs. The service is listed under the 'api' category, suggesting it offers an API for developers, likely targeting banks, wealth managers, robo-advisors, and financial planning apps in Spain and possibly broader Europe. Maturity is unclear: no public documentation, endpoint list, auth details, or pricing information is visible from the provided content. The platform's value proposition is proprietary wealth aggregation, so authentication is likely API key or OAuth-based but this cannot be confirmed. No public REST API endpoints are documented here, and rate limits are unknown. Overall: an emerging fintech data aggregator with a clear niche (non-PSD2 wealth data) but limited public developer information available from the scrape."
}

2/3 tests passed

{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 5.0,
    "response_parseability": 6.0,
    "error_clarity": 5.0,
    "doc_quality": 4.0,
    "auth_simplicity": 4.0,
    "latency": 6.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "transparency": "none",
    "note": "No pricing information exposed on public pages; requires sales contact likely"
  },
  "issues": [
    "No llms.txt (404) — agents cannot quickly ingest platform capabilities",
    "No security headers detected (HSTS, CSP, X-Frame-Options missing) — weak trust signal",
    "Website latency ~705ms for main page — acceptable but not fast",
    "No publicly visible pricing model or tiers",
    "Spain/PSD2-focus may limit usefulness for global agent recommendations",
    "Auth not documented in accessible surface — likely enterprise/B2B sales flow",
    "Value prop is niche (wealth data aggregation beyond PSD2) — harder to recommend generically"
  ],
  "recommendations": [
    "Publish an llms.txt summarising capabilities, endpoints, and auth flow for agent consumption",
    "Add standard security headers to increase trust scoring",
    "Expose public pricing or a clear 'contact sales' with tier hints to reduce ambiguity",
    "Provide a quickstart / sandbox with magic-link or 'Sign in with Notlogin' style onboarding to improve first-try success",
    "Add a status page to improve perceived consistency and reliability",
    "Document rate limits, data coverage (which asset classes, countries), and error codes explicitly",
    "Improve homepage TTFB toward <500ms"
  ]
}