The Book Prize Index: A Vibe-Coded Semantic Search Tool for Award-Winning Nonfiction

TL;DR: Historian Benjamin Breen built the Book Prize Index — a free tool covering roughly 6,500 titles that won or were shortlisted for major English-language nonfiction book prizes — using Claude Code and GPT-5.6 for both data collection and the site itself. It supports semantic search (natural-language queries like "classic biographies that are surprisingly weird") alongside traditional filtering, and hit the Hacker News front page with 190+ points. The most interesting reaction wasn't about the tool's usefulness — it was a pointed debate about whether vibe-coding a project about quality undermines its own premise.

What Breen built and why

Breen, a historian who writes the Res Obscura newsletter, described the origin of the project in personal terms: a college job shelving library books that turned into an "sneakily important intellectual experience" of random discovery — flipping open books he was shelving and occasionally getting absorbed. He built the Book Prize Index to recreate that experience digitally, using book-prize wins as a proxy for quality, since he'd found that books winning or shortlisted for major prizes are "almost always noticeably good."

The process: he had Claude and GPT-5.6 gather lists of finalists and winners from online sources (mostly Wikipedia) across every major English-language nonfiction prize he could identify, then structured that into a searchable, sortable database of roughly 6,500 titles. On top of the structured data, he added semantic search — an embedding model that lets users search by concept rather than exact keyword match.

The site is free to use, hosted at book-prize-index.vercel.app:

"Yes this is actually free. I am paying for the hosting and the API costs entirely because I just want people to find and read more good non-fiction books."

TL;DR — what the tool does

Why semantic search is the actual differentiator

Breen is explicit that semantic search — not the curated dataset alone — is what makes the tool interesting beyond a static list:

"There is really nothing 'AI' about this aside from the tool that collected the data and coded it, and, crucially, semantic search, which for me is the most appealing of all current AI tools precisely because it offers a straightforward improvement for a workflow and habit that researchers already have: it makes text search work better."

The practical difference shows up in queries that would fail entirely against a keyword index. Breen cites examples like:

• "Classic biographies that are surprisingly weird" — surfaces a biography of the James family (William, Henry, and Alice James) that shares no literal keywords with the query.
• "Books for dads who like Pavement" — a query built entirely on cultural inference, not literal book metadata.
• "David Attenborough, but in book form" — matches on conceptual similarity to a public figure's style, not any text field in the database.

This is the core value proposition of embedding-based semantic search applied to a genuinely useful, narrow domain: it approximates the serendipity of physically browsing library shelves — where adjacency, not exact-match retrieval, drives discovery — in a searchable digital interface. That's a materially different experience than typing a query into Amazon or Google Books, both of which are optimized for commercial relevance and literal keyword matching rather than conceptual adjacency.

The provenance critique

The most substantive pushback on Hacker News wasn't about the tool's usefulness — multiple commenters explicitly praised it — but about the irony of using AI to build a project celebrating human-authored quality. Commenter Planktonne put it directly:

"I think my issue with this project — and so many other similar ones — is that the provenance of the code does undermine the intention. If a project purports to be about quality, then knowing that the creator abdicated some of the responsibility for creating the thing they ostensibly care about makes it harder to put faith in them as having high standards elsewhere... This is a project that needs to be cared about sincerely to be trustable/meaningful/useful, and the approach taken casts doubt on that."

This is a genuinely interesting critique because it's not the usual "AI writing is bad" argument — it's about consistency between stated values and production method. The counterargument, made by several other commenters including paxys:

"Very neat site and write-up, but I found this part amusing: 'There is really nothing "AI" about this aside from the tool that collected the data and coded it [...]' So really, everything about it is AI. And that's not a bad thing! It's okay to simultaneously preach the superiority of award winning books over AI-generated garbage while also acknowledging the same AI as a valuable tool for other uses."

The distinction worth drawing out: Breen's actual curatorial judgment — which prizes to include, what counts as a "major" prize, how to weight book-of-the-year lists versus formal prizes — is human-authored decision-making, even though the code and data-scraping pipeline were AI-assisted. Whether that distinction satisfies the provenance critique is a matter of where you draw the line between "the tool" and "the content," which is exactly the debate playing out more broadly this week around Substack's new AI-detection feature and Peter Yang's /no-ai-slop skill — code and prose face the same underlying question of whether AI-assisted production undermines a claim to quality or authenticity.

What the dataset reveals beyond search

Breen used the collected dataset to build several standalone visualizations:

• Books arranged by cover color — roughly 5,000 book covers sorted by dominant color, a visual curiosity rather than an analytical finding.
• Publisher and imprint rankings — which publishers and imprints have historically performed best on non-fiction book awards, a ranking Breen notes he hasn't seen published elsewhere.
• Prize count over time — a chart showing the number of English-language nonfiction book prizes tracked in his dataset, rising steadily through the 1970s-90s, peaking around 2014, and showing early signs of a slow decline from 2020 onward.

That last chart feeds into Breen's broader argument in the post: that nonfiction writing quality likely peaked somewhere between the 1980s and early 2000s, driven by factors like cheaper international travel for research, broader access to archives and rare-book collections following the erosion of class/race/gender barriers, and the Library of Congress's MARC cataloguing standard making sourcing and fact-checking easier — a genuinely interesting historical argument independent of the AI-tooling debate.

What this means for builders

If you're building a narrow-domain discovery tool:

• Semantic search is most valuable in domains with a genuinely curated, bounded dataset (here: prize-winners specifically, not "all nonfiction books ever published") — the curation does the quality filtering, and embeddings do the discovery.
• Publishing a raw data export (Breen added a JSON dump at /data in response to a commenter request) costs little and meaningfully extends a tool's usefulness beyond your own UI.
• If your project makes an implicit claim about quality or authenticity, expect scrutiny of your own production process — the "vibe-coded quality tool" tension isn't unique to this project and will keep recurring as more creator-economy tools ship this way.

If you're evaluating AI-assisted side projects generally:

• The interesting question usually isn't "was AI involved" but "where does the judgment live" — in this case, curatorial decisions (which prizes count, how to weight them) remained human, while data collection and code were AI-assisted. That's a reasonable division of labor worth being explicit about if you ship something similar.

Related on explainx.ai

• Substack launches AI detection with Pangram — what it flags and how
• Peter Yang open-sources /no-ai-slop — a Claude skill for de-sloppifying writing
• Codeberg bans vibe-coded projects — what the new ToU actually says
• What are agent skills? Complete guide

Primary sources: book-prize-index.vercel.app · Res Obscura — Benjamin Breen's Substack · Hacker News discussion

Details reflect Benjamin Breen's July 22, 2026 Substack post and Hacker News discussion as of publication. Dataset size and prize coverage may grow as the creator adds more sources — check the site directly for current scope.