Priced workload · Agents

Ticket triage and bulk classification

Label and draft replies for a high volume of short requests, and see what one ticket costs.

Why the bill is hard to read

Short, repetitive requests arrive in volume. Sending every one to the top model pays a flagship price for easy work. A bill per token does not show what one ticket costs.

How AVELIN is used

Put each step on the tier that fits it. A fast tier labels the request, the pro tier drafts the reply, and only the cases the first pass could not settle reach the ultra tier or a person. In the API you can name the tier, or let the Decision Layer choose. A POC compares your split with what the Decision Layer would choose for the same tickets.

  1. Label

    Send each request to avelin-agentic-fast with a fixed list of labels and ask for one label back.

  2. Draft

    Send the labelled request and the matching help text to avelin-pro and ask for a draft reply.

  3. Escalate

    Send requests the first pass could not label to avelin-ultra, or to a person.

  4. Log

    Keep the label, the tier and the token counts for every request, so each ticket has its own cost.

Tiers and list prices

USD per 1M tokens unless stated, list price as of 3 October 2026.

The models or endpoints this workload uses, with their list prices.
Model or endpointUsed forList price
avelin-agentic-fastLabel the request$0.285 in, $1.14 out
avelin-proDraft the reply$1.40 in, $4.40 out
avelin-ultraCases the first pass could not settle$2.50 in, $12.50 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.

  • Calls per ticket, counted in a log of one real day.
  • Input and output tokens per call.
  • Which tier answered each call.
  • How many tickets reach the ultra tier or a person.

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 "Ticket triage and bulk classification"?

Label and draft replies for a high volume of short requests, and see what one ticket costs.

Which tiers does it use?

It uses avelin-agentic-fast, avelin-pro, avelin-ultra. 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.

Request a POC

Bring one workload. See its cost per task.

Start with a POC on one of your workloads.