Priced workload · Agents
Research agent with web access
Search, read and summarize sources with citations, and count the web requests and the tokens on one bill.
Why the bill is hard to read
A research task mixes model calls and web requests. Counting only tokens misses the web half of the cost.
How AVELIN is used
Use the search and scrape endpoints for sources and avelin-agentic-pro for planning and writing. Each web request has its own list price, so one task has two lines on the bill: model tokens and web requests.
Plan
avelin-agentic-pro breaks the question into searches.
Search
POST /v2/search for each query, at $0.005 per request.
Read
POST /v2/scrape for each page, at $0.001 per request.
Write
avelin-agentic-pro writes the answer and cites the URL of each source.
Tiers and list prices
USD per 1M tokens unless stated, list price as of 3 October 2026.
| Model or endpoint | Used for | List price |
|---|---|---|
avelin-agentic-pro | Planning and writing | $1.26 in, $3.96 out |
POST /v2/search | Web search | $0.005 per request |
POST /v2/scrape | Read one page | $0.001 per request |
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.
- Searches and page reads per task.
- Tokens per planning call and per writing call.
- Total web requests multiplied by their list price, added to the token cost.
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 "Research agent with web access"?
Search, read and summarize sources with citations, and count the web requests and the tokens on one bill.
Which tiers does it use?
It uses avelin-agentic-pro, POST /v2/search, POST /v2/scrape. 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.