Ragly turns your vector store into email and API endpoints that answer questions.
Your inbox just got a power-up. Ragly gives you an email endpoint for Q&A and an API endpoint for retrieval, plus a dead-simple way to add docs by email. Send email attachments, and Ragly adds them to your vector store so you can ask for grounded answers.
Bring your docs. Ask questions. Get grounded answers.
Adding docs is as easy as emailing a PDF.
Early access only. No credit card.
Email endpoint (Q&A)
From: [email protected]
“Do we carry over PTO next year?”
Ragly reply: 2 sources + summary
Email endpoint (Ingest)
Attachments: PTO.pdf, Handbook.docx
Ragly: added 2 files to Acme KB
API endpoint
GET /v1/search?query=pto
JSON results in 180ms
Social proof
Built for teams who live in docs and inboxes
Email as an endpoint
Ask questions from your inbox. A friendly email endpoint searches your vector store and replies with grounded results.
Drop docs in by email
Forward email attachments and Ragly adds docs by email so your knowledge stays fresh without extra tools.
API for retrieval
Call a simple API endpoint to power RAG workflows, dashboards, or internal tools.
Features
Every endpoint you need to make Ragly useful fast
Ragly is the glue between your vector store and the places you already work. Use the email endpoint, the API endpoint, or both to turn searches into answers.
- Create a vector store
- Upload docs (web)
- Add docs by email (attachments)
- Generate email endpoint (Q&A)
- Generate API endpoint
- Run vector search
- Get results back (email reply / JSON response)
- Permission controls (allowlist)
Permissioned endpoints
Ragly keeps the knobs simple: set an allowlist for who can ask questions via the email endpoint or API endpoint, and a separate allowlist for who can add docs by email attachments.
Ingesters
How it works
Three steps from docs to answers
Step 1
Add docs to a store
Upload files or add docs by email. Email attachments become searchable knowledge.
Step 2
Create endpoints
Spin up an email endpoint for Q&A, an email ingest endpoint, and an API endpoint.
Step 3
Ask, send, call
Ask a question, send a document, or call the API endpoint. Ragly searches and replies with results.
Examples
Make it click in 10 seconds
Ragly keeps the workflow familiar: email, endpoints, and clear answers.
Email Q&A
Subject: Question about our PTO policy
"If I take 3 days off in December, do they roll over into next year?"
Email ingest
Subject: Add these docs
Attachments:
- pricing.pdf
- faq.docx
API response
{
"query": "PTO rollover",
"matches": [
{"title": "PTO.md", "score": 0.87, "snippet": "Unused PTO rolls over..."},
{"title": "EmployeeHandbook.pdf", "score": 0.81, "snippet": "Carry over up to 5 days"}
],
"answer": "Yes. PTO rolls over up to 5 days.",
"sources": ["PTO.md", "EmployeeHandbook.pdf"]
}FAQ
Quick answers before you ask Ragly
What is a vector store?
It is a searchable index for your docs that makes semantic search fast and relevant.
Do I need to be technical?
No. If you can send an email, you can use the email endpoint. The API endpoint is there for builders.
Can I control who can email or call an endpoint?
Yes. Set an allowlist for who can ask vs who can add docs by email attachments.
What file types are supported?
Common docs like PDF, DOCX, TXT, and more. If it is a document, Ragly can likely ingest it.
Is this a chatbot?
It can power chat, email, or API experiences. Ragly focuses on retrieval and grounded answers, not a single UI.
Ready for Ragly early access?
Add docs by email, get answers by email, and ship clean results from the API endpoint. Ship answers, not tabs.
Ragly is friendly for non-experts and still handy for engineers.