Can You Use FMP Data in a Public App, Website, or Client Dashboard?

Yes. FMP data can be used in a public app, website, internal tool, or client dashboard when the agreement covers the intended users, datasets, and method of delivery. Access to an API key and permission to place the resulting data in front of other people are separate matters.

An individual-use plan is intended for one person's own non-business use. A project connected to an employer, client, startup, agency, or other organization may be commercial even while it remains a private prototype. A free public website may still involve data display, while a paid product may also involve redistribution if users can download or retrieve the underlying information.

The useful starting point is not the endpoint. It is a short product review: who is the project for, who will see the output, and what will they be able to do with it? Those answers usually show whether the project remains personal, clearly needs a commercial arrangement, or contains details that FMP must confirm in writing.

This article provides a product-planning framework. FMP's Terms of Service and any signed agreement control the permitted use.

Key Takeaways

• Individual use is narrow. It applies to an individual's own personal, non-business and non-commercial use, not work performed for a company, client, or other third party.
• Private does not always mean personal. A private prototype can still be commercial when it supports an employer, startup, agency, consulting engagement, or client.
• Free does not mean exempt. FMP's published terms address multi-user display whether the application is free or paid and whether it is used internally or externally.
• Display and redistribution are different product features. Showing values or charts, allowing downloads, and providing data through an application or feed should be described separately.
• Real-time and delayed market data may add exchange requirements. Subscriber classification, declarations, agreements, and fees can depend on the exchange and intended use.

Use Three Questions to Classify the Project

1. Who is the project for?

Start with the party that benefits from the work. FMP's personal-use terms apply to an individual using the service for personal, non-business and non-commercial purposes. The same terms define commercial use broadly enough to include association with a business and collecting, aggregating, or analyzing data to support commercial activity.

This means ownership and purpose matter before launch. A developer researching companies for personal use is in a different position from an employee testing a dashboard for a finance team or a consultant preparing a tool for a client. The second and third examples remain connected to a business even if only one person can access the prototype today.

2. Who can access the output?

Next, identify everyone who can see or receive information produced from the API. The list may include employees, clients, customers, subscribers, public visitors, contractors, or users of another application.

FMP's published terms require a specific agreement before its services or data are displayed through websites, blogs, software products, or applications designed for multiple people. The restriction applies to internal and external applications and does not depend on whether users pay for access.

3. What can those users see, retrieve, or export?

Do not stop at the interface label. Record what actually reaches the user: individual values, tables, charts, company profiles, historical series, alerts, rankings, calculated scores, downloadable files, or an API response. A server-side API call can still support public display because the licensing question follows the output delivered to users, not the location of the API key.

FMP's pricing page states that displaying or redistributing FMP-sourced data requires a Data Display and Licensing Agreement. The required scope can depend on whether users only view an output, can export information, or receive data through another service.

Practical Licensing Decision Matrix

The matrix below is a planning tool based on FMP's published terms. It does not replace the agreement that applies to a specific account.

Proposed use	What changes the licensing question	Published terms point to	Action before relying on the data
Personal research in a local notebook	One individual; no business purpose; no sharing or third-party access	Personal use	Stay within the individual plan and its applicable limits
Public portfolio or demonstration site	Other people can see FMP-sourced information, even if the site is free	Data display	Confirm display rights before publishing the data
Private prototype for an employer, startup, agency, or client	The work is associated with a business or supports commercial activity	Commercial use	Arrange an authorized commercial evaluation rather than assuming privacy makes it personal
Internal dashboard used by employees	Multiple people access FMP-sourced information inside an organization	Internal multi-user display	Define the employee population and obtain the appropriate agreement before use
Client dashboard or research portal	A client or other third party can view the output	Commercial display and third-party access	Confirm the users, datasets, display format, and client scope in writing
Public website or mobile app	The public can view FMP-sourced values, charts, tables, or other information	Public data display	Establish a Data Display and Licensing Agreement before launch
SaaS or subscription product	Customers access a commercial product built with FMP data	Commercial use and data display	Confirm licensing, datasets, scale, territory, and delivery method
Download, export, API, or data-feed feature	Users receive data outside the visual interface	Redistribution or third-party access	Specify the fields, formats, frequency, limits, and downstream rights
Scores, rankings, signals, summaries, or alerts	The product shares information calculated from FMP data	Derived information and commercial analysis	Describe both the source data and the resulting output so the agreement addresses the complete workflow

Five Common Shortcuts That Do Not Resolve the Question

The API key stays on the server

Keeping an API key out of browser code is an important security control. It does not decide whether the resulting display is licensed. If a server retrieves an FMP price and sends that price to a public webpage, users still receive FMP-sourced information.

Treat key protection and data rights as separate review items. The first concerns credential security. The second concerns who receives the data and what the agreement permits.

The application is free

The presence or absence of a subscription fee does not determine whether data display occurs. FMP's terms address multi-user display in both complimentary and paid products.

A free stock chart, public company profile, or open website can therefore require a display agreement even when the developer earns no revenue from the page.

The prototype is private

Privacy answers who can access the current environment. It does not answer who the project serves. A prototype built for an employer, client, agency, or startup can fall within commercial use before outside users are invited.

Teams should classify the project by its purpose and sponsoring organization, not only by whether it has reached production.

The product shows calculations instead of raw data

Changing a price series into a return, score, ranking, alert, or summary does not automatically remove the licensing question. FMP's terms address information contained in or derived from its services, while the commercial-use definition includes analysis performed for commercial purposes.

Describe the transformation clearly. FMP needs to know which source fields are used, what the product calculates, whether users can recover the underlying values, and how the output is distributed.

Only one client will use it

A single client is still a third party. The number of client organizations may affect the agreement's scope, but it does not turn a client project into personal use.

For a client dashboard, identify whether the client sees only charts and conclusions, can inspect individual data points, can download results, or can pass the information to additional users.

Display, Redistribution, and Derived Outputs Should Be Scoped Separately

These three terms describe different product behaviors. Separating them makes the licensing conversation faster and reduces the chance that an important feature is omitted.

Display means users can see FMP-sourced information through a website, app, dashboard, report, or other interface. Examples include a quote tile, historical chart, financial statement table, peer comparison, earnings calendar, or company profile.

Redistribution can arise when users receive data beyond viewing it in the interface. Downloads, exports, files, data feeds, API responses, scheduled deliveries, and other transfers should be described explicitly. The format and frequency matter because a single PDF report is not operationally identical to a recurring machine-readable feed.

Derived output is information calculated from FMP data, such as a proprietary score, ranking, signal, alert, screen, or summary. The transformation may add meaningful intellectual work, but the source data and delivery method still need to be covered by the agreement.

One product may involve all three. A screening platform might display company metrics, rank securities using a proprietary model, and allow users to export the results. The licensing review should describe each feature instead of labeling the whole product simply as a dashboard.

Real-Time and Delayed Market Data Add an Exchange Layer

General commercial authorization is not always the final licensing step. Real-time and delayed market data can be governed by exchange rules that classify users and impose separate declarations, agreements, or fees.

FMP explains that users requesting regulated real-time or delayed market data may need to complete a User Declaration Form that identifies the applicable subscriber type. The published categories distinguish non-professional individuals, professional individuals, and business or enterprise subscribers.

This review is dataset-specific. A product using end-of-day fundamentals does not necessarily create the same exchange requirements as a platform displaying real-time quotes. When describing the project, identify the exact datasets, exchanges, update frequency, and whether the information is real-time, delayed, intraday, or end of day.

Prepare a Use-Case Brief Before Requesting Commercial Terms

The enterprise team can give a more useful answer when the product description is concrete. Prepare the following information before submitting an inquiry:

Information to provide	What to describe
Organization and product	Company, client relationship, product name, and the problem the product solves
Intended users	Employees, named clients, subscribers, public visitors, or users of another service
User scale	Current and expected users, accounts, organizations, and geographic reach
FMP datasets	Exact data families or endpoints being evaluated
Data timing	Real-time, delayed, intraday, end-of-day, or historical
Display	Values, tables, charts, profiles, statements, alerts, or other visible outputs
Exports and delivery	CSV, JSON, PDF, API, data feed, email, scheduled file, or no export
Derived outputs	Calculations, scores, rankings, summaries, signals, or alerts built from FMP data
Technical delivery	REST API, WebSocket, bulk file, batch request, cache, or stored database
Project stage	Evaluation, private beta, client pilot, production build, or public launch

The final description can be short, but it should be specific. For example: "We are building an internal dashboard for 25 employees. It will display end-of-day US equity prices and selected financial statement fields, refresh once daily, and will not provide downloads or external access."

That description gives FMP enough context to address the users, dataset, display, freshness, and delivery method. The enterprise inquiry form provides a field for describing the use case and the organization behind it.

Separate Licensing Fit From Plan Capacity

Licensing answers whether the intended use is permitted. Plan capacity answers whether the subscription supports the required datasets, historical depth, request volume, and bandwidth. A plan with enough API calls does not automatically include public-display or redistribution rights.

Review the licensing path first. Once the use is confirmed, choose an FMP plan based on the workflow's actual data and capacity requirements. This prevents a team from optimizing call limits for a deployment that still lacks the required display rights.

The same distinction applies during technical evaluation. Request limits, response fields, freshness, and historical coverage are technical-fit questions. Users, display, exports, and downstream access are licensing questions. Both reviews matter, but they should not be treated as the same decision.

What Technical Teams Can Validate Before Launch

Once the evaluation is operating under the appropriate access arrangement, the technical team can test the parts of the integration that determine whether FMP fits the product:

• Confirm that the required endpoints return the fields and historical periods the product needs.
• Measure request volume, payload size, bandwidth, and refresh frequency against expected use.
• Identify which responses will be cached or stored and how long the product needs to retain them.
• Keep the API key out of client-side code and prevent users from calling FMP through the account credentials.
• Map every visible value, chart, export, alert, and derived output back to its source dataset.
• Test permissions so internal, client, and public users receive only the access covered by the product design.
• Record any real-time or delayed exchange data separately from end-of-day and fundamental datasets.

This creates a useful bridge between the commercial agreement and the implementation. The agreement defines the allowed scope; the architecture should make that scope enforceable.

Make the Licensing Decision Before the Product Depends on It

The fastest way to classify a project is to answer three questions in order: who the work is for, who can access the result, and what those users can see or receive.

If the project is solely for one individual's personal, non-business use and no one else can access the data or output, the individual-use terms are designed for that situation. If the work supports a business or client, serves multiple users, displays information publicly, provides downloads, or distributes derived outputs, plan for a commercial review before the product relies on the data.

That review does not need to begin with a vague request for enterprise pricing. A short use-case brief can identify the users, datasets, display, exports, derived outputs, and technical delivery. FMP can then evaluate the intended product against the applicable agreement before the launch architecture and customer promises are fixed.

FAQs

Can I use an individual FMP plan to build a private prototype for my startup?

Do not assume that a private environment makes the use personal. FMP's commercial-use definition includes association with a business and analysis performed to support commercial activity. Describe the startup, prototype users, datasets, and planned deployment before relying on an individual plan for the project.

Can I put FMP data on a free public website?

A free website can still display FMP-sourced data to other people. FMP's published terms apply the multi-user display restriction whether access is complimentary or paid. Confirm the appropriate display agreement before publishing the data.

Does a server-side API call avoid the display requirement?

No. Server-side retrieval protects the API key, but users can still receive FMP-sourced values, charts, tables, or other outputs. Licensing depends on the product's users and output, not only where the request is executed.

Can an internal company dashboard use an individual plan?

An internal multi-user dashboard is not personal use simply because it is unavailable to the public. FMP's published data-display terms apply to internal and external organizational applications designed for multiple people.

Are proprietary scores or rankings exempt because they are derived?

Not automatically. The applicable terms address information derived from FMP services, and commercial analysis is part of the commercial-use definition. Explain the source fields, calculation, displayed result, and export options so the agreement can address the derived workflow.

Do all products using real-time data need the same exchange agreements?

Not necessarily. Requirements can depend on the exchanges, datasets, user classification, geography, and delivery model. Identify each real-time or delayed dataset so FMP can determine the required declaration, agreement, and applicable fees.