Skip to main content

AI Use Cases: GPUs and LLM APIs Compared

What a workload costs depends on how you run it. Calling a hosted model bills per token; renting GPUs bills per hour. Each page below covers what the workload demands, which models or GPUs suit it, and what providers currently charge.

API inference

LLM API use cases

All LLM API prices →

Models are chosen from live prices by a quality floor and any hard requirement, then ranked by the estimated cost of a typical request. Figures are per 1,000 requests at the cheapest provider.

Best LLMs for Coding Agents

Long, mostly cached repository context with high reasoning demands

40,000 in · 2,500 out per request
9 modelsfrom $5.53 / 1,000 req

Best LLMs for Reasoning and Research Agents

Multi-step planning, tool use and long outputs on hard problems

60,000 in · 8,000 out per request
7 modelsfrom $16.45 / 1,000 req

Best LLMs for Customer Support Chatbots

Short conversational turns where latency and cost per conversation matter

3,000 in · 400 out per request
27 modelsfrom $0.135 / 1,000 req

Best LLMs for RAG Question Answering

Answering from retrieved passages with grounded, cited responses

8,000 in · 500 out per request
22 modelsfrom $0.453 / 1,000 req

Best LLMs for Document Summarization

Large inputs, short outputs — input rate and context window decide the bill

25,000 in · 800 out per request
1 modelfrom $45.21 / 1,000 req

Best LLMs for Structured Data Extraction

Turning emails, invoices and forms into JSON at volume

4,000 in · 600 out per request
33 modelsfrom $0.118 / 1,000 req

Best LLMs for Classification and Content Moderation

Tiny outputs at very high volume — the cheapest capable model wins

600 in · 15 out per request
266 modelsfrom $0.0061 / 1,000 req

Best LLMs for Vision and Document Understanding

Reading screenshots, scans, charts and photos alongside text

3,000 in · 500 out per request
1 modelfrom $7.43 / 1,000 req

Best LLMs for Translation and Localization

Output roughly equal to input — both token rates count

1,500 in · 1,600 out per request
33 modelsfrom $0.187 / 1,000 req
Self-hosted

GPU use cases

All GPU prices →

GPUs are ordered by suitability for the workload, not by price. Figures are the lowest current on-demand rate per GPU-hour across providers.

Frequently Asked Questions

Should I call an LLM API or rent GPUs and run the model myself?

An API bills per token and needs no infrastructure, so it suits variable or modest traffic and access to closed models. Renting GPUs bills per hour whether or not they are busy, so it pays off when utilisation is steady and high, when you need an open-weight model the APIs do not host, or when data must stay on hardware you control.

How are the API cost estimates calculated?

Each API use case states a typical request: input tokens, how many of them are served from a prompt cache, and output tokens. The estimate applies every provider’s current standard rates to that request and takes the cheapest provider for each model. The request shape is shown on each page so you can scale it to your own traffic.

How are models chosen for each API use case?

Models are selected from live pricing rather than a fixed list. Each use case sets a quality floor as a percentile of the Artificial Analysis Intelligence Index across all priced models, plus any hard requirement such as image input or a minimum context window. Models that clear it are ranked by estimated cost.

How are GPUs ordered on the GPU use-case pages?

By suitability for the workload — memory capacity, bandwidth, interconnect and precision support — not by price. The comparison table shows each GPU’s specs beside its lowest and median on-demand rate per GPU-hour, its lowest spot rate, and for multi-GPU workloads the cheapest node of the typical size. Spot and reserved rates are never used as the headline price.