How a round gets into the feed.
Every round goes through four steps before it shows up in the feed. Each step is a Firecrawl endpoint you can call yourself. X is read with Firecrawl too: search finds who posted about each new round, and that is what ranks Trending.
- 01[ Search ]
Search finds the articles
Eight queries per watchlist across news and the web. A result that cannot be an article, like a site root, a tag page, or an investor directory, is declined before any scrape.
search · news + web
- 02[ Scrape ]
Scrape reads each into a schema
One scrape per page with a JSON format: company, stage, amount, date, and investors, plus the sentence that states them. A round whose sentence is not on the page is dropped.
scrape · json format
- 03[ Verify ]
Each record is read back against its sources
Before a record publishes, a model reads it against up to 4 of its sources together and cites the page and sentence for each field. Without a model key, the judge reads the primary page with Firecrawl.
reconcile · up to 4 sources
- 04[ Enrich ]
Enrichment adds the company
The company's homepage, checked against the record first, gives the profile and the logo through the branding format. Alexandria adds sourced facts on the verified domain.
branding · alexandria
Read it in the dashboard, pull it from the API, or hand it to an agent.
The dashboard, feeds, API, and MCP server all use the same verified data, so an agent sees exactly what you see.
The feed. Every round with its logo, stage, amount, lead, and a Verified mark with its source count. Sort by Trending for the rounds X, the press, and Hacker News are talking about.
Companies and investors. A page for each: every round on record, total raised, the syndicate, co-investors, and Alexandria facts.
The API. Rounds, companies, investors, and funding news over /api/v1: JSON, CSV, or JSONL, with the same filters as the feed. Described in OpenAPI.
The MCP server. Tools at /api/mcp, so an agent can list, search, and read rounds the way the dashboard does.
Delivery. Slack in one click, RSS, Atom, and JSON Feed, and Standard Webhooks, each from one outbox.
Share cards. A company or investor link unfurls in Slack with its logo, latest round, and total raised.
Query it with curl, or connect it to an agent.
The same records over HTTP and over MCP. The response below is a row from this instance, trimmed to a few fields. In ChatGPT or Claude, use Fireround in Firecrawl Alexandria.
Get new rounds in Slack or by RSS.
Each new round goes to every channel you set up, and a failed send is retried with backoff. On your own instance you set channels up in Settings, under Delivery; here you can add this feed to Slack or read it as RSS.
- Slack
Add to Slack picks a channel on Slack's own screen, and each new round posts as the message shown here, or one digest each morning. No app to make? Copy a /feed command and Slack's RSS app posts the rounds instead.
Slack setup - Feeds
RSS, Atom, and JSON Feed for each watchlist: public, as on this instance, or behind a private token you can revoke.
- Webhooks
A signed JSON event per round, in the Standard Webhooks format, so any receiver that speaks it can check the signature.
Standard Webhooks
The retries, the digest window, and the webhook headers in full. How it works
The message delivery posts, built from a round in this feed. The buttons open the round and its primary source.
Run your own in four commands.
No database to set up: without a database URL it runs on embedded Postgres under ./data. On Vercel the button provisions Neon, and cron runs the sweeps. It runs on your own Firecrawl API key, and you choose how often it looks.
Need a key? Get a Firecrawl API key
- License
- MIT
- Runtime
- Node 24+ and pnpm
- Database
- Embedded Postgres, or any Postgres 15+
- Schedule
- Vercel cron, or pnpm start ticks itself
git clone https://github.com/firecrawl/fireround.git && cd fireroundpnpm installcp .env.example .env # paste your Firecrawl keypnpm dev # http://localhost:3000# the one you needFIRECRAWL_API_KEY=fc-...# optional: locks the dashboardDASHBOARD_PASSWORD=...# any random string, 16+ charactersCRON_SECRET=...Every other variable is optional; the README lists them. Configuration
