Which AI Model Should You Use? The November 2026 Guide

A practical guide to choosing AI models and agents across work, school, research and everyday operations. Model and price checks: 3 November 2026.

The useful question is not “Which model is best?” It is “Which part of this job can I safely hand to which system, at what cost, and how will I know the result is good?” A strong frontier model can plan, research, write, code and use tools. A small local model can sort, extract, summarize or draft routine text without sending it to a provider. Neither removes the need to check consequential work. For most people, the sensible system is a human directing a capable cloud model for the hard steps and small, bounded local or cheaper models for repetitive work.

There is no universal winner. Model labels change; API price is only one part of cost; a model that is impressive on a benchmark may still fail your form, language, device or approval process. This guide recommends shortlists by job, explains what “open” actually means, gives a cost-per-accepted-task calculation, and proposes ten operational measures. It is a decision guide, not a claim that any product has been independently tested here.

Illustrative context: women at work in a computer lab in Cameroon. Photograph by Minette Lontsie, CC BY-SA 4.0, via Wikimedia Commons. This image does not document a particular AI deployment or event.

The technology question remains human-sized. A farmer does not need a digital sage on the roof; she needs the right local bulletin in time, in a language she trusts, and a person to call when the answer is wrong. A model's fluency is useful only when it leaves the person better able to act.

What is available now

The four named frontier systems are publicly documented by their providers, with different access arrangements. The model names below are exact API identifiers when one is published. Prices are USD per million text tokens, checked on 3 November 2026; provider rates, cache treatment, peak/off-peak windows, tool fees, taxes, service geography and account eligibility can change. Check the live rate card before committing. A product page or an agent available in one software session is not proof of public API availability; the entries here are based on provider documentation.

Official model and rate-card records checked on 3 November 2026: OpenAI models and pricing, Anthropic Opus 5.5 pricing, Google Gemini API pricing, xAI Grok 4.3 model page, Mistral model pricing, DeepSeek API pricing, and Moonshot Kimi API platform. DeepSeek's V4.1 Flash release notice records the current model update. The descriptions of model strengths above are provider statements; they are not comparative test results from this guide.

This short list is a working registry, not a permanent leaderboard. GPT-6.1 Sol and Terra sit between Astra and Luna on OpenAI's current rate card ($2/$10 and $1/$5, respectively). A cost-sensitive team should include Luna, Flash, Grok 4.3, Gemini Flash-Lite and Mistral Large 3 in an evaluation; a team with long, complex tool workflows should compare Astra, Opus 5.5 and K3 on its own tasks. Select for the workflow, not a press-release ranking. Provider benchmarks use different harnesses, effort settings, tools and fallbacks; those scores do not settle your choice.

Choose by the work and the person doing it

Treat a model as a worker with a job description, permissions and a supervisor. Do not hand a model a vague “handle everything” instruction and then count fluency as success. Use the smallest model that passes your own test set. Escalate only the uncertain or high-consequence cases.

Age rules are provider and account specific, so check current terms before giving a child access: OpenAI's ChatGPT age guidance, Google's Gemini account requirements, and Anthropic's age and safety information. School administrators and local law may add requirements.

For a mixed organization, let the domain owner set what “good” means. A teacher scores learning, a finance controller scores reconciliations, a farmer values local timing, and a small-business owner counts a customer task finished correctly. The same chatbot can be helpful in one workflow and a liability in another.

Closed, open-weight, genuinely open-source, and local

These labels describe access, not intelligence.

• Closed hosted models keep weights and much of the training process with the provider. You call a web product or API. This is the quickest route to frontier capability and avoids buying and operating accelerators. You accept provider availability, prices, data handling and product changes. Contracts and controls matter more than a generic “enterprise grade” label.
• Open-weight models let a user download parameters and often run or adapt them, subject to a license. That provides more deployment control and can enable offline processing; it does not disclose all training data or guarantee reproducibility, unlimited commercial use, or easy local inference. Kimi K3 is published under a named K3 license; inspect the actual terms. DeepSeek V4.1 Flash 1017 labels its weights MIT. Neither statement by itself verifies every supply-chain or output risk.
• Open-source AI, in the Open Source Initiative's definition, requires more than weights: the model's preferred form for modification includes data information and code used to derive the parameters, as well as architecture, parameters and inference code. Many projects marketed as “open source” are more accurately called open-weight. Evaluate the license and completeness component by component. OSI definition.
• Small/local models run on a phone, laptop or organization-controlled server. Google's Gemma 4 guide lists E2B/E4B variants for mobile/edge and approximate memory needs of 2.9 GB for the quantized E2B weights and 4.5 GB for quantized E4B, before context and runtime overhead. These are model-load estimates, not a promise that any laptop will be fast. A 4B Qwen3.5 weight release is also available under Apache 2.0. Small models are good candidates for private extraction, tagging, boilerplate and offline use; test quality on your language and data. Gemma deployment and memory guide, Qwen3.5-4B card.

Local inference means local processing after model download and setup; it does not automatically mean secure. A compromised laptop, cloud-synced folder, logging layer, plugin, remote telemetry or agent tool can still disclose information. A local model can also be wrong with no provider to correct it. Conversely, a hosted provider may offer useful contractual controls, access management and mature infrastructure that an underfunded self-hosted server cannot.

A large planner with small workers

A practical hybrid pattern is a capable hosted orchestrator for decomposition, ambiguity and review, with small or cheaper workers for bounded steps: extract invoice fields, label support tickets, summarize a known file, format a table, or run a deterministic calculation. The orchestrator should receive only the fields needed to decide or synthesize, not every raw record. Give each worker a narrow schema, a short prompt and a clear “uncertain / escalate” option.

This arrangement can lower token cost, keep repeatable work close to the data, and reserve expensive reasoning for cases where it changes the result. It can also make failure harder to see: one bad extraction multiplied across thousands of records is still a bad system; every handoff adds latency and failure modes; debugging a multi-agent chain costs staff time; and local infrastructure needs patching, monitoring, backups, access controls and someone on call. The economics improve only if the cheaper workers meet a quality threshold and the orchestration overhead stays below the savings.

Do not route sensitive data to a local worker and then send its raw output to a hosted coordinator. Redact or aggregate first. Do not let a model invent a schema and silently pass it downstream. Version prompts and model IDs, log inputs only as policy allows, and make one person accountable for the final decision. For an early deployment, begin with one workflow, one fallback route and one human approval queue.

Measure ten things that show whether it works

These are operational measures, not a claim of a globally novel framework. Define acceptance with the person who owns the work; log model version, prompt version, date, and workflow. Report slices by language, device, task type and user group. Averages conceal the cases that matter.

• 1. Accepted-outcome cost (USD/accepted task) = (model + tools + compute + allocated hardware + human review + ops across passes) ÷ accepted tasks. Include rejected attempts.
• 2. Correction burden (human minutes/accepted task) = review + rewrite + checking minutes ÷ accepted outcomes. Record median and 90th percentile; a few difficult cases can dominate.
• 3. Evidence integrity (% supported claims) = audited claims whose linked primary evidence supports the exact wording ÷ claims sampled. Report sample size and unsupported/high-impact claims separately.
• 4. Language-switch loss (percentage-point change) = acceptance rate in a user's chosen language minus acceptance rate on the same task in the team's reference language. Test code-switching and local names, not only translated prompts.
• 5. Offline continuity (% tasks completed offline) = accepted eligible tasks completed with network disconnected ÷ eligible tasks attempted offline. Record task class and device; do not average across very different tasks.
• 6. Privacy boundary crossings (events/1,000 sensitive tasks) = sensitive payloads sent beyond the approved boundary ÷ sensitive tasks × 1,000. Count raw and derived identifiers; keep incident severity separately and target zero unauthorized crossings.
• 7. Handoff tax (minutes + tokens per accepted task) = human context-reconstruction minutes and duplicated tokens across agent/model transfers, reported as two units. This exposes hidden multi-agent overhead.
• 8. Escalation closure (median minutes; % resolved) = time to accountable human resolution, plus escalations resolved within the stated service window ÷ escalations. A high escalation rate can be appropriate if high-risk cases are caught.
• 9. Access gap (percentage points) = highest-group acceptance rate minus lowest-group rate across device tier, language, disability/access mode or user group. Publish group counts; small samples need uncertainty ranges.
• 10. Safe-action yield (% guarded actions completed) = simulator or field actions that meet the goal without breaching a pre-registered hard constraint ÷ actions attempted. Also report every severe violation as a count; do not hide it inside the average. Keep privacy incidents separate as a raw count with severity and response time; never merge a breach into a benign average.

For each metric, publish a baseline before rollout, an owner, the sample size and the decision it can change. Review a small random sample of accepted work as well as every rejected or escalated case. Do not optimize a measure that rewards passing work quickly if the task requires careful review.

Cost per accepted task: a worked illustration

Token price is not job price. Consider one research-and-draft task with 50,000 input tokens and 8,000 output tokens per attempt, no cache discount, and a 75% chance that a completed attempt meets the acceptance bar. Assume each failed attempt is retried until an acceptable result; the simple geometric estimate is 1 ÷ 0.75 = 1.33 attempts per accepted task. This deliberately excludes changing prompts, tool fees, and latency variance, so it is a lower bound on real production effort.

Now add 30 minutes of human review at an assumed $20/hour = $10 per accepted output, plus an assumed $0.10 for search/tool calls and $0.05 per accepted task for logging/compute allocation. The illustrative totals become approximately $11.35 Astra, $10.63 Opus, $10.51 K3 and $10.18 Flash. This is arithmetic from stated assumptions, not a price quote or quality comparison. If Astra's own-task acceptance rate is 90%, its model spend falls to $1.00 per accepted output; if Flash is accepted only 40% of the time, model spend rises to $0.0615, while review and rework may rise much more. If a failed output still takes review time, that labor also needs to be added. Prompt caching, provider tools, currency conversion, taxes, discounts, batch rates and special context surcharges can change the result.

Generic solar-panel installation used as context for energy and hardware costs; it does not depict a specific project or event.

Image: TheUltimateGrass. CC0 1.0. Original source.

Illustrative context for the energy side of local compute costs: a generic solar-panel installation. Photograph by TheUltimateGrass, CC0 1.0, via Wikimedia Commons; not a specific project.

For a small local model, API tokens may appear free after downloading, but the cost does not disappear. Suppose a laptop/workstation costs an assumed $1,200, is useful for 36 months, and is used for AI 100 hours/month: allocate $1,200 ÷ 3,600 = $0.33 per AI hour. At an assumed 0.20 kW average draw and $0.20/kWh, electricity adds $0.04/hour. Add storage, setup, updates, downtime and the operator's time. If a task takes ten minutes of machine time and three minutes of staff checking, its allocated hardware/electricity is about six cents, but the staff review at the same $20/hour is another dollar. These illustrative inputs are not Kenyan hardware or electricity prices. Replace them with the actual quote, metered consumption and fully loaded labor rate before buying equipment.

The selection rule follows from the arithmetic: first measure acceptance and correction time. Then compare cost per accepted result. A cheap model that needs double the review can cost more than a dearer model; a local model can be worth paying for when offline access, data locality or predictable volume matters. For a one-person workflow, the simplest hosted plan may beat running a server. For a high-volume repetitive workflow, a small model can pay back—but only after it passes a representative evaluation set.

A small, model-specific sample of public conversation

These dated posts help identify questions worth testing; they do not establish general sentiment, benchmark performance or provider reliability. Subreddits self-select by product and enthusiasm, posters are not audited, comments can be deleted, and vote totals change. A few strongly worded anecdotes cannot reveal prevalence. The picks in the persona table are therefore budget-aware pilot suggestions. Where this sample does not support a task pairing, it says so.

• Opus 5.5, coding: On 22 September, one r/ClaudeAI user praised speed and interface-bug finding but explicitly worried about launch-week honeymoon effects. A 13 October r/ClaudeAI post described strong coding; replies included a user who found it poor at serious reasoning at medium effort and another who reported missed edge cases. On 22 October, a game-development user said natural-language changes had become less reliable in their existing framework. Positive and critical accounts coexist. Sep. 22 thread, Oct. 13 thread, Oct. 22 thread.
• Astra, robotics: On 11 September, a Reddit thread reposted an X user's positive claim that Astra copied a demonstrated task with a robot arm on the first pass. In a small two-model painting exercise posted 14 September, the author's informal audience preferred Claude's output; both arms did poorly. Separately, a 2026 research preprint tested eight robot configurations and reports costly demonstrations and real-world limits. None of these justify letting a general model command an unsupervised machine. Arm demonstration discussion, painting comparison, preprint.
• DeepSeek V4.1 Flash, finance: In a 25 September r/DeepSeek thread, one commenter said they use Flash at low effort for complex finance tasks and find it fast and accurate. Another commenter in an October finance/legal recommendation thread explicitly said they had not tried Flash on financial numbers and questioned spreadsheet handling. These are useful test hypotheses, not validation of calculations. Sep. 25 discussion, finance/legal question.
• Kimi K3, contracts and research: A July/August r/claude thread has one user reporting detailed proposal and contract-fulfillment specs from K3 agents, and another saying K3 found an edge case in specifications but used extra deliberation. This is project-contract work, not legal research. An r/LocalLLaMA user reported K3 found five reproducible bugs in a cryptography project after other models missed them; a different developer reported a long drawing task failed after timeouts and exhausted balance. I found no direct, credible user report in this search sample that establishes K3's legal-research quality. Project/contract discussion, security review, failed task and cost.
• Local inference economics: In an October 2026 r/LocalLLaMA post, a user argued self-hosting can take a team and may not save money. It is a useful cost checklist, not a general cost study. Discussion.

The practical conclusion is narrow: use those reports to design a local evaluation set—coding edge cases, robot safety constraints, spreadsheet calculations, contract clause extraction, retries and actual bills. Do not promote any model-task pairing as established by Reddit sentiment. For local audiences, the one Kenya work thread found during this audit expressed uncertainty about displacement, but its few votes and one participant cannot show how common that concern is. r/Kenya thread, 7 September 2026.

Which AI questions are people actually searching for?

Search queries reveal the jobs people want AI to do. Google’s U.S. AI search trends page ranks “best AI for coding,” “best AI for writing,” “best AI for math,” “best AI for image generation” and “best AI for writing essays” as its top five “best AI for…” searches. That is a practical map of demand: people are comparing tools to solve specific problems. The list is U.S.-scoped, and Google’s page does not state its aggregation window beside the ranking, so this is a published list retrieved on 3 November 2026 with an unspecified ranking window. Google Trends’ AI search hub

The same distinction matters when looking at model names. In Google’s 2025 global Year in Search list, Gemini ranked first and DeepSeek sixth among the year’s trending searches. “Trending” means searches that rose notably during the year; it does not mean the two most searched models, nor does it measure use or quality. Google’s 2025 global list

For Kenya, Omdia’s March 2026 report, based on its analysis of Google Trends, places ChatGPT seventh among 2025 searches in Kenya and reports a 100% year-on-year increase; it places “AI” 24th, up 50%. These are Omdia’s reported figures; its underlying Google export was not independently reproduced. Separately, Business Daily on 26 April 2026 reported Google-supplied search-trend growth of 16,720% for “AI agents,” 1,010% for AI literacy and 1,230% for prompting tools in Kenya over the previous year. Such steep percentages describe reported growth in search interest, not the number of searches; a small starting base can produce a dramatic percentage. Omdia’s commissioned report, p. 13 · Business Daily, 26 April 2026

What should you compare when choosing? Start with your own job: coding, research, writing, mathematics, image creation, study or automation. Search for a model’s exact name plus the task, then check whether it can do the work reliably, what it costs, whether its limits fit your workflow and how it handles your data. “Best” searches show comparison intent; they do not establish a winner. A model’s popularity in search is a clue about attention, not proof of capability.

Google’s direct Explore/API comparison remained rate-limited during this check. The published evidence above was recovered through Google’s accessible editorial pages and attributed research. Fresh Kenya-versus-worldwide scores for the four named model versions remain unavailable.

Sources and checking notes

Provider prices and model availability above were checked against official OpenAI, Anthropic, DeepSeek and Moonshot pages on 3 November 2026. Vendor capability statements are not independent rankings. DeepSeek and Kimi weights are not treated as easy laptop deployments. The OSI definition distinguishes open-source AI from open weights. Google’s memory estimates exclude extra context/runtime needs. Age guidance summarizes provider terms; local law and account features vary. Public comments are a small, dated sample. Search evidence above separates published Google rankings, Omdia’s analysis and newspaper reporting, with their dates and geography. Growth, popularity and capability are evaluated separately.

Continue exploring

AI Jobs in Africa: Who Benefits When Work Is Automated?. AI Companions and Mental Health: A Test to Protect Attention.

Cover: Women working at computers in Cameroon. Photo by Minette Lontsie, CC BY-SA 4.0 via Wikimedia Commons. Credit: Minette Lontsie. CC BY-SA 4.0. Original source.