I Tested an Anime Search Engine on 580 Real "Tip of My Tongue" Posts — Here's What Happened
Every anime fan knows this feeling: you vaguely remember a show from ten years ago—"a detective stuck in a time loop trying to stop a murder in a small town" or "a character with a black cloud tattoo with red borders"—and keyword search gets you nowhere because none of those exact words appear in the synopsis.
That frustration is why I built Anime Akashic Records (AAR)—a semantic discovery engine and developer API covering 146,140 works (anime, manga, light novels, visual novels, and manhwa) alongside 760,000+ timestamped anime scenes across 102,264 episodes and 10,565 story arcs.
You can test the live search directly on aarecords.tech without creating an account.
Why I Skipped Synthetic Benchmarks
It's easy to make any semantic search engine look great if you generate clean test queries with an LLM. Real people don't search like that. Real people forget character names, mix up two different shows, misremember the year, and write messy paragraphs on r/tipofmytongue.
So instead of synthetic tests, I collected 580 real, unedited human posts from r/tipofmytongue (zero LLM rewriting, zero query cleanup—even keeping noisy posts that barely describe anything or just drop dead video links) and ran them end-to-end against the live production API.
Live Evaluation Results (580 Raw Queries)
| Metric | Result |
|---|---|
| Franchise Recall @ 20 | 65.5% (380 / 580 recovered) |
| Exact Match Recall @ 20 | 61.9% |
| Median Live Latency (during eval) | 786 ms |
| Safe-for-Work Isolation | 0 / 580 NSFW leaks |
Both the raw 580-query JSONL dataset and the Top-20 outputs are publicly downloadable from aarecords.tech/about#benchmark if you want to inspect the failure cases or benchmark your own search pipeline against them.
What Makes It Different From Standard Catalog Search
Most anime databases rely on exact titles, genres, and tag filters—which work great when you already know what you're looking for, and fall apart when you only remember a premise, a trope, or a single scene.
AAR approaches discovery from three angles:
- Plot & Trope Understanding: Combines semantic meaning with keyword matching and reranking so vague, natural-language plot descriptions still surface the right title—even when none of your words appear in the official synopsis.
- Scene-Level & Arc Indexing: Goes deeper than series summaries by indexing timestamped episode scenes, dialogue, and canonical story arcs so you can pinpoint exact episodes and moments.
- Cross-Platform ID Mapping: Unified records across MAL, AniList, AniDB, TMDB, and VNDB so developers don't have to stitch five databases together.
Using the Developer API
If you're building an anime Discord bot, a recommendation widget, or an AI agent that needs grounded anime and manga citations instead of hallucinated episode numbers, there's a REST API with a free daily tier at https://api.aarecords.tech:
curl -G "https://api.aarecords.tech/search" \ --data-urlencode "q=time loop detective trying to prevent a murder in a small town" \ --data-urlencode "limit=5" \ -H "X-API-Key: YOUR_API_KEY" Core endpoints include:
-
GET /search— Semantic and keyword discovery across all 5 media types -
GET /recommend— Similarity and plot-based recommendations -
POST /lore-ask— Citation-backed answers grounded in episode scenes and story arcs
Try Breaking It
The most useful feedback right now is weird, vague, half-remembered queries that trip the engine up. Give it a try on aarecords.tech (no signup needed) and drop the hardest anime memory you can think of in the comments—I'd love to see where it nails it and where it fails.