FinFeedAPI data can be used across internal systems, commercial applications, research platforms, AI workflows, analytics products, and other financial data applications.
How the data can be used depends primarily on who can access it and how it is made available. Internal use is generally permitted, while customer-facing use and redistribution may require additional review or licensing depending on how the underlying data is exposed.
For legally binding terms, refer to the FinFeedAPI legal documentation and Acceptable Usage Policy.
FinFeedAPI supports both internal business workflows and commercial applications. Commercial use does not automatically mean redistribution. The important distinction is whether your application uses FinFeedAPI data to provide its own functionality or makes the underlying data available to third parties.
How FinFeedAPI data can be used depends on who has access to the data and how it is delivered.
Internal use generally means FinFeedAPI data is used within your own organization to support systems and business operations without making the underlying data available to external users.
Examples include:
These workflows generally fall within standard internal use.
FinFeedAPI can also power commercial and customer-facing applications.
If FinFeedAPI-sourced data is displayed or otherwise made available to customers or end users, the use case may require additional review or licensing depending on how the data is exposed.
Applications that provide analytics, calculations, indicators, alerts, visualizations, or other derived functionality are different from products that provide users with direct access to the underlying financial data.
Redistribution generally means making FinFeedAPI-sourced raw or near-raw data available to third parties.
Examples may include:
The table below provides practical guidance for common FinFeedAPI implementations. If you are unsure where your application fits, contact our team before making FinFeedAPI-sourced data available to external users.
| Use Case | Typical Treatment |
|---|---|
| Internal research platform | Generally allowed |
| Internal trading or quantitative system | Generally allowed |
| Internal AI or machine learning workflow | Generally allowed |
| Internal dashboards and reporting | Generally allowed |
| Customer-facing derived analytics | Generally allowed, depending on implementation |
| Customer-facing raw data terminal | Requires review |
| Public financial data API | Requires review |
| Bulk raw-data exports to customers | Requires review |
| Selling or licensing raw datasets | Requires permission |
| White-label raw data access | Requires permission |
| Reselling FinFeedAPI API access | Not permitted |
Derived outputs use FinFeedAPI data as an input to create additional functionality, analysis, or information rather than simply exposing the underlying feed. The distinction depends on the actual output provided to users, not simply how the data is technically processed.
Transforming JSON into another format, normalizing fields, storing records in your own database, or routing data through your own infrastructure does not by itself change the licensing treatment of the underlying data.
If customers can retrieve substantially the same financial data supplied by FinFeedAPI, the use case may still be considered redistribution and should be reviewed.
FinFeedAPI is designed for legitimate financial applications, research, analytics, AI, data processing, and production workloads. The Acceptable Usage Policy applies across FinFeedAPI services and may be updated as the platform and its services evolve.
FinFeedAPI API keys are used to authenticate and track access to services and should remain private. If separate organizations, customers, or external systems require direct access, contact our team to discuss the appropriate setup rather than sharing credentials.
FinFeedAPI may monitor service usage to maintain platform reliability and ensure compliance with the Acceptable Usage Policy.
If a workload appears abnormal, harmful, or inconsistent with its intended use, our team may review the activity and contact the customer to better understand the use case.
Where appropriate, we may recommend implementation changes, a different plan, or another commercial arrangement. Access may be limited, suspended, or terminated where usage violates applicable terms or threatens the platform or other users.
Yes. Internal analytics, research, reporting, trading systems, AI workflows, dashboards, and similar applications are generally permitted.
Yes. Commercial use is allowed. If your product makes FinFeedAPI-sourced data available to customers or end users, additional review or licensing may be required depending on how the data is exposed.
Yes. FinFeedAPI data can be used as an input for AI and machine learning workflows. Customer-facing applications that expose the underlying data may require additional redistribution rights.
Potentially. Customer-facing use should be evaluated based on what data users can access. Derived analytics and functionality are different from providing direct access to raw or near-raw financial data.
Not necessarily. Changing a format, renaming fields, normalizing records, storing data in another database, or passing it through your own backend does not automatically turn FinFeedAPI data into a derived output.
If your API provides third parties with FinFeedAPI-sourced data, redistribution permission or a separate agreement may be required.
Bulk exports containing FinFeedAPI-sourced data require review and may require redistribution rights.
Reselling FinFeedAPI services is not permitted by default. Raw data redistribution or resale generally requires explicit permission or an appropriate agreement.
No. API keys should remain private and should only be used by your authorized applications and services.
Every application uses financial data differently. If you are building a customer-facing fintech product, AI application, analytics platform, financial terminal, API, or data service, our team can review how FinFeedAPI data will be used.
Talk to us before launching a product if you are unsure whether your use case requires additional licensing.
