Using Fireround.

The source code is open under the MIT license. You may run, change, and redistribute it under that license. Your own copy is yours to operate, and these terms cover only this site.

Each record is extracted automatically from public reporting and links to the pages it came from. The data is provided as is. It may contain errors, omissions, or out-of-date figures, so check the linked sources before you rely on a record. It is not investment advice.

You may use, copy, and republish the records. Attribution to Fireround, with a link to this site, is appreciated. The articles, announcements, and filings we link to belong to their publishers; we show a short excerpt and link to the original, and the publisher's own terms govern the original.

Found a mistake? The corrections process explains how to report it.

The API, feeds, and MCP server are free to use within fair limits. Per IP address, the current limits are:

• API pages (JSON and JSONL): 60 per minute.
• Full CSV exports: 10 per 10 minutes.
• MCP calls: 60 per minute.

A request over a limit gets HTTP 429 with a Retry-After header. Limits can change. Please do not work around them (for example by rotating addresses), load the site in ways that degrade it for others, or use the data to spam or harass the people and companies it names. We may block traffic that does. For bulk use, run your own copy.

Add Fireround only to Slack channels you are allowed to add apps to. A channel receives at most 50 posts a day, and every post links to manage or unsubscribe.

The site, the data, and the code are provided "as is", without warranty of any kind, express or implied, including fitness for a particular purpose and accuracy. To the extent the law allows, Firecrawl is not liable for any loss arising from your use of them. We may change, pause, or stop the service at any time.

When these terms change, this page changes with them, and the date at the top says when.

Open an issue on GitHub, or email maxwell@sideguide.dev. No account is needed for either.

How we handle data is on the privacy page.