Firehose
Dashboard

The live feed

Watch matches arrive in real time in the dashboard, review them as they stream in, then save the ones that matter and export your selection for later.

View as Markdown

The feed is the dashboard view of a tap's stream. It's the same matches you'd receive over GET /v1/stream, rendered live as cards so you can monitor a tap without writing any code.

What you see

Each card shows the matched page's title, URL, domain, language, category labels, and publish time, plus the content diff that triggered the match. You can:

  • Search and filter the feed by text to focus on a subset.
  • Open a match to read its full diff.
  • Save a match so it doesn't roll off the live view.

Reviewable matches

Each plan includes a monthly allowance of reviewable matches — how many the feed surfaces in the dashboard each calendar month. Once that allowance is used up, the feed waits until the next month to show new cards; the SSE stream is unaffected and keeps delivering every match. See plans for the per-tier numbers.

The feed is for monitoring and triage in the browser. For programmatic ingestion at volume, use the SSE stream directly.

Saving matches

The live feed is a rolling window. To keep a match around, save it — pinning it to a persistent list scoped to your organization. A saved match stores the full event: URL, title, the originating tap and rule, language, category and type labels, publish time, and the matched content. You can attach a note to capture why it mattered.

  • Deduplicated by URL — saving the same URL twice is a no-op, so re-saving is safe.
  • Shared within the org — saved matches are visible across your organization, with the saver recorded.
  • Searchable — find saved matches by text from the Saved page.

Saving matches requires a paid plan. The Free and API-only tiers don't include the saved list — see plans.

Exporting matches

Saved matches can be exported to CSV from the Saved page — useful for reporting, sharing, or loading into a spreadsheet or BI tool. The export includes, per saved match:

  • matched_at, saved_at
  • url, title, domain, language
  • page_category, page_types, publish_time
  • the originating tap and rule
  • your note and the saved_by user

For continuous, programmatic delivery rather than a point-in-time export, consume the SSE stream and write matches to your own store.

Next steps