API Terms
Version api-1 · Last updated 7 October 2026
These terms cover the Fundalyze API and MCP server (together, the “API”): the way to reach Fundalyze data from your own code, scripts and AI tools with an API key. They add to our Terms of Service, which still apply in full. Where the two disagree about the API, these terms win.
You accept them when you create your first API key, and we keep a record of that, with the version you accepted. The Terms of Service do not allow automated access except through features we provide for it: the API is that feature, and these terms are how you may use it.
What you may do
While your plan is in good standing, we grant you a limited, non-exclusive, non-transferable, revocable licence to call the API and use what it returns for your own analysis and in your own tools: your scripts, your spreadsheets, and AI assistants or agents that you run for yourself. The API is included in every paid plan and ends when your plan does.
What you may not do
- Resell, sublicense or redistribute the data, in raw or bulk form, or offer it to others as a feed, a dataset or an API of your own.
- Cache, store or crawl the API to rebuild our dataset, or any large part of it. Keeping what you need for your own analysis is fine; mirroring the database is not.
- Use the API to build a product that competes with Fundalyze.
- Share a key with anyone else, or use more keys or accounts to get around the limits.
- Attack, overload or probe the API, or try to reach data that is not offered through it.
Credit us when others see it
When output from the API is shown to other people, for example in a post, a report, a newsletter or a screenshot, credit it as “Data via Fundalyze” with a link to fundalyze.ai or to the page the answer links to. Every answer carries that link.
Keys and limits
- Keep your keys secret. Anything done with a key counts as done by you. If a key may have leaked, revoke it straight away from Account → API & MCP.
- You can revoke a key at any time. So can we, if it is misused.
- Today's limits are 2,000 calls per key per day (reset at 00:00 UTC, REST and MCP together), 3 keys per account, and one call at a time per key. We may change them, and will email you before a change applies to you.
- The tools, their inputs and their answers may change as the API grows.
Third-party sources
The API passes on public data from other organisations, and their terms come with it:
- Filings, financial statements and insider trades come from the SEC's EDGAR system. Filings are public records.
- Congressional trades come from the disclosures filed with the U.S. House of Representatives and Senate.
- Headlines are found through the news index of the GDELT Project. Each one belongs to its publisher and links to the article on the publisher's site; the API gives the headline and link only.
- Economic indicators come through FRED, the Federal Reserve Bank of St. Louis's data service. This product uses the FRED® API but is not endorsed or certified by the Federal Reserve Bank of St. Louis. Some series are copyrighted by their publishers.
More detail is on our Data attributions page.
No warranty, and not advice
The API is provided “as is” and “as available”. Its data may be delayed, incomplete or wrong, and it may be unavailable at times. Nothing it returns is investment advice, and an AI tool reading it can still get things wrong: check the original filing before relying on anything. The disclaimers and limits on our liability in the Terms of Service apply to the API too.
Suspension
We may suspend or revoke your API access, without warning, where we reasonably believe a key is being abused, shared, used to redistribute or rebuild our data, is overloading the service, or puts a data source's terms at risk. Where it is reasonable to, we will tell you why.
Changes to these terms
We may update these terms. When we make a material change we will post the new version here and email you before it takes effect. Continuing to use the API after that means you accept the change; if you do not, revoke your keys.
Contact
What changed
- Version api-1, 7 October 2026: First published.