Use case · Engineers building a chunker or embedding service
A content-processor test harness
A stable HTTP harness that exercises your content-processor service against real-world URLs drawn from arbitrary queries.
The problem
You are building the content processor — the service that fetches a URL, strips boilerplate, chunks, and embeds. Testing it against synthetic fixtures is easy; testing it against the messy reality of arbitrary web pages is not. You want a stable driver that feeds it real URLs from real queries and shows you the assembled output.
How Polymathy helps
- Point PROCESSOR_URL at your service and Polymathy will drive it with the top ten URLs for any query you throw at /v1/search.
- The assembled chunk map lets you eyeball how your processor handles real pages end to end.
- Because Polymathy is a single binary with a fixed contract, it makes a reproducible harness in CI or local dev.
What the flow looks like
Test query → Polymathy → your processor (under test) → chunk map → assertions on chunk count, boilerplate removal, embedding shape.
A good fit when
- You are iterating on a chunking or embedding service
- You want to test against real web pages, not fixtures
- You want a stable, scriptable driver for CI
Reach for something else when
- You need a full evaluation framework with scoring built in
- Your processor speaks a contract Polymathy does not send
Other use cases
A Perplexity-style answer UI
A Rust backend that fetches a handful of pages per query and returns them shaped for prompt-stuffing, so your UI owns the chat and the citations.
Read →An internal-docs answer engine
Point SearxNG at your internal indices and turn matches into cited chunks for a private assistant your employees can trust.
Read →A cited research assistant
Ground every generated paragraph in real source URLs, because the chunk-to-URL mapping is enforced by the response shape.
Read →