What generative AI is, and why people build with it

Generative AI is software that produces new text, code, images or audio in response to an instruction, using a model trained on very large amounts of existing data. When people say "AI" in 2026 they usually mean a large language model (LLM): a model that reads text and writes text, such as the models behind ChatGPT, Claude, Gemini or Le Chat.

This page explains what these models do, what people actually use them for, where they fail, and how you pay for them. For the vocabulary, see the glossary.

How it works, in one paragraph

An LLM continues text: given everything so far, it predicts the next small piece, then the next, until it stops. Anthropic describes pretraining as teaching a model "to predict the next word, given the previous context of text in the document" (Anthropic glossary, checked 2026-10-28). A raw pretrained model is then further trained (fine-tuned, often with human feedback) so that it follows instructions and behaves like an assistant.

The pieces it reads and writes are called tokens. OpenAI's rule of thumb: "1 token is approximately 4 characters or 0.75 words for English text" (OpenAI docs, checked 2026-10-28). The exact ratio depends on the model and the language, so use the provider's token counter when it matters.

Two consequences follow from this design:

What developers and entrepreneurs use it for

The most common use is writing and checking code. In the 2025 Stack Overflow Developer Survey, "84% of respondents are using or planning to use AI tools in their development process" (survey, 2025, checked 2026-10-28). In the 2026 edition, 73% of respondents use coding assistants and agents daily (survey, 2026, checked 2026-10-28).

Beyond code, the uses that hold up well in practice share one trait: a person or a program can check the result.

Use Example Why it works
Drafting First version of an email, a product page, a job ad A person edits before it goes out
Summarizing A 40-page contract into one page of key clauses You can check against the original
Extracting Invoice PDFs into rows: supplier, date, total Output is structured and testable
Classifying Routing support tickets to "billing", "bug" or "sales" Errors are cheap and measurable
Answering from your documents A help bot that quotes your docs (RAG) Answers can cite their source
Coding Writing a function, a test, a migration script Code can be run and tested
Acting through tools An agent that reads an issue, edits code, runs tests The loop checks its own work, within limits

For a founder, the pattern is usually one of two:

Where it fails

The main limit is that the model can be wrong without warning. Anthropic's own guide says models "can sometimes generate text that is factually incorrect or inconsistent with the given context", which is called hallucination, and that mitigation techniques "don't eliminate them entirely" (Anthropic, reduce hallucinations, checked 2026-10-28). Developers notice: in the 2025 survey, 66% named "AI solutions that are almost right, but not quite" as a frustration, and more respondents distrusted AI accuracy (46%) than trusted it (33%) (survey, 2025).

Other limits worth knowing before you build:

A practical rule: use generative AI where a wrong answer is cheap to spot and fix, and add a check (a person, a test, a schema) where it is not.

What it costs

There are two ways to pay: a monthly subscription for a chat app, or per token through an API.

An example, using one vendor's list prices. Anthropic lists Claude Sonnet 5.5 at $2 per million input tokens and $10 per million output tokens (Anthropic pricing, checked 2026-10-28). Suppose a support bot handles 1,000 conversations a day, each sending 2,000 tokens and receiving 500:

This is arithmetic on list prices, not a measurement; real conversations vary a lot in length. The same page lists ways to pay less, for example a Batch API with "a 50 percent discount on both input and output tokens" for work that can wait, and lower prices for cached, repeated input (Anthropic pricing). Other providers have similar mechanisms; compare on providers and models.

Three habits keep the bill predictable:

  1. Pick the smallest model that does the job. Prices across one vendor's own tiers can differ by more than ten times.
  2. Set a spend limit in the provider's console, and per-user limits in your app. See the workflow page.
  3. Count the hosting separately. Calling a model and hosting your app are two different bills. See the cloud for AI apps.

See also

Glossary terms used on this page: Agent, API, Cloud, Coding agent, Context window, Generative AI, Hallucination, Host, LLM, Model, Prompt, Provider, RAG, Temperature, Token, Tool, Workflow.

Sources

All checked on 2026-10-28.


First version written with AI assistance and checked against the sources on 2026-10-28. Found a mistake? Fix it or open an issue. Text licensed under CC BY 4.0.