Show HN: A Vectorless LLM-Native Document Index Method
Show HN (score: 12)Description
Computers later borrowed the term for data structures: e.g., B-trees, hash tables, and more recently, vector indexes. They are highly efficient for machines; but abstract and unnatural: not something a human, or an LLM, can understand and directly use as a reasoning aid. This creates a gap between how indexes work for computers and how they should work for models that reason like humans.
PageIndex is a new step that "looks back to move forward". It revives the original, human-oriented idea of an index and adapts it for LLMs. Now the index itself (PageIndex) lives inside the LLM's context window: the model sees a hierarchical table-of-contents tree and reasons its way down to the right span, much like a person would retrieve information using a book's index.
PageIndex MCP shows how this works in practice: it runs as a MCP server, exposing a document's structure directly to LLMs/Agents. This means platforms like Claude, Cursor, or any MCP-enabled agent or LLM can navigate the index themselves and reason their way through documents, not with vectors/chunking, but in a human-like, reasoning-based way.
More from Show
Show HN: DocsRouter – The OpenRouter for OCR and Vision Models
Show HN: DocsRouter – The OpenRouter for OCR and Vision Models Most products that touch PDFs or images quietly rebuild the same thing: a hacked-together “router” that picks which OCR/vision API to call, normalizes the responses, and prays the bill is sane at the end of the month.<p>DocsRouter is that layer as a product: one stable API that talks to multiple OCR engines and vision LLMs, lets you route per document based on cost/quality/latency, and gives you normalized outputs (text, tables, fields) so your app doesn’t care which provider was used.<p>It’s meant for teams doing serious stuff with documents: invoices/receipts, contracts, payroll, medical/admin forms, logistics docs, etc., who are either stuck on “the OCR we picked years ago” or are overwhelmed by the churn of new vision models.<p>Right now you get a REST API, simple SDKs (coming soon), a few pluggable backends (classic OCR + newer vision models), some basic routing policies, and a playground where you can upload a doc and compare outputs side by side.<p>I’d love feedback from HN on two things:<p>1- If you already juggle multiple OCR/vision providers, what does your homegrown router look like, and what would you need to trust an external one?<p>2 - Would you prefer this or use the LLM/OCR providers directly, with the possibility of changing the provider every so often?<p>Demo and docs are here: <a href="https://docsrouter.com" rel="nofollow">https://docsrouter.com</a>
Show HN: Diesel-guard – Lint Diesel migrations for unsafe PostgreSQL patterns
Show HN: Diesel-guard – Lint Diesel migrations for unsafe PostgreSQL patterns
Show HN: Apicat – A Lightweight Offline Postman Alternative
Show HN: Apicat – A Lightweight Offline Postman Alternative Apicat is the ultimate offline Postman alternative that stores your .http files locally. It’s Git-friendly, open-source, and highly compatible with Postman. Test APIs offline with this powerful free offline API client designed for developers who need a reliable local API testing tool.
Show HN: Cmux – Coding Agent Multiplexer
Show HN: Cmux – Coding Agent Multiplexer HN,<p>I'm stoked to share this product I've been working on non-stop for the past few weeks. It's an immersive GUI experience for working with many coding agents in parallel. The UX should be familiar to Claude Code users, but we took advantage of the GUI nature to add in a bunch more.<p>cmux is early but certainly usable—almost all of our internal cmux development rolls through cmux itself. Please let me know your thoughts and feedback!
No other tools from this source yet.