Priced workload · Retrieval
Search and answers over your documents
Embed documents once, retrieve the passages for each question and answer from them, at list prices.
Why the bill is hard to read
Embedding is cheap and done once. Answers are paid per question. The cost of an answer depends on how many passages you send with it.
How AVELIN is used
Embed each document once with bge-m3. For each question, embed the question, fetch the closest passages and send them with the question to avelin-fast or avelin-pro. Y-Ray Data packages this with citations for teams that do not want to build it.
Embed
Send each document to bge-m3 once and store the vectors.
Retrieve
Embed the question and fetch the closest passages from your store.
Answer
Send the question and the passages to avelin-fast, or to avelin-pro for harder questions.
Cite
Return the passage and document each part of the answer came from.
Tiers and list prices
USD per 1M tokens unless stated, list price as of 3 October 2026.
| Model or endpoint | Used for | List price |
|---|---|---|
bge-m3 | Embeddings, once per document | $0.02 per 1M tokens |
avelin-fast | Answers to routine questions | $0.30 in, $1.20 out |
avelin-pro | Answers to harder questions | $1.40 in, $4.40 out |
What to count
Cost per task = the sum, over every call in the task, of (input tokens × input price + output tokens × output price) ÷ 1,000,000. Add cache write and cache read tokens at their own rates, and add any web requests at their per-request price.
- Tokens embedded per document, which you pay once.
- Passages and tokens sent with each question.
- Questions per day, which sets how much of the cost is chat.
Count this workload on your own runs, or request a POC and we price one workload at list price beside your current bill.
Questions about this use case
What is "Search and answers over your documents"?
Embed documents once, retrieve the passages for each question and answer from them, at list prices.
Which tiers does it use?
It uses bge-m3, avelin-fast, avelin-pro. Prices are in US dollars per 1M tokens, list price as of 3 October 2026.
How do I test it on my own workload?
A POC is a proof of concept on one of your workloads. It runs beside your current setup, with nothing in your production path, and ends in a cost-per-task report.
Bring one workload. See its cost per task.
Start with a POC on one of your workloads.