Search knowledge with evidence, not guesswork.
Search public knowledge, route into the right portal, and move from curiosity to a real next step without guessing what this product is for.
Make the first decision obvious.
The homepage should not make an author feel like they landed in a developer tool, and it should not make a developer hunt for the serious path. Start with the route that fits what you are here to do.
For Developers
Start with docs, keys, MCP, and a real first request path.
Best for API users, agent builders, and teams that need a serious retrieval layer.
For Searchers
Search public-domain knowledge with direct evidence and source-linked results.
Best for people who want answers grounded in chunks, citations, and readable sources.
For Contributors
Add public or open material through a rights-aware path instead of blind publishing.
Best for uploaders who need proof, review, and a truthful submission process.
Put people at ease before asking them to trust the system.
Verified citations stay attached
Search, summaries, and source pages should keep provenance visible instead of hiding it behind generic AI copy.
Retrieval first, synthesis second
When public-domain chunks answer the question cleanly, the product should not waste AI-answer cost pretending that is the better path.
Rights-aware by default
Public, private, licensed, and restricted paths should not blur together. The UI should make scope and safety legible.
The site should always show what comes next.
Start with the demo, go straight to developer onboarding, or read the docs before you touch a single endpoint. No dead-end pages. No fake certainty. No generic AI theater.