Table of Contents
About The Project
Every host-read promo a podcast network runs for its new show is an ad slot it didn't sell, yet launch plans are drawn up by topic: the new true-crime show goes on the other true-crime shows. Crossfeed plans by who listens instead. It looks the launch and the network's shows up in Qloo, ranks the roster by how much each show's listeners overlap the launch's, asks a person at each fork, and drafts an insertion order that code prices from the network's own downloads and CPM. A member approves it; the agent never can.
The same engine works the booking inbox. Crossfeed reads the pitches publicists send, looks up the public work each guest is promoting, a book, film, TV show, or podcast, ranks those works against a show's listeners, and drafts a reply to every pitch for the booker to approve, edit, or discard.
Beside every Qloo ranking sits the plan an agent without Qloo would make: Claude's ranking from show names and descriptions, or from a pitch's own words, with no Qloo data. So what Qloo adds is on the screen, not asserted.
It's a product a network's members sign in to, with passkeys, shared networks, a REST API, a TypeScript SDK, an MCP server, and a Claude Code plugin. Anyone can try it as a guest, in one click, on a sample network built from The Ringer's public show names, with labelled sample figures. Crossfeed isn't affiliated with The Ringer.
Built for the Qloo Agentic Hackathon: the entry is on Devpost.
Screenshots
The live app on October 30, 2026, signed in as a guest, on the guest network's sample data.
How It Works
-
Start a run. Open a launch, such as the sample network's The Watch, and select Start run. The agent looks the launch up in Qloo, ranks the roster against its listeners in one call, and asks you for a slot budget, then which shows to leave out.
-
See who shares its listeners. The fit chart ranks the roster by listener overlap, with each show's rank in a topic-only plan beside it. A show that climbs three or more places is marked ▲: select it for why it moved, and select a call number, such as C-53, for the Qloo request and raw scores behind it.
-
Approve the plan. The agent drafts slots and a host-read angle for each finalist from the tags its listeners share with the launch's in Qloo. Code prices each slot, holds the plan to the budget, and names any close pairs among its shows. Only a member approves it, and only then exports the CSV.
-
Hand it on. An approved order has a launch report to print or save as PDF, with an index of every Qloo call it cites.
-
Run it again. Answer differently, and the launch's Changes tab says what changed since the earlier run: the inputs, the finalists, each show's move, and the plan's slots and value.
-
Work the inbox. On the inbox's Rank tab, select Rank pitches. Each type of pitched work is ranked against the show by who listens, beside its rank by the pitch's own words, and every pitch gets a drafted reply under Book, Later, or Decline.
Features
- Ranked by who listens. One Qloo insights call ranks the network's closed list, its own roster, against a launch, or against up to three comparable shows for a launch that hasn't aired.
- The counterfactual on screen. Claude's topic-only ranking sits beside Qloo's in every run, and the chart's lens moves the rows between the two.
- An agent that asks. It asks a person for the budget, the shows to leave out, and any ambiguous Qloo match, and it has no tool to approve or export.
- Priced by code. Each slot is worth downloads per episode × CPM ÷ 1,000, from the network's own figures, and code refuses a plan over the budget.
- Evidence for every figure. Each ranking, tag, and flag cites its Qloo call, which opens the request, its status, latency, and cache hit, and the raw scores.
- Analysis where it belongs. The roster's overlap and close pairs, its listeners by age band and gender, what changed between runs, the promo inventory, and a printable launch report.
- The booking inbox. Pitches as
.eml, .mbox, or text. Only each work's title and type reach Qloo, never a name, an address, or the pitch's text.
- A product to sign in to. Passkeys with no password or email, networks shared with invited teammates who see each other's changes live, roster CSV import, each network's own Qloo key, and daily caps.
- For scripts and assistants. A REST API with an OpenAPI document, the
@crossfeed/sdk TypeScript client, an MCP server at /mcp, two Agent Skills, and a Claude Code plugin. None of them can approve anything.
- Honest limits. Past the day's limits, or while Qloo fails, the sample launch replays its stored run, labelled "Replayed", and every other run stops and says why.
Architecture
One Worker serves every surface. Each network and each launch is its own Agents SDK Durable Object, which runs Claude's tool loop, and every Qloo call goes through one gateway Durable Object that caches, paces, retries, and caps them. A D1 database holds only what has to be looked up across them: members, networks, sessions, invites, and API keys.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
