nFusion Solutions Market Data API

{
  "service_type": "platform",
  "base_url": "https://nfusionsolutions.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "No public pricing page. The provided URL redirects to a contact page, suggesting enterprise/contact-sales pricing model."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "REST API for financial market data",
    "Real-time financial data feeds",
    "Historical financial data feeds",
    "Enterprise-grade data delivery",
    "Cryptocurrency and traditional market data (inferred from typical offerings)"
  ],
  "raw_analysis": "nFusion Solutions is a financial data provider offering REST APIs for enterprise-grade market data, including real-time and historical datasets. The service appears targeted at enterprise customers, financial institutions, trading platforms, and fintech developers who require reliable, low-latency financial data. \n\nThe provided URL (https://nfusionsolutions.com/contact-us) is a marketing/contact page rather than a developer documentation or API reference page. This strongly indicates the platform uses a sales-led onboarding model, typical of enterprise data vendors: prospective customers must contact sales to obtain API keys, pricing, and documentation. There is no publicly available developer portal, OpenAPI spec, or sign-up flow evident.\n\nAuthentication method is not publicly documented but is likely API key or token-based, issued through a sales/onboarding process. Rate limits, endpoint specifics, and detailed data coverage are not exposed publicly. Pricing is almost certainly custom/enterprise, requiring direct engagement with the vendor.\n\nGiven the lack of public technical documentation, this service is more of a commercial data vendor than a self-serve developer platform. Integration capability exists (REST APIs are advertised), but actual developer experience cannot be evaluated without contacting the vendor."
}

3/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 4.0,
    "response_parseability": 6.0,
    "error_clarity": 4.0,
    "doc_quality": 5.0,
    "auth_simplicity": 5.0,
    "latency": 9.0,
    "consistency": 5.0
  },
  "pricing_normalized": {
    "model": "contact_sales",
    "transparency": 2.0,
    "notes": "No public pricing page; URL redirects to a contact page suggesting enterprise/quote-based pricing."
  },
  "issues": [
    "No public pricing — enterprise contact-sales model creates high friction for agents recommending to users",
    "Missing security headers on all responses (uptime, robots.txt, llms.txt)",
    "Auth/onboarding path unclear; no documented self-serve signup or API key flow visible",
    "Documentation for API limits, errors, and rate limits not surfaced in provided data",
    "Positioned as bullion/precious-metals business software rather than a clean developer-focused API platform"
  ],
  "recommendations": [
    "Publish a public pricing page or tiered plans so agents can give users a concrete cost answer",
    "Add a self-serve developer signup with magic-link or OAuth to reduce onboarding friction",
    "Expose OpenAPI/Swagger spec and a machine-readable endpoint catalog for structured agent consumption",
    "Document rate limits, error codes, and data coverage clearly to improve error clarity and first-try success",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) to increase perceived reliability",
    "Maintain a public status page for uptime transparency to boost consistency score"
  ]
}