Financial Modeling Prep review

Financial Modeling Prep is a hosted financial-data service with a website for looking up information and an API for integrating structured data into applications. It is not presented as a self-hosted server, a local database, a library or a CLI. FMP collects financial information from global markets and makes it available through its site and developer delivery options.

In a typical stack, FMP sits upstream of a research tool, financial app, dashboard or internal data pipeline. Its catalog includes quotes and historical prices, financial statements, analyst estimates, earnings transcripts, news, calendars and ownership records. The homepage lists more than 100 endpoints and delivery through API, WebSocket and bulk downloads in JSON or CSV. The stated coverage includes stocks, ETFs, funds, indexes, forex, crypto and commodities. That can reduce the number of separate sources an application needs to integrate, but teams still need to map FMP fields to their own data model and confirm that the required instruments and endpoints are covered.

FMP provides more than 100 API endpoints, alongside WebSocket and bulk-download delivery. The homepage lists JSON and CSV as supported formats and points developers to API documentation. Its endpoint categories include real-time and historical market data, financial statements, company profiles, search and directories, calendars, news, economics, analyst estimates and ownership data.

The homepage describes integration with any programming language, but does not name specific languages, SDKs or a CLI. Confirm SDK support and the exact authentication, pagination, error-handling and endpoint details in FMP's documentation before choosing a client library or building a production integration. Bulk APIs are an option for pulling larger datasets rather than making individual requests, while WebSocket delivery is listed for streaming data. The site also describes custom endpoints and delivery for Enterprise customers. FMP's delivery options give developers several ways to fit data into an application, but the integration work still depends on validating the endpoint schema and coverage against the product's requirements.

The free Basic plan includes 250 calls per day, end-of-day historical data, a five-year historical range and 500MB of trailing 30-day bandwidth. It is suited to exploring endpoints, not a high-volume production feed. Starter costs $29 monthly or $19 per month with annual billing; it lists 300 calls per minute, up to five years of historical data, US coverage and 20GB of trailing 30-day bandwidth.

Premium is $69 monthly or $49 per month with annual billing. It lists 750 calls per minute, 30-plus years of historical data, UK and Canada coverage and 50GB of bandwidth. Ultimate is $139 monthly or $99 per month with annual billing, with 3,000 calls per minute, full historical access, global coverage and 150GB of bandwidth. The pricing page lists no add-ons or overage rates. It also does not say whether excess calls or bandwidth are billed, blocked or handled another way. Ask FMP how those limits are enforced before sizing a production workload.

FMP is described as a hosted website and data service, with no self-hosting option or open-source licence published. Treat the data service as an external dependency unless FMP confirms otherwise. The vendor lists bulk downloads and API delivery in JSON and CSV, which gives teams formats they can ingest into their own storage and use when changing providers.

That does not make migration automatic. Applications may depend on FMP-specific endpoint paths, field names, historical coverage and access tiers. Keep a provider-neutral internal schema, retain the data your use case permits, and compare replacement-provider coverage before switching. FMP's published materials here do not establish export rights, retention terms or a migration service; ask the vendor about those points, along with the applicable data-use terms, before building a durable data warehouse around its feed.

Plan around the limits attached to the selected tier: call rates, historical access, market coverage and trailing 30-day bandwidth. The Basic plan is capped at 250 calls per day and provides end-of-day historical data; paid tiers list calls per minute and different coverage. The pricing page does not publish overage rates or explain what happens when a limit is reached, so confirm enforcement and failure behavior with FMP.

Reddit reports raise data-quality and continuity questions. One r/algotrading post says a paid Starter user lost access to a shares-float endpoint for NSE stocks without notice; a separate r/WarrenBuffett post describes recurring missing or incorrect data. These are individual reports, not service-wide measurements, but they make endpoint-level monitoring and fallback planning sensible. Before depending on FMP, check the required symbols and fields, monitor freshness and response errors, and ask the vendor about support, uptime commitments, security controls and compliance documentation. The homepage does not list those production commitments.