A data layer for people and AI agents

Stop filtering the news by hand.
Name a topic. feedql builds the feed.

feedql collects from the sources you choose, an LLM scores every item against your topic and says why, duplicates fold away and reports of one event are grouped. Your agents query it through MCP and the API; you read it on the web or export it for analysis.

No spam, one email when your seat is ready.

FQL
topic:"fusion" source:hn,github since:7d score>70
  1. 94
    Compact tokamak reaches a new plasma-confinement record 11 items grouped · first seen on GitHub · 2h ago Why: an experimental result, the core of your topic
  2. 86
    Open-source plasma simulator ships a major release 5 items grouped · first seen on Hacker News · 1d ago Why: a release of a tool you follow
  3. 78
    Funding round announced for a fusion start-up 3 items grouped · first seen on Hacker News · 3d ago

feedql = feed + query language.

Ask your feeds like a database. Filter by topic, source, time and score, and get grouped events back instead of a stream to scroll.

Scattered newspaper clippings stream through a prism and come out as three neat cards

What we all tried.

  • Alerts & RSS

    A flood with no sorting

    One story arrives five times because five sites reprinted it, and nothing tells you which copy came first.

  • Big aggregators

    Fine until the pivot

    The product is rewritten for enterprise, features vanish, the API closes, and years of setup stay inside. Google Reader gave millions of people three months to leave.

  • Fifteen tabs

    Every morning, by hand

    It works the longest, and it costs the most: the same sites, the same scrolling, the same things missed.

A feed that builds itself.

It started as a script for one person: pull HN, Reddit and GitHub, let a model decide what fits, and make it explain why. Two months later it reads 20+ kinds of sources.

One pool, two readers.

You need to see what matters fast and not get lost. Your agent needs structure. feedql serves both from the same data, and can be your agent's outside memory: say it researches a client, feedql has been collecting reviews of their apps for months, and the agent takes a clean base. No storage to run, nothing to rebuild from scratch.

Data ready for analysis.

Market research, competitor watch, app-review mining, lead and tender tracking: feedql does the collecting and cleaning, so your analysis and your LLM start from a dataset, not a scraper.

Ask the feed.

A built-in assistant sits next to every item. It answers from your actual settings and data, and it changes nothing without your confirmation.

Sources beyond RSS

Rolling out calmly.

Reading thousands of sources a day without getting banned, losing anything or flooding people with repeats is its own engineering problem. So feedql opens in steps.

  1. Now

    Private beta. The collection runs every day across thousands of sources.

  2. Next week

    The first small group from the waitlist gets in.

  3. Then

    Entry by invite, step by step, so nothing breaks and nobody gets flooded.

Join the waitlist

The first seats go to a small group. Leave your email and tell us what you follow.