Build with a serious retrieval layer.
Use a developer path that makes the next step obvious: create an account, get a key, test MCP, and move into docs or discovery without guessing where the real product is.
Create a key and run one request
The first developer experience should feel obvious: sign up, create a key, read the quick path, and test MCP without hunting through marketing.
Header-only auth and rights-aware retrieval
The product should make safety and scope legible, not bury them behind vague claims or magical language.
Public-domain retrieval should not waste AI spend
When chunks and source links answer the question, the system should favor the direct path and let synthesis remain an intentional choice.
From account to first request in minutes.
- 01
Create your account
Use the secure signup flow and land in onboarding instead of a generic dead-end.
- 02
Get a key or run MCP
Move straight to key creation, docs, or the MCP demo path without guessing what matters first.
- 03
Search or add content
Use the public-domain path for chunk-first search, or move into the real ingestion route when you are ready to push content.