Turn your documents into cited answers.
Ask questions of your own documents and get the answer with the source attached, so anyone can check it. Set it up with no code this afternoon, or call one API from your product.
POST /v1/answers/{corpus}/query → a cited answer in one call · API reference →The retrieval under all of this ranks #1 on MTEB, the public benchmark for search quality. Independently verified, and anyone can check the leaderboard. That is the sentence to repeat when someone asks if the answers can be trusted.
Start from where you actually are.
The same retrieval engine, three different front doors. Pick the one that sounds like your week.
One call. A cited answer comes back.
No vector database to provision, no chunking pipeline to babysit. Keep your stack; swap one URL.
- First real call in under five minutes, key issued at signup.
- OpenAI-compatible embeddings if you only want the model.
- Real prices on one page. No sales call anywhere.
Upload the docs. Share one link.
A private answer page for your team, set up by you, alone, today. No IT ticket, no code, nothing to install.
- Every answer cites its source, so you can defend it without rereading the originals.
- A corpus health score you can show a skeptic.
- Your team's name on it, not ours.
One vendor both halves will use.
Your engineers get the API. Everyone else gets no-code Spaces. One bill, one admin view, one security review.
- SSO and central administration on team plans; SAML, SCIM, and audit logs on Enterprise.
- A security page that states what we have and what we don't, in writing.
- Documents that can't leave your control? Forge Local runs the same engine inside your own AWS account.
- A corpus quality report you can put in front of a VP at day 90.
The part your security review will ask about.
Not stored, not trained on.
Embedding request text is not retained after the response, on every plan. Your content is not used to train models. Stated plainly in the security page and terms.
What we don't have, in writing.
No SOC 2 yet, and we say so before you ask. The Security and Trust page lists encryption, sub-processors, retention, and the gaps, so your review starts with answers instead of emails.
Or keep it in your account entirely.
Forge Local runs the same engine on your own AWS hardware. Nothing crosses our infrastructure, which is usually the shortest path through a review.
Already built RAG, and the answers are still wrong?
Send 10 to 50 failing queries and a sanitized slice of your corpus. We return your Recall@10, your nDCG@10, and the answers you are missing, measured, not guessed. Then you decide.
Free to start. Both doors open.
Try it on one real corpus before anyone asks for a card.