<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tokely — AI API Platform</title>
    <description>The latest articles on DEV Community by Tokely — AI API Platform (@tokely).</description>
    <link>https://dev.to/tokely</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4199825%2Fbcfa7e9c-26dd-4a89-91ef-f2401cfe718f.png</url>
      <title>DEV Community: Tokely — AI API Platform</title>
      <link>https://dev.to/tokely</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tokely"/>
    <language>en</language>
    <item>
      <title>AI Agents Found a Maya Site in 72 Hours. Archaeologists Had Been There First</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Thu, 12 Nov 2026 14:01:57 +0000</pubDate>
      <link>https://dev.to/tokely/ai-agents-found-a-maya-site-in-72-hours-archaeologists-had-been-there-first-39e0</link>
      <guid>https://dev.to/tokely/ai-agents-found-a-maya-site-in-72-hours-archaeologists-had-been-there-first-39e0</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; On October 18, Pietro Miotti was traveling in Peru and reading about Hiram Bingham, the explorer who reached Machu Picchu in 1911. He wondered what Bingham would have done with today's tools. That night he pointed a group of AI agents at public NASA lidar data and went to bed. By October 21 he had an official reply from the Mexican government about a Maya site hidden under the jungle.&lt;/p&gt;

&lt;p&gt;Then, on November 11, he added an update to the top of &lt;a href="https://pietromiotti.com/latest/maya-site" rel="noopener noreferrer"&gt;his post&lt;/a&gt;: archaeologists had already mapped the place. The story still climbed to the top of Hacker News with more than 1,000 points. Both halves deserve attention: what the agents pulled off, and the one step where they failed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened in those 72 hours?
&lt;/h2&gt;

&lt;p&gt;Miotti is not an archaeologist, and he says so. He asked Gemini, ChatGPT, Claude and Grok how a modern Bingham would look for ruins, and all of them gave the same answer: lidar. From a satellite, a ruin in the jungle is just trees. Lidar fires laser pulses through the gaps in the canopy and maps the ground underneath.&lt;/p&gt;

&lt;p&gt;Peru has little public lidar coverage, so he switched to the Maya region, which has much more. He asked the agents to analyze it overnight. In the morning the reports listed villages and other regular shapes that looked like structures. He asked which of them had not been discovered yet, and after a search of the literature and the archives the answer came back: one major village did not seem to be registered.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffmd4v6l7cml0spjjlcrn.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffmd4v6l7cml0spjjlcrn.jpg" alt="An envelope with a wax seal flying along a dotted path from a laptop on a desk to a columned government building, a clock above the path" width="800" height="447"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;From an idea on October 18 to an official reply from Mexico's INAH on October 21, according to Pietro Miotti's diary of the project.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The agents also told him what to do next: write a report and send it to INAH, Mexico's National Institute of Anthropology and History. They supplied the reporting steps and the email addresses, and Claude suggested translating the report into Spanish, a language Miotti does not speak. INAH replied that no registered archaeological site was identified at the location in his report.&lt;/p&gt;

&lt;h2&gt;
  
  
  How did 48 agents search 1,200 km² of jungle?
&lt;/h2&gt;

&lt;p&gt;With no special tooling. The lidar strips, about 1,200 km² of forest, were turned into images, and 48 agents went through them one by one, looking for pyramids, platforms and plazas while filtering out natural hills, sinkholes and roads. In Miotti's words: "There was no special model or classifier involved: the agents literally looked at the pictures, following a precise guide."&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvscca8o0vztv2ewtx0k0.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvscca8o0vztv2ewtx0k0.jpg" alt="Small robots with magnifying glasses walking over a large grid of terrain map tiles, one robot in a circled tile raising a flag" width="800" height="447"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;48 agents went through images of about 1,200 km² of lidar data one by one, following a written guide.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;That is the part worth copying. A huge search became thousands of small, identical visual checks, each one run against the same written rules. No single check needs a genius. It needs patience, and patience is what a fleet of agents has.&lt;/p&gt;

&lt;p&gt;There was a second pass, too. The agents went back to the raw point cloud to make sure the shapes were really on the ground and not created by the trees. Under 10 to 17 m of forest, the ground points traced the same plaza, pyramid and courtyard.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did they find under the trees?
&lt;/h2&gt;

&lt;p&gt;A hilltop on the edge of a cliff with straight edges and sharp corners. As Miotti puts it, "Nature doesn't really do straight lines."&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdeu8crn6p94yajb6csa5.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdeu8crn6p94yajb6csa5.jpg" alt="A survey plane firing laser lines through a jungle canopy onto a stepped pyramid, a plaza and platforms on a hilltop at the edge of a cliff" width="800" height="447"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Lidar pulses pass through gaps in the canopy and map the ground below. Illustration, not the real site.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Zoomed in, the lidar shows a levelled plaza, an oval pyramid at least 8 to 12 m tall, a raised courtyard attached to it and a flat-bottomed hollow that might have been a rainwater reservoir. Miotti marks the interpretation as speculation from a long chat with the agents: probably a small Maya civic centre from the Classic period, roughly AD 250 to 900. About the reservoir he adds: "Or it's just a hole."&lt;/p&gt;

&lt;p&gt;One careful detail: the exact coordinates went to INAH in a confidential annex and are not in the post.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why is it a rediscovery and not a discovery?
&lt;/h2&gt;

&lt;p&gt;Because the site is already in the scientific literature. According to Miotti's update, it was mapped in &lt;a href="https://doi.org/10.1016/j.jasrep.2025.105288" rel="noopener noreferrer"&gt;Estrada-Belli et al. 2025&lt;/a&gt;, a study of settlements across the Maya lowlands. The agents missed that paper during their literature check. INAH's register did not have the site yet, so both statements are true at once: it was absent from the official register, and it was not new.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7gsf0g6hr6v3btfvcvmx.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7gsf0g6hr6v3btfvcvmx.jpg" alt="A robot with a magnifying glass studying an old map where a pyramid is already circled, with an unopened book on the shelf behind it" width="800" height="447"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;The site was already mapped in Estrada-Belli et al. 2025. The agents missed the paper in their literature check.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Here is the irony. The step that sounds impossible, spotting a pyramid under 17 m of forest somewhere in 1,200 km², went fine. The step that sounds routine, checking whether somebody got there first, is where the agents slipped. Anyone who has asked an agent "has this been done before?" should remember this case. When an agent reports that it found nothing, that is a statement about its search, not about the world.&lt;/p&gt;

&lt;p&gt;The method itself is the one professionals use. Miotti points to &lt;a href="https://doi.org/10.15184/aqy.2024.148" rel="noopener noreferrer"&gt;Auld-Thomas et al. 2024&lt;/a&gt;, where archaeologists found a whole Maya city in Mexico in lidar that had been collected for environmental research. His own conclusion is generous to both sides: "an outsider with agents ended up in a similar place to the experts."&lt;/p&gt;

&lt;h2&gt;
  
  
  What did Hacker News argue about?
&lt;/h2&gt;

&lt;p&gt;The thread passed 370 comments, and it was not all applause. Someone coined "vibe archeology" within hours. Skeptics said they would wait for an archaeologist to verify the claim, because agents are good at producing findings that sound groundbreaking and collapse on review. The November 11 update proved that instinct half right.&lt;/p&gt;

&lt;p&gt;Others worried about the receiving end. Open-source maintainers already complain about floods of AI-written reports, and archaeologists could be next. The most serious point was about capacity: finding a site is now cheaper than protecting it. If agents surface hundreds of candidates, there will be more than archaeologists can excavate or guard, and looters do not wait for permits. That makes the confidential annex look like the smartest decision in the whole story.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can you run a search like this yourself?
&lt;/h2&gt;

&lt;p&gt;The recipe is simple enough to reuse far outside archaeology. Take a large public dataset that can be rendered as images. Write a precise guide: what counts as a hit and what the usual false positives look like. Fan the tiles out to many agents in parallel. Send every hit to a second pass against the raw data. Then treat the "is this new?" answer as a lead, and put it in front of a human expert before you call it a discovery.&lt;/p&gt;

&lt;p&gt;The bill is mostly image input, so the model choice matters. A cheap vision model can do the first sweep over every tile, and a stronger one can recheck only the tiles that were flagged. On Tokely, vision models from different developers sit behind one OpenAI-compatible key, so a two-tier pass like this is a change of model name in the request. The current list is on the &lt;a href="https://tokely.me/models" rel="noopener noreferrer"&gt;models page&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Miotti ends his post with a proposal: "we should probably lidar the whole planet and let the agents discover the rest." Maybe. For now the site is with INAH and with the archaeologists who mapped it first, which is exactly where a find like this belongs.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/ai-agents-maya-site-lidar" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>llm</category>
      <category>news</category>
    </item>
    <item>
      <title>Claude Fable 5.2: 1,000 Agents, 30 Hours and a 20% Price Cut. What Actually Changed</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Tue, 10 Nov 2026 10:09:36 +0000</pubDate>
      <link>https://dev.to/tokely/claude-fable-52-1000-agents-30-hours-and-a-20-price-cut-what-actually-changed-4f4i</link>
      <guid>https://dev.to/tokely/claude-fable-52-1000-agents-30-hours-and-a-20-price-cut-what-actually-changed-4f4i</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; It took an unreleased research version of Claude 11 days to formalize the proof of Fermat's Last Theorem. On November 9, Anthropic said a team of 1,000 Claude Fable 5.2 agents did it in 30 hours, with minimal human help. The same day, the price of the model dropped by 20%.&lt;/p&gt;

&lt;p&gt;That is the headline. The details are more interesting: where Fable 5.2 actually jumped, what Anthropic still keeps behind a door, which of your requests may be answered by a different model, and why the real discount for agent work is bigger than 20%.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did Anthropic ship on November 9?
&lt;/h2&gt;

&lt;p&gt;Two models. Claude Fable 5.2 (API ID &lt;code&gt;claude-fable-5-2&lt;/code&gt;) is open to every developer on the Claude API, Amazon Bedrock, Google Cloud and Microsoft Foundry. Claude Mythos 5.2 has the same price but goes only to organizations verified through Anthropic's Cyber Verification Program and Life Sciences Verification Program.&lt;/p&gt;

&lt;p&gt;Both keep a 1M-token context window, up to 128K output tokens and a June 2026 knowledge cutoff. Anthropic says both generate output up to 30% faster than the 5.1 models. Fable 5.1 does not disappear: it is now a legacy model, with retirement no sooner than September 1, 2027.&lt;/p&gt;

&lt;p&gt;The release landed shortly before Anthropic's planned IPO, which is how CNBC framed it. For developers, the timing matters less than what changed in the model and in the bill.&lt;/p&gt;

&lt;h2&gt;
  
  
  How did 1,000 agents formalize Fermat's Last Theorem in 30 hours?
&lt;/h2&gt;

&lt;p&gt;The proof was written in Lean, a programming language for mathematics where every step has to check. According to Anthropic, Fable 5.2 started from minimal prompts, built its own ways to coordinate, and used no mathematical references, only a list of intermediate theorem statements to score progress.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcjr3yhjsbu6lfjbjglzz.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcjr3yhjsbu6lfjbjglzz.jpg" alt="Hundreds of small robots on scaffolding and ladders inspecting a giant x^n + y^n = z^n equation with magnifying glasses, a clock reading 30 hours in the corner" width="800" height="447"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;About 1,000 Fable 5.2 agents formalized the proof of Fermat's Last Theorem in Lean in 30 hours, according to Anthropic. A single run, not a benchmark.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The comparison is the striking part. Opus 5.5, run with the same setup of about 1,000 agents, completed only 26% of the formalization in 18 hours and, in Anthropic's words, barely made any more progress after 30. Both lines come from a single run per model, so treat it as a demonstration, not a benchmark.&lt;/p&gt;

&lt;p&gt;The lesson for anyone building agents: the gain shows up when a model has to keep a long, shared plan alive across many workers. That is exactly where the previous models stalled.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where did Fable 5.2 actually get better?
&lt;/h2&gt;

&lt;p&gt;Not evenly. On the coding benchmarks most people quote, the jump is solid but not dramatic: FrontierSWE v2 went from 56.3% on Fable 5.1 to 69.9%, and OSWorld 2.1 from 83.5% to 89.3%. Humanity's Last Exam with tools rose from 65.6% to 74.2%.&lt;/p&gt;

&lt;p&gt;The big moves are in long, messy, real work. On the Remote Labor Index, Fable 5.2 scored 41.3% at high effort against 17.9% for Fable 5.1, more than double. On RoboDojo, where a model controls a simulated two-arm robot from camera images, it scored 64.9% against 27.6% for Fable 5.1 and 29.8% for GPT-6 Astra.&lt;/p&gt;

&lt;p&gt;All of these numbers are reported by Anthropic. They still tell a clear story: Fable 5.2 is less a better autocomplete and more a better worker on tasks that run for hours.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is Mythos 5.2, and why can't you use it?
&lt;/h2&gt;

&lt;p&gt;Mythos 5.2 is the same generation built for dual-use domains: security research and biology. Anthropic says it found 10.2% more vulnerabilities than Opus 5.5 and 14.4% more than Mythos 5.1, and it scored 89.6% on CVE Rediscovery against 78.3% for Mythos 5.1.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fek1f0ghp4ewkux8qxihz.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fek1f0ghp4ewkux8qxihz.jpg" alt="A huge bank vault door half open with light pouring out, a person holding an ID badge in front of it, a velvet rope and a VERIFIED stamp" width="800" height="447"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Claude Mythos 5.2 is available only to organizations verified through Anthropic's Cyber and Life Sciences programs.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;That capability is the reason for the door. Access requires verification, and even fast mode for Mythos 5.2 is limited to members of the verification programs. Claude Enterprise customers can reach it through Claude Security. Everyone else gets Fable 5.2.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which of your requests get answered by another model?
&lt;/h2&gt;

&lt;p&gt;Here is the detail most launch coverage skipped. Fable 5.2 runs safety classifiers on cybersecurity and biology topics. When a query is blocked, Anthropic says the user receives a response from Opus 4.8 for cybersecurity and from Opus 5 for biology. A small set of AI research topics also falls back to Opus 5.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9au2sak96gr7wdnkcck1.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9au2sak96gr7wdnkcck1.jpg" alt="A train approaching a railway switch while a hand-operated lever in the foreground is thrown to divert it onto a side track" width="800" height="447"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;When a classifier blocks a query, Anthropic says the answer comes from Opus 4.8 (cybersecurity) or Opus 5 (biology).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Anthropic calls these fallbacks transparent and reports about 55% fewer blocks than Fable 5.1 in early testing across claude.ai, Claude Code and Cowork. If you build security or bio tooling on the API, read Anthropic's &lt;a href="https://platform.claude.com/docs/en/build-with-claude/refusals-and-fallback" rel="noopener noreferrer"&gt;refusals and fallback guide&lt;/a&gt; before you assume every answer came from Fable 5.2.&lt;/p&gt;

&lt;p&gt;Two more fine-print items. Fable 5.2 requires 30-day data retention and is not available under zero data retention unless Anthropic expressly authorizes it. And fast mode, which Anthropic says speeds generation up to 2.5 times, costs twice the standard price.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much cheaper is it, really?
&lt;/h2&gt;

&lt;p&gt;On the price list, exactly 20%. Fable 5.2 costs $8 per 1M input tokens and $40 per 1M output tokens, against $10 and $50 for Fable 5.1. Cache reads cost $0.20 per 1M tokens, the Batch API halves the price to $4 and $20, and there is no surcharge for long prompts anywhere in the 1M window.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F10l7xnmppk04zqos7alu.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F10l7xnmppk04zqos7alu.jpg" alt="A paper price tag reading -20% being cut by a large pair of scissors, a strip of the tag falling away" width="800" height="447"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Fable 5.2 lists at $8 input and $40 output per 1M tokens, 20% below Fable 5.1.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;For agents, the cut is deeper because of what we call the Cache Gap. GPT-6 Astra lists at $10 and $50, only 20% above Fable 5.2, but charges $1.00 per 1M cached tokens, five times more. Agent tools resend the same context every turn, so most input is cached. In our calculation of a cache-heavy coding session, Fable 5.2 costs $17.44 and Astra $27.20, a 35.9% difference. The full breakdown is in our &lt;a href="https://tokely.me/blog/claude-fable-5-2-pricing-2026" rel="noopener noreferrer"&gt;Claude Fable 5.2 pricing study&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It is still a premium model. The same session costs $9.44 on Claude Opus 5.5, so Fable 5.2 runs 1.85 times the price. On Tokely, Fable 5.2 lists at $6 input and $30 output per 1M tokens.&lt;/p&gt;

&lt;h2&gt;
  
  
  Should you switch?
&lt;/h2&gt;

&lt;p&gt;If you run long agent jobs, multi-step research or anything that has to hold a plan for hours, yes. That is where the Remote Labor Index and the Fermat run say Fable 5.2 pulls away, and it costs less than the model it replaces.&lt;/p&gt;

&lt;p&gt;If most of your traffic is short chat turns or routine code edits, Opus 5.5 or Sonnet 5.5 will do the job for a fraction of the cost. A practical setup routes everyday turns to the cheaper model and sends only the hardest tasks to Fable 5.2. Keep fast mode for the moments when a person is waiting.&lt;/p&gt;

&lt;p&gt;If you work in security or biology, test your real prompts first. Some answers may come from Opus 4.8 or Opus 5, and that changes what you are actually buying.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/claude-fable-5-2-what-changed" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>claude</category>
      <category>news</category>
    </item>
    <item>
      <title>Claude Fable 5.2 Pricing: What the 20% Cut Means per Task vs Fable 5.1, Opus 5.5 and GPT-6 Astra</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Tue, 10 Nov 2026 09:47:40 +0000</pubDate>
      <link>https://dev.to/tokely/claude-fable-52-pricing-what-the-20-cut-means-per-task-vs-fable-51-opus-55-and-gpt-6-astra-3fhd</link>
      <guid>https://dev.to/tokely/claude-fable-52-pricing-what-the-20-cut-means-per-task-vs-fable-51-opus-55-and-gpt-6-astra-3fhd</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Research scope:&lt;/strong&gt; This study compares official list prices on the Anthropic, OpenAI and Google pricing pages, read on November 10, 2026, one day after Claude Fable 5.2 was released. Workload costs are calculated from those list prices and a stated token mix (a short chat turn, one 400K-token prompt and a cache-heavy coding agent session); they are not measured invoices. Benchmark scores are vendor-reported by Anthropic.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Claude Fable 5.2 costs $8 for input and $40 for output per 1M tokens, exactly 20% below Claude Fable 5.1 rates of $10 and $50. Cache reads run at $0.20 per 1M tokens, creating the Cache Gap that makes a long coding agent session 35.9% cheaper than GPT-6 Astra. Even with that discount, Fable 5.2 still costs 1.85 times as much as Claude Opus 5.5 for typical agent workloads.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did Anthropic change on November 9?
&lt;/h2&gt;

&lt;p&gt;Anthropic released Claude Fable 5.2 and Claude Mythos 5.2 on November 9, 2026. Fable 5.2 uses the API identifier claude-fable-5-2 and is available to all developers on the Claude API, Amazon Bedrock, Google Cloud, and Microsoft Foundry. Mythos 5.2 carries the same list prices as Fable 5.2, but Anthropic restricts its access to organizations verified through specific programs such as the Cyber Verification Program and the Life Sciences Verification Program.&lt;/p&gt;

&lt;p&gt;Both models maintain a 1M-token context window, support a maximum output of 128K tokens, and have a knowledge cutoff of June 2026. Anthropic states that both versions generate output up to 30% faster than the 5.1 generation. Developers using Fable 5.1 do not face an immediate cutoff, as Anthropic will keep Fable 5.1 available as a legacy model until at least September 1, 2027.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much does Claude Fable 5.2 cost?
&lt;/h2&gt;

&lt;p&gt;Claude Fable 5.2 standard tier pricing sits at $8 per 1M input tokens and $40 per 1M output tokens, compared to $10 and $50 for Fable 5.1. Anthropic set cache read pricing at $0.20 per 1M tokens, down from $0.25 on Fable 5.1. Cache write pricing dropped in equal measure, moving to $10 per 1M tokens for 5-minute writes and $16 per 1M tokens for 1-hour writes, compared to $12.50 and $20 on the prior release.&lt;/p&gt;

&lt;p&gt;The Batch API offers half-price execution at $4 per 1M input tokens and $20 per 1M output tokens. For interactive applications that need lower latency, fast mode costs $16 per 1M input tokens and $80 per 1M output tokens. Anthropic states that fast mode speeds output generation up to 2.5 times, but developers cannot combine fast mode with the Batch API discount.&lt;/p&gt;

&lt;p&gt;Every listed price point for Fable 5.2 sits exactly 20% below the equivalent tier on Fable 5.1. Anthropic does not charge a long-context surcharge, meaning requests that use the entire 1M-token window bill at the base $8 and $40 rates. For developers using external gateway routing, Tokely lists Fable 5.2 at $6 input and $30 output per 1M tokens.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does that compare with GPT-6 Astra, Opus 5.5 and the rest?
&lt;/h2&gt;

&lt;p&gt;The frontier tier splits into two clear price brackets across the primary model providers. Claude Fable 5.2 lists at $8 input, $40 output, and $0.20 for cache reads per 1M tokens, while GPT-6 Astra lists at $10 input, $50 output, and $1.00 for cache reads. Claude Fable 5.1 remains listed at $10 input, $50 output, and $0.25 cache reads, matching Astra on raw input and output base rates.&lt;/p&gt;

&lt;p&gt;Beneath the top tier, Claude Opus 5.5 lists at $4 input, $20 output, and $0.20 cache reads per 1M tokens. The mid-tier options run lower still: Claude Sonnet 5.5 lists at $2 input, $10 output, and $0.10 cache reads, matching GPT-6.1 Sol at $2 input, $10 output, and $0.10 cache reads. Gemini 4 Argon currently lists at an introductory price of $2 input, $10 output, and $0.10 cache reads, but Google stated this price will double to $4 input, $20 output, and $0.20 cache reads on December 1, 2026.&lt;/p&gt;

&lt;p&gt;These list prices make Fable 5.2 the cheapest of the two top-priced flagships by 20% on input and output. At the same time, Fable 5.2 remains exactly twice the list price of Opus 5.5 for uncached tokens. How those differences translate to production invoices depends directly on how each platform bills cached context.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F52ukhz6qtajhm8qt2w1g.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F52ukhz6qtajhm8qt2w1g.png" alt="Paired bars. Claude Fable 5.2: input $8, output $40; Claude Fable 5.1: input $10, output $50; Claude Opus 5.5: input $4, output $20; Claude Sonnet 5.5: input $2, output $10; GPT-6 Astra: input $10, output $50; GPT-6.1 Sol: input $2, output $10; Gemini 4 Argon: input $2, output $10." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Standard-tier list prices per 1M tokens on official pricing pages, read November 10, 2026. Gemini 4 Argon is shown at its introductory price, which doubles on December 1, 2026.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Cache Gap
&lt;/h2&gt;

&lt;p&gt;The pricing difference between flagships expands significantly when evaluating prompt caching mechanisms. We define "the Cache Gap" as follows: Claude Fable 5.2 and GPT-6 Astra differ by 20% on list input and output prices ($8 vs $10 input, $40 vs $50 output per 1M tokens), but Fable 5.2 reads cached tokens at $0.20 per 1M against $1.00 for Astra, five times less. In a cache-heavy coding agent session the bill differs by 35.9% ($17.44 vs $27.20), not 20%, because cache reads are 26.5% of the Astra bill and 8.3% of the Fable 5.2 bill.&lt;/p&gt;

&lt;p&gt;Cache read rates vary widely across model catalogs. GPT-6 Astra charges $1.00 per 1M tokens, Fable 5.1 charges $0.25, Fable 5.2 charges $0.20, and Opus 5.5 charges $0.20. Lower down the stack, Sonnet 5.5, GPT-6.1 Sol, and Gemini 4 Argon all bill cache reads at $0.10 per 1M tokens.&lt;/p&gt;

&lt;p&gt;Anthropic bills cache reads on Fable models at 0.025 times base input, while OpenAI bills Astra cache reads at 0.1 times base input. Because agent tools resend the entire accumulated context on every turn, cached input tokens account for the vast majority of tokens processed during an extended workflow. The cache read multiplier therefore has a much larger impact on multi-turn costs than the headline input price.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F21gwn0wzteno48abl0yr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F21gwn0wzteno48abl0yr.png" alt="Horizontal bars. GPT-6 Astra: $1.00; Claude Fable 5.1: $0.25; Claude Fable 5.2: $0.20; Claude Opus 5.5: $0.20; Claude Sonnet 5.5: $0.10; GPT-6.1 Sol: $0.10; Gemini 4 Argon: $0.10." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Price of reading 1M cached input tokens, standard tier, prompts below the long-context threshold.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What does a coding agent session cost?
&lt;/h2&gt;

&lt;p&gt;To see how these rates interact, consider an illustrative coding agent session processing 8M total input tokens across approximately 50 requests of 160K tokens each. All requests stay below OpenAI's 272K-token threshold for long-context billing. The session assumes a 90% cache read rate (7.2M tokens read from cache), 0.8M tokens written to cache, and 200K total output tokens generated.&lt;/p&gt;

&lt;p&gt;Under this workload, GPT-6 Astra generates a total cost of $27.20. That bill consists of $10.00 in cache writes (using OpenAI's 30-minute write rate of $12.50 per 1M tokens), $7.20 in cache reads, and $10.00 in output tokens. Claude Fable 5.1 runs at $21.80 for the identical session, because every one of its rates is 25% higher than on Fable 5.2.&lt;/p&gt;

&lt;p&gt;Claude Fable 5.2 completes this session for $17.44. The cost breaks down into $8.00 in 5-minute cache writes, $1.44 in cache reads, and $8.00 in output tokens. Claude Opus 5.5 costs $9.44 for the same session, while Claude Sonnet 5.5 and GPT-6.1 Sol cost $4.72 each. Gemini 4 Argon, which has implicit caching only and no write fee, totals $4.32 at its introductory rate and $8.64 from December 1.&lt;/p&gt;

&lt;p&gt;Comparing totals reveals that Fable 5.2 is 20.0% cheaper than Fable 5.1 and 35.9% cheaper than Astra. The Cache Gap explains why the savings against Astra exceed the 20% base price delta. Despite this drop, Fable 5.2 still bills at 1.85 times the cost of Opus 5.5 for agent workloads.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd83phs5kr7l51c9v8f7c.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd83phs5kr7l51c9v8f7c.png" alt="Stacked bars. GPT-6 Astra: $27.20 (cache writes $10.00, cache reads $7.20, output $10.00); Claude Fable 5.1: $21.80 (cache writes $10.00, cache reads $1.80, output $10.00); Claude Fable 5.2: $17.44 (cache writes $8.00, cache reads $1.44, output $8.00); Claude Opus 5.5: $9.44 (cache writes $4.00, cache reads $1.44, output $4.00); Claude Sonnet 5.5: $4.72 (cache writes $2.00, cache reads $0.72, output $2.00); GPT-6.1 Sol: $4.72 (cache writes $2.00, cache reads $0.72, output $2.00); Gemini 4 Argon: $4.32 (cache writes $1.60, cache reads $0.72, output $2.00)." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Calculated at list prices for a stated workload: 0.8M tokens written to cache, 7.2M read from cache and 200K output tokens over about 50 requests of 160K tokens. Not a measured bill.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What about one huge prompt?
&lt;/h2&gt;

&lt;p&gt;Workloads that send a large standalone context without caching produce a completely different cost spread. Consider a workload consisting of a single 400K-token prompt yielding a 2K-token answer with zero cache reuse. This mirrors large document analysis, code repository ingestion or bulk data extraction.&lt;/p&gt;

&lt;p&gt;OpenAI enforces a long-context surcharge on requests where input exceeds 272K tokens, billing the entire request at $20 per 1M input tokens and $75 per 1M output tokens for Astra. Anthropic applies no surcharge, billing Fable 5.2 at the base $8 input and $40 output rates. As a result, GPT-6 Astra costs $8.15 for this single request, while Claude Fable 5.2 costs $3.28.&lt;/p&gt;

&lt;p&gt;Fable 5.1 costs $4.10 for the same prompt, while Claude Opus 5.5 costs $1.64. GPT-6.1 Sol reaches $1.63, Claude Sonnet 5.5 totals $0.82, and Gemini 4 Argon bills at $0.82 under introductory rates. Because OpenAI doubles Astra input rates past 272K tokens, Astra ends up costing 2.48 times as much as Fable 5.2 for this 400K-token prompt.&lt;/p&gt;

&lt;p&gt;For standard conversational turns, the differences scale down linearly. A short chat turn of 3K input tokens and 1K output tokens costs $0.064 on Fable 5.2 compared to $0.080 on both Astra and Fable 5.1. Claude Opus 5.5 processes that same short turn for $0.032.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fx0hmrunlly2xj98kpr8s.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fx0hmrunlly2xj98kpr8s.png" alt="Horizontal bars. GPT-6 Astra: $8.15; Claude Fable 5.1: $4.10; Claude Fable 5.2: $3.28; Claude Opus 5.5: $1.64; GPT-6.1 Sol: $1.63; Claude Sonnet 5.5: $0.82; Gemini 4 Argon: $0.82." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;One 400K-token prompt with a 2K-token answer and no cache. OpenAI bills the whole request at long-context rates above 272K input tokens; Anthropic and Google charge no surcharge for these models.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Is Fable 5.2 worth twice the price of Opus 5.5?
&lt;/h2&gt;

&lt;p&gt;Deciding between Fable 5.2 and Opus 5.5 requires comparing benchmark accuracy against the 1.85 cost ratio seen in agent tasks. All benchmark scores cited here are vendor-reported by Anthropic in their model release documentation. The evaluations compare Fable 5.2, Fable 5.1, Opus 5.5, and GPT-6 Astra on identical software engineering and agentic benchmarks.&lt;/p&gt;

&lt;p&gt;On FrontierSWE v2, Fable 5.2 scores 69.9%, compared to 56.3% for Fable 5.1, 62.3% for Opus 5.5, and 65.5% for GPT-6 Astra. On OSWorld 2.1, Fable 5.2 achieves 89.3%, while Fable 5.1 records 83.5%, Opus 5.5 reaches 87.2%, and Astra scores 79.5%. On FrontierCode 2.0, Fable 5.2 reaches 49.1%, leading Opus 5.5 at 45.5%, Astra at 42.8%, and Fable 5.1 at 32.4%.&lt;/p&gt;

&lt;p&gt;On Humanity's Last Exam with tools, Fable 5.2 scores 74.2%, ahead of Opus 5.5 at 67.7%, Fable 5.1 at 65.6%, and Astra at 57.2%. Overall, Fable 5.2 leads Opus 5.5 by 7.6 percentage points on FrontierSWE v2 and by 2.1 points on OSWorld 2.1. Engineering leads must weigh whether that 7.6-point gain on complex software tasks justifies paying 1.85 times the agent session price.&lt;/p&gt;

&lt;p&gt;A practical routing split can balance performance and expenditure across high-volume pipelines. Developers can deploy Opus 5.5 or Sonnet 5.5 for routine turns and basic triage, reserving Fable 5.2 for the hardest coding or orchestration steps. Offline jobs can use Fable 5.2 on the Batch API at $4 input and $20 output, while fast mode should remain restricted to latency-critical user-facing paths because it doubles standard prices to $16 input and $80 output.&lt;/p&gt;

&lt;h2&gt;
  
  
  Methodology and limitations
&lt;/h2&gt;

&lt;p&gt;All prices in this analysis reflect official list prices retrieved on November 10, 2026, from the Anthropic pricing page (platform.claude.com/docs/en/about-claude/pricing), the OpenAI pricing page (developers.openai.com/api/docs/pricing), and the Google AI Studio pricing page (aistudio.google.com/docs/pricing). Model details and benchmark scores come from Anthropic's announcement page (anthropic.com/claude-fable-and-mythos-5-2).&lt;/p&gt;

&lt;p&gt;The workload figures represent calculated costs based on stated token distributions rather than measured production invoices. Real production sessions will vary based on prompt cache hit rates, average output length, and variance in prompt formatting. Token counts can also vary between models completing the exact same task, particularly because thinking tokens are billed at standard output rates.&lt;/p&gt;

&lt;p&gt;Gemini 4 Carbon appears in Anthropic's published benchmark tables but does not have a public price listed on Google's AI Studio pricing page, so it was excluded from this cost comparison. All calculations exclude regional routing or data-residency uplifts, which add a 10% premium at both Anthropic and OpenAI.&lt;/p&gt;

&lt;h2&gt;
  
  
  Data and citation
&lt;/h2&gt;

&lt;p&gt;The underlying dataset tracks every standard rate, cache read price, cache write schedule, and long-context billing rule across all compared frontier models. It includes the calculated cost of the agent session, the single 400K-token prompt and the short chat turn for each model, with a source link to each provider pricing page.&lt;/p&gt;

&lt;p&gt;Cite this analysis as: Tokely, "Claude Fable 5.2 Pricing: What the 20% Cut Means per Task", November 10, 2026, &lt;a href="https://tokely.me/blog/claude-fable-5-2-pricing-2026" rel="noopener noreferrer"&gt;https://tokely.me/blog/claude-fable-5-2-pricing-2026&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/claude-fable-5-2-pricing-2026" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>claude</category>
      <category>programming</category>
    </item>
    <item>
      <title>How Often Do AI Labs Ship New Models? Release Cadence of OpenAI, Anthropic, Google, DeepSeek and Mistral (2024-2026)</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Tue, 10 Nov 2026 08:37:28 +0000</pubDate>
      <link>https://dev.to/tokely/how-often-do-ai-labs-ship-new-models-release-cadence-of-openai-anthropic-google-deepseek-and-6m8</link>
      <guid>https://dev.to/tokely/how-often-do-ai-labs-ship-new-models-release-cadence-of-openai-anthropic-google-deepseek-and-6m8</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Research scope:&lt;/strong&gt; This study counts releases listed in the official API changelogs of OpenAI, Anthropic, Google, DeepSeek and Mistral, read on November 10, 2026. Each date is the first day a new text model name appeared in the API (experimental, preview or generally available), January 2024 to October 2026. It measures how often models ship, not their quality or price, and counts depend on how each developer names and bundles models.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Across 11 full quarters from January 2024 to September 2026, five developers released 135 new text models in their public APIs. Counting January to September only, releases rose from 23 models in 2024 to 44 in 2025, then held at 40 in 2026. We call the main pattern the Decimal Clock: the median gap between new version numbers fell from 112 to 63 days, while whole-number generations still arrived 308 to 496 days apart.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did we count?
&lt;/h2&gt;

&lt;p&gt;We audited text model releases across five provider changelogs on November 10, 2026. The primary sources include the OpenAI API changelog, the Anthropic Claude Platform release notes, the Google Gemini API release notes, the DeepSeek API news page, and the Mistral changelog. For the Claude 3 family, we included Anthropic's launch announcements from March 4 and March 13, 2024, which predate its formal platform release notes. Each row in our dataset represents a distinct text model name, defined as a new family, a new version number, or a new tier, on the exact date it first surfaced in the public API.&lt;/p&gt;

&lt;p&gt;We excluded several categories to keep the count focused strictly on distinct text model releases. Our count omits dated snapshots of an existing name, such as gpt-4o-2024-08-06 or DeepSeek-V3-0324, along with generic latest aliases. It leaves out models restricted to approved organizations, tool-specific releases for computer use, deep research, or search, and third-party models hosted by a provider. We also excluded audio, image, video, embedding, moderation, and OCR models.&lt;/p&gt;

&lt;p&gt;Across the 11 quarters from Q1 2024 to Q3 2026, the five developers released 135 text models across 101 combined launch days. Mistral released 42 models across 28 launch days, while OpenAI published 40 models across 26 launch days. Anthropic introduced 22 models across 20 launch days, Google added 19 models across 17 launch days, and DeepSeek delivered 12 models across 10 launch days.&lt;/p&gt;

&lt;p&gt;Developers differ in how many model sizes they drop at a single time. OpenAI averaged 1.54 models per launch day, closely matched by Mistral at 1.50 models per launch day. DeepSeek averaged 1.20 models per launch event, Google posted 1.12, and Anthropic averaged 1.10.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 1: Releases doubled in 2025 and moved to the US big three in 2026
&lt;/h2&gt;

&lt;p&gt;Total model releases across the five developers rose through 2024 and 2025 and stayed high in 2026. The count ran at 5 models in Q1 2024, 7 in Q2 2024, 11 in Q3 2024, and 9 in Q4 2024. Volume accelerated to 12 models in Q1 2025, 16 in Q2 2025, and 16 in Q3 2025, reaching a peak of 19 models in Q4 2025, the busiest quarter in the dataset. Activity settled into 2026 with 12 models in Q1, 11 in Q2, and 17 in Q3.&lt;/p&gt;

&lt;p&gt;Comparing the identical nine-month stretch from January to September across calendar years shows this expansion clearly. The five providers published 23 models during the first nine months of 2024, 44 models in the same period of 2025, and 40 models in the first nine months of 2026. While the overall volume in 2026 matched the pace set in 2025, the source of those releases shifted heavily toward OpenAI, Anthropic, and Google.&lt;/p&gt;

&lt;p&gt;OpenAI, Anthropic and Google increased their output in each of these nine-month periods. Together, OpenAI, Anthropic, and Google shipped 11 models between January and September 2024, 24 models in that span in 2025, and 32 models in 2026. OpenAI went from 4 models to 14 and then 15; Anthropic scaled from 4 to 5 and then 10; Google increased from 3 to 5 and then 7.&lt;/p&gt;

&lt;p&gt;DeepSeek and Mistral moved the other way or stayed low. Mistral went from 10 models in the first nine months of 2024 to 17 in 2025, but dropped to 4 in 2026. DeepSeek held steady at lower volumes, moving from 2 models in 2024 to 3 in 2025 and 4 in 2026. The shift was clearest in Q3 2026, when OpenAI, Anthropic, and Google accounted for 15 of the 17 total releases, compared to just 6 of 16 models in Q3 2025. Mistral listed zero new text models in Q3 2026 before introducing Mistral Large 4 in preview on October 6, 2026.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi6fwmgk5mayofihwgc2p.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi6fwmgk5mayofihwgc2p.png" alt="Stacked bars per quarter. Totals: 2024-Q1 5 (3 from OpenAI, Anthropic and Google), 2024-Q2 7 (4 from OpenAI, Anthropic and Google), 2024-Q3 11 (4 from OpenAI, Anthropic and Google), 2024-Q4 9 (4 from OpenAI, Anthropic and Google), 2025-Q1 12 (7 from OpenAI, Anthropic and Google), 2025-Q2 16 (11 from OpenAI, Anthropic and Google), 2025-Q3 16 (6 from OpenAI, Anthropic and Google), 2025-Q4 19 (10 from OpenAI, Anthropic and Google), 2026-Q1 12 (10 from OpenAI, Anthropic and Google), 2026-Q2 11 (7 from OpenAI, Anthropic and Google), 2026-Q3 17 (15 from OpenAI, Anthropic and Google)." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;New text model names by the quarter they first appeared in each developer's official API changelog. Snapshots, aliases, restricted-access and non-text models are not counted.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 2: The Decimal Clock
&lt;/h2&gt;

&lt;p&gt;Our primary finding is the Decimal Clock: on the main model line of each developer, the median time between new version numbers (for example GPT-5.4 to GPT-5.5) fell from 112 days for the 19 gaps that ended in 2024 to 2025 to 63 days for the 21 gaps that ended from January to October 2026, while whole-number generations (for example GPT-5 to GPT-6) still arrived 308 to 496 days apart. We track this metric along each lab's primary text sequence: OpenAI GPT, Anthropic Claude, Google Gemini, DeepSeek V, and Mistral Large. Shorter gaps mean more point releases between whole-number generations.&lt;/p&gt;

&lt;p&gt;From January to October 2026, OpenAI, Anthropic, and Google each shipped six new version numbers along their primary lines. OpenAI shipped GPT-5.3, 5.4, 5.5, 5.6, 6, and 6.1. Anthropic published Claude 4.6, 4.7, 4.8, 5, 5.1, and 5.5. Google deployed Gemini 3.1, 3.5, 3.6, 3.7, 3.8, and 4.&lt;/p&gt;

&lt;p&gt;This tempo represents a sharp break from 2025. Across all twelve months of 2025, OpenAI shipped five main-line versions, Anthropic shipped four, and Google released two. Those 2025 releases included OpenAI GPT-4.5, 4.1, 5, 5.1, and 5.2, Anthropic Claude 3.7, 4, 4.1, and 4.5, and Google Gemini 2.5 and 3.&lt;/p&gt;

&lt;p&gt;Comparing gaps that closed in 2024 to 2025 against those closing between January and October 2026 shows how the cadence contracted. OpenAI saw its median interval between version updates fall from 98 days to 53 days. Anthropic shortened its median gap from 87 days to 56 days. Google registered the most dramatic acceleration, dropping its median gap from 238 days to 52 days. Across all five providers, the median time separating version numbers dropped from 112 days to 63 days.&lt;/p&gt;

&lt;p&gt;The fastest updates in 2026 arrived in a matter of days. OpenAI moved from GPT-5.3 on February 24 to GPT-5.4 on March 5, a gap of just 9 days. Anthropic moved from Claude Opus 4.8 on May 28 to Claude Fable 5 on June 9, an interval of 12 days. Google advanced from Gemini 3.7 Flash on August 13 to Gemini 3.8 Flash on September 2, taking 20 days.&lt;/p&gt;

&lt;p&gt;DeepSeek and Mistral operated on a more extended schedule. DeepSeek recorded a median gap of 112 days across 3 version intervals in 2024 to 2025, followed by 173 days across 2 intervals in 2026. Mistral Large posted a median gap of 149 days across 3 intervals in 2024 to 2025, followed by 308 days for its single gap in 2026. These samples are small.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuxxv7e605bmzxtgoqwsx.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuxxv7e605bmzxtgoqwsx.png" alt="Timeline. OpenAI GPT: 4o 2024-05-13, 4.5 2025-02-27, 4.1 2025-04-14, 5 2025-08-07, 5.1 2025-11-13, 5.2 2025-12-11, 5.3 2026-02-24, 5.4 2026-03-05, 5.5 2026-04-24, 5.6 2026-07-09, 6 2026-09-03, 6.1 2026-09-29; Anthropic Claude: 3 2024-03-04, 3.5 2024-06-20, 3.7 2025-02-24, 4 2025-05-22, 4.1 2025-08-05, 4.5 2025-09-29, 4.6 2026-02-05, 4.7 2026-04-16, 4.8 2026-05-28, 5 2026-06-09, 5.1 2026-09-01, 5.5 2026-09-22; Google Gemini: 1.5 2024-04-09, 2.0 2024-12-11, 2.5 2025-03-25, 3 2025-11-18, 3.1 2026-02-19, 3.5 2026-05-19, 3.6 2026-07-21, 3.7 2026-08-13, 3.8 2026-09-02, 4 2026-10-13; DeepSeek V: 2.5 2024-09-05, 3 2024-12-26, 3.1 2025-08-21, 3.2 2025-09-29, 4 2026-04-24, 4.1 2026-09-10; Mistral Large: 1 2024-02-26, 2 2024-07-24, 2.1 2024-11-18, 3 2025-12-02, 4 2026-10-06." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Main lines only: OpenAI GPT, Anthropic Claude, Google Gemini, DeepSeek V and Mistral Large. Each dot is the first API date of a new version number.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq2zog5lf6lpn9zdselt1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq2zog5lf6lpn9zdselt1.png" alt="Paired bars. OpenAI: 98 days (n=5) in 2024 to 2025, 53 days (n=6) in 2026; Anthropic: 87 days (n=5) in 2024 to 2025, 56 days (n=6) in 2026; Google: 238 days (n=3) in 2024 to 2025, 52 days (n=6) in 2026; DeepSeek: 112 days (n=3) in 2024 to 2025, 173 days (n=2) in 2026; Mistral: 149 days (n=3) in 2024 to 2025, 308 days (n=1) in 2026; All five: 112 days (n=19) in 2024 to 2025, 63 days (n=21) in 2026." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Median days between consecutive new version numbers on each main line, grouped by the year the gap ended. DeepSeek and Mistral rest on 1 to 3 gaps.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 3: Whole-number generations still take about a year
&lt;/h2&gt;

&lt;p&gt;While point releases sped up in 2026, whole-number generations stayed far apart. The median interval across all eight whole-number model transitions in the dataset was 387.5 days. Developers iterated on decimal increments at high frequency, but whole-number versions still arrived roughly ten to sixteen months apart.&lt;/p&gt;

&lt;p&gt;The three longest transitions took well over a year. Mistral Large 2 to Mistral Large 3 took 496 days, running from July 24, 2024 to December 2, 2025. DeepSeek V3 to DeepSeek V4 took 484 days, spanning December 26, 2024 to April 24, 2026. Claude 3 to Claude 4 required 444 days, stretching from March 4, 2024 to May 22, 2025.&lt;/p&gt;

&lt;p&gt;Generational transitions inside OpenAI and Anthropic clustered close to the one-year mark. GPT-5 to GPT-6 took 392 days, running from August 7, 2025 to September 3, 2026. Claude 4 to Claude 5 arrived after 383 days, dating from May 22, 2025 to June 9, 2026.&lt;/p&gt;

&lt;p&gt;The three shortest transitions belong to Google and Mistral. Gemini 2.0 to Gemini 3 took 342 days between December 11, 2024 and November 18, 2025, while Gemini 3 to Gemini 4 arrived 329 days later on October 13, 2026. Mistral Large 3 to Mistral Large 4 recorded 308 days between December 2, 2025 and October 6, 2026. In 2026, the decimals sped up while the whole numbers stayed near one year apart.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fm7b6nd8vtl4muiydzhgh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fm7b6nd8vtl4muiydzhgh.png" alt="Horizontal bars. Mistral Large 2 to 3: 496 days (2024-07-24 to 2025-12-02); DeepSeek V3 to V4: 484 days (2024-12-26 to 2026-04-24); Claude 3 to Claude 4: 444 days (2024-03-04 to 2025-05-22); GPT-5 to GPT-6: 392 days (2025-08-07 to 2026-09-03); Claude 4 to Claude 5: 383 days (2025-05-22 to 2026-06-09); Gemini 2.0 to Gemini 3: 342 days (2024-12-11 to 2025-11-18); Gemini 3 to Gemini 4: 329 days (2025-11-18 to 2026-10-13); Mistral Large 3 to 4: 308 days (2025-12-02 to 2026-10-06)." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Days between the first API release of consecutive whole-number versions on each main line.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 4: Google moved to generally available Flash releases
&lt;/h2&gt;

&lt;p&gt;Google changed how new models first appear in its API. All 12 Google models first listed in 2024 and 2025 appeared as experimental or preview releases. In 2026, 6 of Google's 8 new models launched with general availability on the day they first appeared, starting with Gemini 3.5 Flash on May 19, 2026.&lt;/p&gt;

&lt;p&gt;Most of Google's 2026 releases were Flash models: 6 of its 8 new models were Flash or Flash-Lite. The company released Gemini 3.5 Flash on May 19, Gemini 3.6 Flash on July 21, Gemini 3.7 Flash on August 13, and Gemini 3.8 Flash on September 2. That cadence delivered four successive Flash versions within 106 days.&lt;/p&gt;

&lt;p&gt;After Google listed Gemini 3.1 Pro Preview on February 19, 2026, it did not introduce another non-Flash Gemini model until Gemini 4 Argon arrived on October 13, 2026.&lt;/p&gt;

&lt;p&gt;Across all five developers, the proportion of models launching without general availability held relatively stable. Non-GA models represented 21.9% of total releases in 2024, 19.0% in 2025, and 18.2% in 2026. These figures include Mistral Labs models and DeepSeek's temporary V3.2-Speciale, which both counted as not generally available at launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 5: New tier names replace size words
&lt;/h2&gt;

&lt;p&gt;In 2026, OpenAI, Anthropic, Google and DeepSeek each introduced tier names that were not in their 2024 and 2025 lineups. OpenAI released its final mini and nano models within our observation window on March 17, 2026, with GPT-5.4 mini and GPT-5.4 nano. When OpenAI launched GPT-5.6 on July 9, 2026, it introduced Sol, Terra, and Luna, and followed with Astra alongside GPT-6 on September 3, 2026. Exactly 8 of the 16 models OpenAI published between January and October 2026 used these new naming conventions.&lt;/p&gt;

&lt;p&gt;Anthropic also broadened its tiered naming structure beyond its established sizes. On June 9, 2026, the developer introduced Claude Fable 5, creating a fourth tier alongside Opus, Sonnet, and Haiku. It expanded that tier on September 1, 2026, with the introduction of Claude Fable 5.1.&lt;/p&gt;

&lt;p&gt;Other providers also drifted away from conventional naming schemes. Google dropped the Pro and Flash designations for its primary generation launch, introducing Gemini 4 as Gemini 4 Argon on October 13, 2026. DeepSeek V4, launched on April 24, 2026, came as two models: V4 Pro and V4 Flash.&lt;/p&gt;

&lt;p&gt;Mistral preserved its established tier naming of Large, Medium, Small, and Ministral while releasing specialized models across specific disciplines. Across Mistral's 43 total rows, 9 models targeted software development under the Codestral and Devstral lines. Another 6 rows represented reasoning models under the Magistral label, and 3 rows covered mathematics through the Mathstral and Leanstral series.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means for teams that build on these APIs
&lt;/h2&gt;

&lt;p&gt;With version gaps at the big three sitting at a median of 53 to 56 days, an engineering team pinned to specific model identifiers encounters a new version roughly every two months from each provider. Managing updates can no longer be handled as an annual project. Engineering groups must treat prompt evaluation and model migration as continuous routines rather than rare maintenance events.&lt;/p&gt;

&lt;p&gt;Teams should keep model identifiers stored strictly in configuration files and environment variables rather than hardcoded inside application logic. Decoupling the codebase from explicit model tags reduces migration friction when newer decimals land. A gateway such as Tokely lets you switch the model name without changing the integration.&lt;/p&gt;

&lt;p&gt;New tier names like Sol, Terra, Luna, Fable, Argon, and Flash require independent testing against existing production workloads. Teams cannot rely on legacy size words or familiar brand tiers to deduce performance characteristics, latency profiles, or pricing structures. Direct evaluation against your own task distributions is necessary before routing production traffic to newly released model tiers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Methodology and limitations
&lt;/h2&gt;

&lt;p&gt;We compiled this dataset by reviewing official changelogs on November 10, 2026, verifying each entry against its public source URL on that date. Each release date reflects the timestamp assigned by the provider in its official changelog. These entry dates can differ by a day or so from blog announcements.&lt;/p&gt;

&lt;p&gt;Release counts depend heavily on how individual developers package, brand, and bundle their models. A lab that introduces multiple sizes on a single day logs multiple models in this dataset, which is why launch days should be considered alongside raw model counts. In addition, the cadence medians calculated for DeepSeek and Mistral rest on small samples of 1 to 3 gaps, meaning individual release decisions sway their metrics significantly.&lt;/p&gt;

&lt;p&gt;Our analysis deliberately omits providers and models that do not meet strict documentation criteria. We excluded xAI because its release notes list updates by month rather than specific calendar days and do not list all earlier Grok models. OpenAI's gpt-oss open-weight models do not appear in the OpenAI API changelog and are not tracked here.&lt;/p&gt;

&lt;p&gt;Our version gap calculations track main lines only, covering GPT, Claude, Gemini, DeepSeek V, and Mistral Large. While OpenAI's o-series and Mistral's specialized coding, math, and reasoning lines appear in the raw dataset, we excluded them from the median gap figures. This study measures API release velocity over time and does not measure output quality, inference latency, or pricing changes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Download the data
&lt;/h2&gt;

&lt;p&gt;One CSV with 139 rows contains the raw data across the observation window, covering developer, date, quarter, model ID, line, version, tier, stage, source URL, and verification date. Cite as: Tokely, "How Often Do AI Labs Ship New Models? Release Cadence of OpenAI, Anthropic, Google, DeepSeek and Mistral (2024-2026)", November 2026, &lt;a href="https://tokely.me/blog/ai-model-release-cadence-2026" rel="noopener noreferrer"&gt;https://tokely.me/blog/ai-model-release-cadence-2026&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/ai-model-release-cadence-2026" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>openai</category>
      <category>datascience</category>
    </item>
    <item>
      <title>Claude Code, Codex, Copilot and Cursor Plans vs API: Break-Even and the Cost of Long Sessions (2026)</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Thu, 05 Nov 2026 11:01:17 +0000</pubDate>
      <link>https://dev.to/tokely/claude-code-codex-copilot-and-cursor-plans-vs-api-break-even-and-the-cost-of-long-sessions-2026-53d6</link>
      <guid>https://dev.to/tokely/claude-code-codex-copilot-and-cursor-plans-vs-api-break-even-and-the-cost-of-long-sessions-2026-53d6</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Research scope:&lt;/strong&gt; This study is a snapshot: plan prices and API list prices from official pages read on November 5, 2026. Session costs are calculated from stated assumptions and are not observations of any real agent; break-even figures use the averages Anthropic publishes for Claude Code and ignore plan limits.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; At Anthropic's average of $13 per active day, flat plans at $20, $100 and $200 pay for themselves in 1.5, 7.7 and 15.4 active days if limits do not stop you. Only GitHub Copilot of the four vendors states its allowance in money. On the API, the long-session premium reaches 1.79x to 4.53x.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did we compare?
&lt;/h2&gt;

&lt;p&gt;We compared two things: the published plans of four coding agents (Claude Code, OpenAI Codex, GitHub Copilot and Cursor) and a model of API cost. All session numbers in this analysis come from an explicit mathematical model rather than observations of any real agent.&lt;/p&gt;

&lt;p&gt;The modeled session consists of 100 sequential API calls. The session starts with a 20,000-token context that is written to prompt cache on the very first call. Every subsequent call resends the entire accumulated prior context as a cache read, writes new tokens to the cache and receives 500 output tokens.&lt;/p&gt;

&lt;p&gt;We modeled three session sizes that differ solely by the volume of new tokens added per step. The Short session adds 500 tokens per call and ends at a prompt size of 69,500 tokens. The Medium session adds 2,000 tokens per call to reach 218,000 tokens, while the Long session adds 6,000 tokens per call to finish at 614,000 tokens. These synthetic scenarios serve as illustrative assumptions to test how pricing schedules behave as contexts expand.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 1: Flat plans break even within days, if limits hold
&lt;/h2&gt;

&lt;p&gt;Anthropic's published documentation for Claude Code reports an average enterprise cost of around $13 per developer per active day. That benchmark places full-month usage between $150 and $250 per developer, with costs remaining below $30 per active day for 90% of users. Dividing a flat subscription price by the daily API spend produces the break-even threshold in active working days.&lt;/p&gt;

&lt;p&gt;At the $13 daily average, a $20 entry plan breaks even after 1.5 active days of development. A $100 plan requires 7.7 active days to break even, while a $200 tier requires 15.4 active days. For higher-intensity users spending $30 per active day, those break-even requirements compress to 0.7 days for a $20 plan, 3.3 days for a $100 plan and 6.7 days for a $200 plan.&lt;/p&gt;

&lt;p&gt;Against Anthropic's reported monthly range of $150 to $250, direct API spend sits above the $100 Max plan price and around the $200 Ultra price. These calculations hold only if plan limits do not stop you first, and vendors publish those limits in very different ways.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj77o903s0268s18sx1l9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj77o903s0268s18sx1l9.png" alt="$20 plan at $13 a day: 1.5 days; $20 plan at $30 a day: 0.7 days; $100 plan at $13 a day: 7.7 days; $100 plan at $30 a day: 3.3 days; $200 plan at $13 a day: 15.4 days; $200 plan at $30 a day: 6.7 days" width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Plan price divided by API cost per active day, using the figures in Anthropic Claude Code docs: about $13 on average and below $30 for 90% of users. Plan limits are ignored.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 2: Only one vendor states the allowance in money
&lt;/h2&gt;

&lt;p&gt;Across the four evaluated tools, only GitHub Copilot defines its plan allowances directly in currency. Its $10 Pro tier includes $15 in AI credits, the $39 Pro+ tier includes $70, and the $100 Max tier includes $200. These credits draw down at published token consumption rates, and Copilot lists token rates for Claude Opus 5.5, Claude Sonnet 5.5 and GPT-6.1 Sol that match the respective model providers' public API price sheets.&lt;/p&gt;

&lt;p&gt;Claude structures its tiers around relative capacity multipliers rather than token totals. Pro lists at $20 for 1x allowance, Max lists at $100 for 5x, and Ultra lists at $200 for 10x the Pro weekly limit. This pricing keeps the cost per weekly Pro unit at exactly $20 across all three tiers, making the annual Pro plan at $17 per month the lowest unit rate available. Anthropic publishes no explicit token or message volumes for these plans, though Ultra removes the five-hour restriction for verified accounts.&lt;/p&gt;

&lt;p&gt;Anthropic includes $100 and $200 in monthly Claude Platform API credits with Max and Ultra plans, but Anthropic says those credits cannot be used in Claude Code. Cursor similarly isolates its included allowances to its own internal models and Grok across its $8 Plus, $30 Premium, $100 Super and $200 Ultra plans, which scale at 1x, 4x, 15x and 50x base capacity. Any calls to Claude or GPT models through Cursor require prepaid credits billed at full API list price for Premium users and above.&lt;/p&gt;

&lt;p&gt;OpenAI Codex lists a range of 15 to 160 GPT-6.1 Sol local messages per five hours on its $20 Plus plan and offers Pro plans at $100, $200 and $500. We did not find multipliers between plans on the pages we could read. OpenAI pricing documentation explicitly cautions developers that API token prices are separate from subscription usage and should not be used to estimate included tasks. Respecting that guidance, our model does not attempt to convert Codex message allotments into dollar equivalents.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F41eubfrdfmdeppu625nn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F41eubfrdfmdeppu625nn.png" alt="Claude | Pro $20 · Max $100 · Ultra $200 | 1x · 5x · 10x Pro per week | $20 per weekly Pro unit, on all three; Copilot | Pro $10 · Pro+ $39 · Max $100 | $15 · $70 · $200 in AI credits | $1.50 to $2.00 of credits per plan dollar; Cursor | Plus $8 · Premium $30 · Super $100 · Ultra $200 | 1x · 4x · 15x · 50x Plus, Grok and Cursor | $8 down to $4 per unit; Claude and GPT extra; Codex | Plus $20 · Pro $100, $200, $500 | Plus: 15 to 160 GPT-6.1 Sol messages | Pro multiples not on the pages we could read" width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Monthly prices and allowances as published on official pricing pages, read November 5, 2026.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 3: As sessions grow, output stops being the main cost
&lt;/h2&gt;

&lt;p&gt;Token pricing on Claude Opus 5.5 charges $4 per million input tokens, $5 per million five-minute cache write tokens, $0.20 per million cache read tokens and $20 per million output tokens. In our simulated 100-call workload, the total bill lists at $2.23 for the Short session, $4.43 for the Medium session and $10.29 for the Long session. As context accumulates over sequential requests, the distribution of expenses shifts away from generation toward context maintenance.&lt;/p&gt;

&lt;p&gt;Output generation represents 44.9% of the invoice on the Short session, but accounts for only 9.7% of the total on the Long session. Cache reads expand from 39.5% of total spend in the Short scenario to 60.4% in the Long scenario, while cache writes rise from 15.6% to 29.8%. Across all three modeled sizes, prompt cache reads account for roughly 97% to 98% of all processed tokens.&lt;/p&gt;

&lt;p&gt;Without caching, the exact same three workloads on Opus 5.5 would list at $18.90, $48.60 and $127.80, representing cost increases of 8.5x, 11.0x and 12.4x. Because cache reads are nearly all the tokens in these modeled sessions, the cache-read rate moves the bill more than the headline input price. Comparing models on input and output prices alone misses most of the cost.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsjwk02rk7xd4ma6pb2u1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsjwk02rk7xd4ma6pb2u1.png" alt="Short: cache reads 39.5%, cache writes 15.6%, output 44.9%; Medium: cache reads 52.8%, cache writes 24.6%, output 22.6%; Long: cache reads 60.4%, cache writes 29.8%, output 9.7%" width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Share of the list price of a modeled 100-call session on Claude Opus 5.5. Assumptions are in the text; this is not a measurement of any agent.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 4: Equal list prices stop being equal in long sessions
&lt;/h2&gt;

&lt;p&gt;Applying identical token counts across other provider rate tables reveals sharp divergence during extended sessions. Assuming identical token consumption without assessing model output quality, the modeled Long session lists at $71.33 for GPT-6 Astra, $17.95 for Claude Fable 5.1, $10.29 for Claude Opus 5.5, $9.67 for Gemini 4 Argon from December 1, $8.65 for GPT-6.1 Sol, $5.14 for Claude Sonnet 5.5, $4.84 for Gemini 4 Argon until November 30, $4.32 for GPT-6.1 Terra, $1.97 for Claude Haiku 5.5 and $0.71 for GPT-6 Luna.&lt;/p&gt;

&lt;p&gt;Matching headline rates can obscure major differences in deep contexts. Both GPT-6.1 Sol and Claude Sonnet 5.5 list standard prices of $2 per million input tokens, $0.10 for cached tokens and $10 for output tokens. Consequently, they bill identically at $1.11 in the Short session and $2.21 in the Medium session. In the Long session, Sol costs 1.68x more at $8.65 versus $5.14 for Sonnet, because OpenAI increases pricing tiers once prompt contexts exceed 272,000 tokens, a threshold crossed by 57 of the 100 calls in that simulation.&lt;/p&gt;

&lt;p&gt;A similar divergence appears at higher price points. Both GPT-6 Astra and Claude Fable 5.1 publish headline rates of $10 per million input tokens and $50 per million output tokens. Astra costs 1.74x more than Fable in the Short session because Astra sets cached input at $1 per million versus $0.25 for Claude, and that gap widens to 3.97x in the Long session.&lt;/p&gt;

&lt;p&gt;At the economy tier, Claude Haiku 5.5 and GPT-6 Luna both list $0.10 per million input tokens and $0.50 per million output tokens, resulting in a shared $0.08 cost for the Short session. Haiku, however, imposes a 5x rate multiplier on prompts exceeding 100,000 tokens. This pricing tier causes Haiku to cost 3.9x as much as Luna in the Medium session and 2.76x as much in the Long session.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn9p5v6b6wzao4be56syt.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn9p5v6b6wzao4be56syt.png" alt="GPT-6 Astra: $71.33; Claude Fable 5.1: $17.95; Claude Opus 5.5: $10.29; Gemini 4 Argon from Dec 1: $9.67; GPT-6.1 Sol: $8.65; Claude Sonnet 5.5: $5.14; Gemini 4 Argon until Nov 30: $4.84; GPT-6.1 Terra: $4.32; Claude Haiku 5.5: $1.97; GPT-6 Luna: $0.71" width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;List price of the same modeled Long session on each price table, including long-context tiers. Assumes identical tokens and says nothing about model quality.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 5: The long-session premium
&lt;/h2&gt;

&lt;p&gt;We define the long-session premium as what one 100-call session costs compared with five 20-call sessions that restart from a fresh 20,000-token context. It is 1.79x on Claude Opus 5.5, 3.01x on GPT-6.1 Sol and 4.53x on Claude Haiku 5.5. When an agent session runs continuously without resetting context, accumulating history inflates cache reads on every single request.&lt;/p&gt;

&lt;p&gt;Evaluating our modeled Long session illustrates the scale of this effect. A single 100-call Long session adding 6,000 tokens per call on Claude Opus 5.5 lists at $10.29, compared to $5.76 across five segmented 20-call sessions at the same pace, yielding a 1.79x long-session premium. On GPT-6.1 Sol, the single session costs $8.65 compared to $2.88 across five segmented sessions, representing a 3.01x premium. On Claude Haiku 5.5, the single run costs $1.97 against $0.43 for the segmented alternative, reaching a 4.53x premium.&lt;/p&gt;

&lt;p&gt;The long-session premium expands most aggressively when an extended run crosses a vendor's long-context pricing threshold. The five shorter sessions write slightly more prompt tokens overall, totaling 670,000 tokens against 614,000 tokens for the single unified session, because each restart writes the initial context again. The savings assume the work really can restart without the earlier context, which is the catch.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fty83rrwtyqrrh2to3yu9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fty83rrwtyqrrh2to3yu9.png" alt="Claude Opus 5.5: one long: $10.29; Claude Opus 5.5: five short: $5.76; GPT-6.1 Sol: one long: $8.65; GPT-6.1 Sol: five short: $2.88; Claude Haiku 5.5: one long: $1.97; Claude Haiku 5.5: five short: $0.43" width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Modeled list price of one 100-call session against five 20-call sessions at the same pace, each restarting from 20,000 tokens.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Which should you pick?
&lt;/h2&gt;

&lt;p&gt;Rule one requires pricing your specific development month. Compare expected direct API spend against fixed plan pricing based on your active coding cadence. If you activate an agent only one or two days each month, pay-per-token API billing can be the cheaper choice.&lt;/p&gt;

&lt;p&gt;Rule two applies if you work most days mostly alone inside a single agent environment. A flat subscription plan usually wins on price under regular schedules, provided its limits fit your workflow. Hitting a limit costs time and not money. With Claude usage credits enabled, overflow activity continues at standard API rates, so the plan does not make extra usage more expensive than the API.&lt;/p&gt;

&lt;p&gt;Rule three points to direct API integration when you build custom internal software, share access across an entire engineering team or combine multiple vendors in one pipeline. Claude plan limits cover Claude and Claude Code, but do not provide token allowances for your own standalone applications.&lt;/p&gt;

&lt;p&gt;Rule four addresses optimization when operating directly over raw model APIs. Before committing to a provider, compare cached-input prices and long-context threshold surcharges rather than relying on headline input and output numbers. When managing active coding sessions, restart from a fresh context whenever earlier conversational turns are no longer required by the agent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;Is a coding agent subscription cheaper than the API?&lt;/p&gt;

&lt;p&gt;It depends on active days. At Anthropic's $13 daily average, flat plans break even in 1.5 to 15.4 active days, though developers using agents only a couple of days a month pay less on the API.&lt;/p&gt;

&lt;p&gt;How much usage does Claude Pro include?&lt;/p&gt;

&lt;p&gt;Anthropic publishes no token or message count for Claude Pro. Limits are stated as relative multiples of Pro per five hours and per week.&lt;/p&gt;

&lt;p&gt;Do Max API credits work in Claude Code?&lt;/p&gt;

&lt;p&gt;No, Anthropic states that the monthly API credits included with Max cannot be used in Claude Code or the Claude apps.&lt;/p&gt;

&lt;p&gt;What happens when I hit a Claude plan limit?&lt;/p&gt;

&lt;p&gt;You must wait for the limit window to reset, or continue at standard API rates if you enable usage credits.&lt;/p&gt;

&lt;h2&gt;
  
  
  Methodology and limitations
&lt;/h2&gt;

&lt;p&gt;Session costs in this article represent mathematical calculations derived from assumed workloads rather than direct observations of Claude Code, Codex, Copilot or Cursor. Production agents exhibit varying context window behaviors, diverse prompt caching success rates and differing output lengths. A different underlying model may also require more or fewer tokens to complete an identical development task.&lt;/p&gt;

&lt;p&gt;The break-even benchmarks rely on Anthropic's published Claude Code enterprise deployment averages, so individual developers and small teams may differ. The calculations also omit the impact of plan capacity limits, which most vendors do not publish in comparable units. We assumed that all cache writes use Anthropic's five-minute rate and OpenAI's 30-minute rate, that new tokens on Gemini 4 Argon, which uses implicit caching, bill at the input price, and that long-context thresholds count the whole prompt per request.&lt;/p&gt;

&lt;p&gt;Gemini 3.8 Flash is excluded from this model because its cache storage fees depend on how long content remains cached. Plan prices and API rates reflect public web pages accessed on November 5, 2026, which do not display absolute publication dates. Because two OpenAI help pages returned errors to our fetcher, Codex details come from chatgpt.com/codex/pricing and official OpenAI pricing documentation. We ran no paid requests for this study.&lt;/p&gt;

&lt;h2&gt;
  
  
  Data and citation
&lt;/h2&gt;

&lt;p&gt;All modeled session figures are compiled in a free CSV file that contains every assumption and price, formatted with one row per model and session size. Cite as: Tokely, "Claude Code, Codex, Copilot and Cursor Plans vs API: Break-Even and the Cost of Long Sessions", November 2026, &lt;a href="https://tokely.me/blog/coding-agent-plans-vs-api-cost-2026" rel="noopener noreferrer"&gt;https://tokely.me/blog/coding-agent-plans-vs-api-cost-2026&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/coding-agent-plans-vs-api-cost-2026" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>programming</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Do AI Benchmarks Measure Real Work? 21 Leaderboard Evaluations Mapped to 41 O*NET Work Activities (2026)</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Tue, 03 Nov 2026 08:39:55 +0000</pubDate>
      <link>https://dev.to/tokely/do-ai-benchmarks-measure-real-work-21-leaderboard-evaluations-mapped-to-41-onet-work-activities-dkm</link>
      <guid>https://dev.to/tokely/do-ai-benchmarks-measure-real-work-21-leaderboard-evaluations-mapped-to-41-onet-work-activities-dkm</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Research scope:&lt;/strong&gt; This study is a snapshot: the 21 evaluations listed on the Artificial Analysis Intelligence Benchmarking methodology page on November 3, 2026, coded by Tokely to the 41 Generalized Work Activities in O*NET 31.0. It measures which work activities the evaluations test, not how well any model performs them, and occupations are not weighted by employment.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; The Artificial Analysis Intelligence Index tests 8 of 41 O*NET work activities and puts 73% of its weight on three of them. Across all 21 evaluations listed on its methodology page, coverage widens to 13 of 41 activities. This leaves what we call the colleague gap, where communicating with supervisors, peers or subordinates is rated very important (4 or higher on O*NET's 1 to 5 importance scale) in 541 of 911 occupations, yet 0 of 21 evaluations test it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did we measure?
&lt;/h2&gt;

&lt;p&gt;The US Department of Labor catalogs occupational requirements across the economy using the O*NET 31.0 database. O*NET rates 41 Generalized Work Activities on a 1 to 5 scale of importance for each occupation. These activities span the full spectrum of labor, running from Getting Information to Operating Vehicles, Mechanized Devices, or Equipment. 911 occupations have ratings for all 41 activities.&lt;/p&gt;

&lt;p&gt;Among those 911 occupations, 862 have at least one activity rated 4 or higher on the 5-point scale. We define any activity with an importance score of 4 or higher as a core activity for that occupation.&lt;/p&gt;

&lt;p&gt;To evaluate benchmark coverage against these workplace definitions, we examined the Artificial Analysis leaderboard as published on November 3, 2026. Their methodology page tracks 21 distinct evaluations. Nine of these evaluations constitute the composite Intelligence Index v5.0, while the remaining 12 evaluations are tracked and reported as standalone benchmarks.&lt;/p&gt;

&lt;p&gt;The nine evaluations in the Intelligence Index v5.0 carry specific weights. AA-Briefcase accounts for 15%, FrontierCode 2.0 holds 15%, Terminal-Bench-Science takes 15%, and AA-Omniscience represents 15%. Terminal-Bench 4.0, CritPt v2 hard subset, and HLE-Diamond carry 10% each. AutomationBench-AA and GDP.pdf contribute 5% apiece to complete the composite score.&lt;/p&gt;

&lt;p&gt;The 12 standalone evaluations address specialized domains and task setups outside the composite index. This group consists of GDPval-AA, Harvey LAB-AA, APEX-Agents-AA, AA-AnalystAgent, EnterpriseOps-Gym-AA, and ITBench-AA. It also includes Code2Video-AA, MLCR-AA, HealthBench, IFBench, Global-MMLU-Lite, and MMMU Pro.&lt;/p&gt;

&lt;p&gt;We coded each of the 21 evaluations to between one and four O*NET work activities based directly on what its graded output depends on. For example, FrontierCode 2.0 asks models to generate mergeable changes for real open-source software repositories. Because passing requires writing functional software and resolving bugs, FrontierCode 2.0 maps to Working with Computers and Making Decisions and Solving Problems.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 1: The Intelligence Index tests 8 of 41 work activities
&lt;/h2&gt;

&lt;p&gt;The Artificial Analysis Intelligence Index concentrates 72.9% of its total weight on just three work activities. Working with Computers claims 25.4% of the index weight. Updating and Using Relevant Knowledge receives 25.0%, and Making Decisions and Solving Problems accounts for 22.5%.&lt;/p&gt;

&lt;p&gt;The remaining 27.1% of the index distributes thinly across five other activities. Analyzing Data or Information takes 13.8% of the total index weight. Getting Information accounts for 6.3%, while Interpreting the Meaning of Information for Others captures 3.8%. Processing Information and Performing Administrative Activities take 1.7% each.&lt;/p&gt;

&lt;p&gt;The other 33 Generalized Work Activities receive 0% weight in the index. None of the index evaluations is coded to physical work, to caring for people or to communicating with coworkers or the public. For a team deploying models based solely on the composite index, the leaderboard reflects performance on eight specific knowledge and software activities.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fggzvnkbp383st8voryzw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fggzvnkbp383st8voryzw.png" alt="Bar chart of Artificial Analysis Intelligence Index v5.0 weight by O*NET work activity: Working with Computers 25.4%, Updating and Using Relevant Knowledge 25.0%, Making Decisions and Solving Problems 22.5%, Analyzing Data or Information 13.8%, Getting Information 6.2%, Interpreting the Meaning of Information for Others 3.8%, Processing Information 1.7%, Performing Administrative Activities 1.7%. The other 33 of 41 activities get 0%." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Artificial Analysis Intelligence Index v5.0 weight split evenly across the O*NET 31.0 work activities each of its 9 evaluations is coded to. Evaluation list verified November 3, 2026.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 2: The colleague gap
&lt;/h2&gt;

&lt;p&gt;The data reveals a stark division that we call the colleague gap: communicating with supervisors, peers or subordinates is rated very important (4 or higher on O*NET's 1 to 5 importance scale) in 541 of 911 occupations, the second most common core activity after getting information (723), yet none of the 21 evaluations tests it.&lt;/p&gt;

&lt;p&gt;A comparison of core activities highlights this mismatch across occupations. Getting Information leads the entire database as a core activity in 723 occupations and is tested by five evaluations. Communicating with Supervisors, Peers, or Subordinates follows in 541 occupations, but zero evaluations grade it. Making Decisions and Solving Problems is core in 528 occupations and tested by five evaluations.&lt;/p&gt;

&lt;p&gt;Other frequent core activities show similar patterns of coverage or absence. Working with Computers is core in 425 occupations and tested by 11 evaluations. Updating and Using Relevant Knowledge is core in 382 occupations and covered by five tests. In contrast, Identifying Objects, Actions, and Events is core in 365 occupations, yet zero evaluations measure it.&lt;/p&gt;

&lt;p&gt;Documenting/Recording Information is core in 341 occupations and appears in only one evaluation. Establishing and Maintaining Interpersonal Relationships is core in 284 occupations, yet zero evaluations test it. Customer Service Representatives rate coworker communication as their single most important activity, scoring it at 4.59 out of 5.&lt;/p&gt;

&lt;p&gt;Current AI evaluations score a finished file, answer, or code change. None of the 21 evaluations grades how an agent reports to, asks, or hands off work to people inside a team.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdhqqpyty3wdrge7c58zc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdhqqpyty3wdrge7c58zc.png" alt="Bar chart of how many of 911 O*NET occupations rate each work activity 4 or higher in importance: Getting Information 723 (tested by 5), Communicating with Supervisors, Peers, or Subordinates 541 (untested), Making Decisions and Solving Problems 528 (tested by 5), Working with Computers 425 (tested by 11), Updating and Using Relevant Knowledge 382 (tested by 5), Identifying Objects, Actions, and Events 365 (untested), Documenting/Recording Information 341 (tested by 1), Processing Information 290 (tested by 2), Organizing, Planning, and Prioritizing Work 284 (tested by 1), Establishing and Maintaining Interpersonal Relationships 284 (untested), Evaluating Information to Determine Compliance with Standards 239 (tested by 2), Analyzing Data or Information 237 (tested by 9)." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;The 12 O*NET 31.0 work activities rated 4 or higher in importance by the most occupations (of 911), and whether any of the 21 Artificial Analysis evaluations tests them.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 3: Coverage follows the job family
&lt;/h2&gt;

&lt;p&gt;Benchmark coverage concentrates heavily in technical and desk-bound occupations. For each occupation, we computed the share of its core activities that at least one Intelligence Index evaluation tests, then took the median by job family across the 22 Standard Occupational Classification major groups. Computer and Mathematical occupations top the rankings with a median coverage of 70%.&lt;/p&gt;

&lt;p&gt;Professional desk jobs follow right behind the software sector. Legal occupations post a median core activity coverage of 56%. Architecture and Engineering, Life, Physical, and Social Science, and Office and Administrative Support each sit at a median of 50%. Business and Financial Operations records a median coverage score of 46%.&lt;/p&gt;

&lt;p&gt;Healthcare Practitioners and Technical occupations sit in the middle at 40%. Manual, trade and service families sit at the bottom: Production occupations drop to 24%, while Transportation and Material Moving sits at 22%. Construction and Extraction posts 21%, Building and Grounds Cleaning and Maintenance reaches 18%, Food Preparation and Serving Related scores 17%, and Farming, Fishing, and Forestry records 0%.&lt;/p&gt;

&lt;p&gt;Individual occupations illustrate how these disparities play out in practice. For Software Developers, the index tests six of their nine core activities. For Registered Nurses, the index tests five of 17 core activities, leaving their top activity, Assisting and Caring for Others at 4.94 out of 5, completely untested. Elementary School Teachers see only one of five core activities tested, with their top activity of Training and Teaching Others omitted.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjc59g721m84jbe3pilgr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjc59g721m84jbe3pilgr.png" alt="Bar chart of the median share of very important O*NET work activities tested by the AA Intelligence Index v5.0, by SOC job family: Computer and Mathematical 70%, Legal 56%, Architecture and Engineering 50%, Life, Physical, and Social Science 50%, Office and Administrative Support 50%, Business and Financial Operations 46%, Production 24%, Transportation and Material Moving 22%, Construction and Extraction 21%, Building and Grounds Cleaning and Maintenance 18%, Food Preparation and Serving Related 17%, Farming, Fishing, and Forestry 0%." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Median share of very important O*NET work activities (importance 4 or higher) tested by at least one Intelligence Index v5.0 evaluation, by SOC major group. Occupations are not weighted by employment.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 4: Adding 12 standalone evaluations widens coverage to 13 activities
&lt;/h2&gt;

&lt;p&gt;Looking beyond the composite index expands the scope of evaluated work. Combining all 21 evaluations across the methodology page brings total coverage to 13 of the 41 work activities. Even with this expanded suite, 28 work activities remain completely untested by any evaluation on the page.&lt;/p&gt;

&lt;p&gt;The existing evaluations double down on familiar digital tasks. Working with Computers is tested by 11 of the 21 evaluations, making it the most frequently evaluated activity in the set. Analyzing Data or Information is tested by nine evaluations, reinforcing the focus on analytical processing.&lt;/p&gt;

&lt;p&gt;The 12 standalone evaluations introduce coverage for five additional activities. Harvey LAB-AA and MLCR-AA add Evaluating Information to Determine Compliance with Standards. Harvey LAB-AA also adds Documenting/Recording Information. EnterpriseOps-Gym-AA adds Organizing, Planning, and Prioritizing Work, Code2Video-AA adds Thinking Creatively, and APEX-Agents-AA along with HealthBench adds Providing Consultation and Advice to Others.&lt;/p&gt;

&lt;p&gt;These additions lift coverage across occupations. The median occupation goes from 37.5% of core activities tested under the index alone to 54.2% across all 21 benchmarks. Occupations with more than half of their core activities tested go from 193 to 446 of 862.&lt;/p&gt;

&lt;p&gt;The expanded suite reduces but does not eliminate zero-coverage jobs. The number of occupations with none of their core activities tested drops from 92 to 81. When examining the single most important activity for an occupation, the Intelligence Index tests the top activity for 373 of 911 occupations, and adding the standalone evaluations raises that total to 463.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F27a0uoljzp5d2prcsu2f.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F27a0uoljzp5d2prcsu2f.png" alt="Bar chart of the number of Artificial Analysis evaluations, out of 21, coded to each O*NET work activity: Working with Computers 11, Analyzing Data or Information 9, Making Decisions and Solving Problems 5, Updating and Using Relevant Knowledge 5, Getting Information 5, Interpreting the Meaning of Information for Others 4, Processing Information 2, Performing Administrative Activities 2, Evaluating Information to Determine Compliance with Standards 2, Providing Consultation and Advice to Others 2, Documenting/Recording Information 1, Organizing, Planning, and Prioritizing Work 1, Thinking Creatively 1. The other 28 of 41 activities are tested by none." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Number of the 21 Artificial Analysis evaluations coded to each O*NET work activity. 28 of 41 activities are tested by none.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How does this compare with Mercor's benchmark map?
&lt;/h2&gt;

&lt;p&gt;Our findings align with external research on benchmark scope. In October 2026, Mercor published its Benchmark Map at mercor.com/research/labor-index/benchmark-map. Mercor mapped prompts from 29 selected benchmarks against 18,797 O*NET tasks across 923 occupations using an LLM judge.&lt;/p&gt;

&lt;p&gt;Mercor defined a task as covered at five or more prompts, and it weighted its results by estimated working time. It reports that 208 of 923 occupations have a covered task, and that about 90% of US working hours go to tasks with little or no benchmark coverage. That is Mercor's result, not ours.&lt;/p&gt;

&lt;p&gt;Our study is coarser, examining 41 Generalized Work Activities instead of 18,797 tasks. We also used the evaluations a popular public leaderboard actually runs, rather than a list of benchmarks selected for economic relevance.&lt;/p&gt;

&lt;p&gt;Despite these differences in method and granularity, both studies point the same way. Evaluation coverage is deep in computer, legal, and analytical work. At the same time, coverage is thin in physical, interpersonal, and hands-on work.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means when you pick a model
&lt;/h2&gt;

&lt;p&gt;A leaderboard score mostly tells you how a model does on computer work, recall of knowledge, and solving well-defined problems. If your product writes code, analyzes documents, or answers expert questions, the Intelligence Index is measuring close to your use case.&lt;/p&gt;

&lt;p&gt;The leaderboard offers much less insight for products that handle collaborative or interactive tasks. If your product handles customer conversations, team handoffs, scheduling, or anything physical, run your own evaluation on your own tasks, because none of the 21 evaluations scores those activities. A model leading the public leaderboard might not show an advantage on unmeasured coordination tasks.&lt;/p&gt;

&lt;p&gt;An internal test set built from your own tasks shows whether a model asks clarifying questions, respects user constraints and fits the way your team hands off work. Tokely gives one API key for many models, which makes running the same task set across several models cheap to set up.&lt;/p&gt;

&lt;h2&gt;
  
  
  Methodology and limitations
&lt;/h2&gt;

&lt;p&gt;Our analysis relies on the O*NET 31.0 Work Activities file, which provides importance ratings for 41 Generalized Work Activities; 911 occupations have all 41 rated. We downloaded this dataset directly from onetcenter.org on November 3, 2026. On the evaluation side, we extracted the list of active evaluations from the Artificial Analysis methodology page on November 3, 2026, referencing the evaluation papers and announcements linked in the CSV.&lt;/p&gt;

&lt;p&gt;Coding was done by one Tokely analyst at the activity level, from each evaluation's published description, and is a judgment call. A stricter or looser coder would move individual activities between categories. Because our goal was assessing general alignment, we evaluated benchmarks at the level of broad work activities rather than individual prompt statements.&lt;/p&gt;

&lt;p&gt;Occupations are not weighted by employment, so the medians describe the typical O*NET occupation, not the typical worker. Ties for an occupation's top activity are resolved in O*NET element order. In addition, an activity counts as tested if at least one evaluation targets it, regardless of how many tasks or how hard they are.&lt;/p&gt;

&lt;p&gt;The data is a snapshot of one leaderboard's evaluation list on November 3, 2026. Benchmark providers update their rosters, and new evaluations appear over time. These numbers describe that one evaluation list at the time of the snapshot, not every benchmark in use.&lt;/p&gt;

&lt;h2&gt;
  
  
  Download the data
&lt;/h2&gt;

&lt;p&gt;We have published the underlying mapping data in two CSV files. The first file contains the evaluation-to-activity map covering 21 evaluations, index weight, task format, O*NET activity, source URL, and verification date. The second file provides per-activity coverage details across all 41 activities, occupations rating each 4 or higher, mean importance, evaluations testing it, and index weight.&lt;/p&gt;

&lt;p&gt;We make both datasets freely available for developer research. Cite as: Tokely, "Do AI Benchmarks Measure Real Work? 21 Leaderboard Evaluations Mapped to 41 O*NET Work Activities", November 2026, &lt;a href="https://tokely.me/blog/ai-benchmarks-vs-real-work-2026" rel="noopener noreferrer"&gt;https://tokely.me/blog/ai-benchmarks-vs-real-work-2026&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/ai-benchmarks-vs-real-work-2026" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>machinelearning</category>
      <category>datascience</category>
    </item>
    <item>
      <title>Jev by TypeSafe vs Small LLMs: Accuracy, Speed and Cost per Decision (2026 Benchmark)</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Mon, 02 Nov 2026 09:44:07 +0000</pubDate>
      <link>https://dev.to/tokely/jev-by-typesafe-vs-small-llms-accuracy-speed-and-cost-per-decision-2026-benchmark-2fab</link>
      <guid>https://dev.to/tokely/jev-by-typesafe-vs-small-llms-accuracy-speed-and-cost-per-decision-2026-benchmark-2fab</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Research scope:&lt;/strong&gt; This study combines one benchmark we ran on November 2, 2026 (100 Banking77 test messages, 10 intents, six models, one request each) with official TypeSafe documentation read the same day and official list prices verified October 5, 2026. Costs are list prices multiplied by the tokens each API reported; they are not Tokely invoices.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Jev 1.14.0 classified 97 of 100 Banking77 messages correctly, landing between Claude Haiku 5.5 at 98 and Gemini 2.5 Flash-Lite at 96. Its median response time was 0.62 s, compared to 1.19 s to 3.41 s across four small LLMs. At official list prices, 1M requests cost $19.78 on Jev, which sits below three of the four LLMs and runs 1.1x the cost of GPT-4.1 nano at $17.78.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is Jev?
&lt;/h2&gt;

&lt;p&gt;Jev is a System One decision model from TypeSafe AI, an AI lab based in San Francisco. Instead of generating freeform text, Jev answers typed questions about a piece of content designated as the state and returns probabilities. TypeSafe introduced System One models and Jev on September 15, 2026, in a blog post by founder Diogo Almeida. The name System One references Daniel Kahneman's description of fast, intuitive System 1 human cognition, while Jev takes its name from the economist William Stanley Jevons.&lt;/p&gt;

&lt;p&gt;TypeSafe says Jev is trained using Reinforcement Learning for Calibrated Decisions, an approach it calls RLCD. This training target aims at output probabilities where higher confidence directly matches higher observed accuracy. Two versions of the model are currently active: jev-1.13.0 and jev-1.14.0, which became available on October 14, 2026. The alias jev-latest routes directly to jev-1.14.0.&lt;/p&gt;

&lt;p&gt;Calls to Jev support four question types. A noul question produces the probability of a yes or true outcome, expressed on a continuous scale from 0 to 1. A choice question selects one option from up to 255 named candidates, accompanied by individual probabilities and an overall confidence score. A score question places the input onto an ordered scale of up to 10 distinct levels, while a box question places a bounding box over an image, a capability restricted to jev-1.14.0 and marked experimental by TypeSafe.&lt;/p&gt;

&lt;p&gt;API consumers interact with Jev via POST /v1/systemone using a JSON payload containing model, state, and questions. The questions field accepts an object keyed by user-defined identifiers. Requests accept standard limits of 64k tokens per request and 32k tokens per question, expanding to 262k tokens when callers provide the TypeSafe-Danger-Zone-Long-Context header. TypeSafe prices Jev at $0.042 per 1M input tokens, which equals $42 per billion tokens, while billed output tokens remain free.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did we measure?
&lt;/h2&gt;

&lt;p&gt;Our benchmark evaluated 100 customer support messages drawn from the Banking77 test set, published by PolyAI under the CC BY 4.0 license. We sampled 10 specific intents at random using random seed 77, selecting 10 individual messages for each intent. The selected intents include card linking, card payment with a wrong exchange rate, contactless not working, country support, disposable card limits, exchange charge, fiat currency support, getting a virtual card, top-up limits, and Visa or Mastercard. Several pairs represent semantically adjacent issues, most visibly exchange charge alongside card payment with a wrong exchange rate.&lt;/p&gt;

&lt;p&gt;Every test message was dispatched once across six distinct model configurations through the Tokely API on November 2, 2026. We evaluated Jev 1.14.0 and Jev 1.13.0 using a single choice question configured with the 10 intents as its evaluation criteria. Alongside Jev, we submitted the identical messages to four low-cost LLMs: Claude Haiku 5.5, GPT-6 Luna, Gemini 2.5 Flash-Lite, and GPT-4.1 nano. Each LLM received a system prompt enumerating the same 10 intents, set to return a structured JSON object at temperature 0 with a cap of 400 output tokens.&lt;/p&gt;

&lt;p&gt;The complete run yielded 600 individual requests, every one of which resolved successfully with an HTTP 200 status code. Calls executed sequentially, originating from a Tokely server in Finland. Latencies are full round trips measured from that server. Cost calculations apply developer list prices against the exact token volumes recorded by each respective provider API.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 1: Jev answered in 0.62 seconds, 1.9x faster than the fastest LLM
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdabdzlxyp2235krn15a9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdabdzlxyp2235krn15a9.png" alt="Chart of response times: Jev 1.13.0 median 0.60 s, 90th percentile 0.80 s, Jev 1.14.0 median 0.62 s, 90th percentile 0.74 s, GPT-4.1 nano median 1.19 s, 90th percentile 1.57 s, Gemini 2.5 Flash-Lite median 1.58 s, 90th percentile 8.93 s, GPT-6 Luna median 1.90 s, 90th percentile 4.29 s, Claude Haiku 5.5 median 3.41 s, 90th percentile 6.79 s." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;End-to-end response time per request, median and 90th percentile, 100 Banking77 messages per model, measured November 2, 2026 from a Tokely server in Finland.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Response latencies clustered into two distinct performance tiers across the six evaluated engines. Median response times registered at 0.60 s for Jev 1.13.0, 0.62 s for Jev 1.14.0, 1.19 s for GPT-4.1 nano, 1.58 s for Gemini 2.5 Flash-Lite, 1.90 s for GPT-6 Luna, and 3.41 s for Claude Haiku 5.5. Jev 1.14.0 cleared the benchmark 1.9x faster than GPT-4.1 nano and 5.5x faster than Claude Haiku 5.5 at the median.&lt;/p&gt;

&lt;p&gt;Tail latencies separated the two groups further. At the 90th percentile, Jev 1.14.0 clocked 0.74 s and Jev 1.13.0 recorded 0.80 s, while GPT-4.1 nano reached 1.57 s, GPT-6 Luna hit 4.30 s, Claude Haiku 5.5 reached 6.79 s, and Gemini 2.5 Flash-Lite extended to 8.93 s. Nine in ten Jev requests finished within 0.80 s, and the slowest took 1.63 s, while the LLM tails stretched from 1.57 to 8.93 seconds.&lt;/p&gt;

&lt;p&gt;TypeSafe quotes baseline end-to-end latencies between 70 ms and 500 ms for its own internal measurements. TypeSafe says its published evaluations are generally run from the US West Coast. Our recorded latencies include the network time from our server in Finland.&lt;/p&gt;

&lt;p&gt;GPT-6 Luna is a reasoning model: on average, 27.6 of its 43.9 output tokens per request were reasoning tokens.&lt;/p&gt;
&lt;h2&gt;
  
  
  Finding 2: 97% accuracy, between Claude Haiku 5.5 and Gemini 2.5 Flash-Lite
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjrdh80pwwu61z70drijr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjrdh80pwwu61z70drijr.png" alt="Bar chart of intent accuracy on 100 Banking77 test messages: Claude Haiku 5.5 98%, Jev 1.14.0 97%, Jev 1.13.0 97%, Gemini 2.5 Flash-Lite 96%, GPT-6 Luna 94%, GPT-4.1 nano 86%." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Share of 100 Banking77 test messages (10 intents) where each model returned the labelled intent, November 2, 2026.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Accuracy remained high across five of the six evaluated endpoints. Claude Haiku 5.5 achieved top accuracy with 98 correct intents out of 100, followed immediately by Jev 1.14.0 and Jev 1.13.0 at 97 correct answers each. Gemini 2.5 Flash-Lite followed closely with 96 correct classifications, GPT-6 Luna reached 94, and GPT-4.1 nano fell behind with 86.&lt;/p&gt;

&lt;p&gt;Jev 1.14.0 produced three misclassifications across the 100 benchmark items. The model assigned a fiat currency support question to top-up limits, routed a card linking message into getting a virtual card, and placed a contactless payment problem under card linking. GPT-4.1 nano struggled primarily on fine distinctions between foreign currency fees, sorting 5 of the 10 wrong-exchange-rate queries into the broader exchange charge bucket.&lt;/p&gt;

&lt;p&gt;Model output formatting introduced edge cases on generative endpoints that did not appear with Jev. GPT-6 Luna failed an exact match check on one request by returning "getting virtual card" with spaces instead of the exact label from the prompt. By contrast, a Jev choice response maps strictly to one of the predefined criteria keys supplied in the payload, eliminating schema parsing drift.&lt;/p&gt;

&lt;p&gt;These accuracy differences should be interpreted within standard sampling margins. Across a target run of 100 individual evaluation samples, deviations of one or two correct answers fall fully within expected statistical noise. Both Jev models demonstrated intent discrimination capabilities equivalent to current small LLMs.&lt;/p&gt;
&lt;h2&gt;
  
  
  Finding 3: The free-output trade
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F59qyndsdgwevozyigobg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F59qyndsdgwevozyigobg.png" alt="Bar chart of the list price of one million benchmark requests: GPT-4.1 nano $17.78, Jev 1.14.0 $19.78, Jev 1.13.0 $19.78, Gemini 2.5 Flash-Lite $32.84, GPT-6 Luna $36.32, Claude Haiku 5.5 $46.03." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;List price of 1M requests at the mean input and output tokens each API reported in our run. Jev output tokens are free.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;We define "the free-output trade" as the economic dynamic observed in our benchmark where Jev billed 1.8x to 3.3x more input tokens than the LLMs for the same message, but returned its answer with zero billed output tokens. This trade-off dictates whether Jev or a minimal LLM yields lower costs for a given classification task.&lt;/p&gt;

&lt;p&gt;Average token consumption varied sharply by architecture on the Banking77 workload. Jev logged an average of 471.1 input tokens and 118.8 output tokens per query, though none of its output tokens accrued billing charges under TypeSafe's pricing rules. Among the LLMs, Claude Haiku 5.5 averaged 232.5 input tokens and 45.6 output tokens, GPT-6 Luna consumed 143.8 input tokens and 43.9 output tokens, Gemini 2.5 Flash-Lite processed 268.4 input tokens and 15.0 output tokens, and GPT-4.1 nano required 144.8 input tokens alongside 8.2 output tokens. Jev and the LLMs received the same message and the same 10 intents; the difference is in how each API counts its tokens.&lt;/p&gt;

&lt;p&gt;At official developer list prices, handling 1M such classification queries totals $19.78 on Jev. GPT-4.1 nano came in slightly lower at $17.78 per 1M requests, representing 0.90x the expense of Jev. The remaining three models cost substantially more: Gemini 2.5 Flash-Lite totaled $32.84 (1.66x Jev), GPT-6 Luna totaled $36.32 (1.84x Jev), and Claude Haiku 5.5 accumulated $46.03 (2.33x Jev).&lt;/p&gt;

&lt;p&gt;Output token rates exert a major influence on LLM expense profiles. Billed output tokens represented 49.5% of total spend for Claude Haiku 5.5 and 60.4% of spend for GPT-6 Luna, while settling between 18% and 19% for Gemini 2.5 Flash-Lite and GPT-4.1 nano. Through Tokely, Jev input tokens list at $0.0294 per 1M tokens, a 30% reduction from TypeSafe's direct list price, bringing the total expense for 1M identical requests down to $13.85.&lt;/p&gt;
&lt;h2&gt;
  
  
  Finding 4: At TypeSafe's own example, the gap is wider
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffkglpcka5n5t6kqslol8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffkglpcka5n5t6kqslol8.png" alt="Bar chart of the list price of one million decisions at 428 input and 73 output tokens each: Jev (1.13.0 or 1.14.0) $17.98, Qwen-Flash $25.18, GPT-5 nano $50.60, Gemini 2.5 Flash-Lite $72.00, GPT-4.1 nano $72.00, Claude Haiku 5.5 $79.30, GPT-6 Luna $79.30, GPT-4o mini $108.00, DeepSeek V4.1 Flash $108.00, GPT-5.6 Luna $173.20, Gemini 3.1 Flash-Lite $216.50, GPT-5 mini $253.00." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;List price of 1M decisions at 428 input and 73 output tokens, the usage of TypeSafe's quickstart request. Official list prices; GPT-6 Astra and Claude Fable 5.1 ($7,930) are left out of the chart.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The pricing variance between Jev and general-purpose LLMs expands when evaluating TypeSafe's reference workload. In the quickstart example published in TypeSafe's developer documentation, a single text input evaluated against three questions consumes 428 input tokens and generates 73 output tokens. Calculating pricing under the assumption that LLMs process those exact token quantities highlights the extreme ends of provider pricing scales.&lt;/p&gt;

&lt;p&gt;Under that matched-token assumption, executing 1M decisions costs $17.98 on Jev, compared to $25.18 on Qwen-Flash at 1.4x the cost. GPT-5 nano reaches $50.60 (2.8x), while Gemini 2.5 Flash-Lite and GPT-4.1 nano both reach $72.00 (4.0x). Claude Haiku 5.5 and GPT-6 Luna both land at $79.30 (4.4x), followed by GPT-4o mini and DeepSeek V4.1 Flash at $108.00 (6.0x), GPT-5.6 Luna at $173.20 (9.6x), Gemini 3.1 Flash-Lite at $216.50 (12.0x), and GPT-5 mini at $253.00 (14.1x).&lt;/p&gt;

&lt;p&gt;At the top of the provider spectrum, GPT-6 Astra and Claude Fable 5.1 would bill $7,930 for that same 1M request volume, or 441x the cost of Jev. This is close to the "444.6x cheaper" figure that TypeSafe shows on its home page.&lt;/p&gt;

&lt;p&gt;Our empirical benchmark explains why that theoretical 441x figure functions primarily as an upper bound. In our benchmark, the small LLMs used fewer input tokens than Jev for the same message, and the measured cost of the small LLMs ranged from 0.9x to 2.3x Jev.&lt;/p&gt;
&lt;h2&gt;
  
  
  Finding 5: Confidence tells you which answers to trust
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frri05p99lh9focawk7xh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frri05p99lh9focawk7xh.png" alt="Chart for Jev 1.14.0 by confidence threshold: at 0.5 it handles 98% of messages with 97% accuracy, at 0.7 it handles 94% of messages with 99% accuracy, at 0.9 it handles 91% of messages with 99% accuracy." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Jev 1.14.0 on 100 Banking77 messages: share of messages at or above each confidence threshold and accuracy on those messages.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Jev returns an explicit confidence metric ranging from 0 to 1 with every choice response. The value reaches 1 when the model assigns all probability density to a single candidate, and drops toward 0 when probability distributes uniformly across the available options. This property allows developers to construct automated routing rules based on numerical certainty.&lt;/p&gt;

&lt;p&gt;In our Banking77 evaluation, Jev 1.14.0 produced 91 classifications with a confidence score of 0.9 or greater. Out of those 91 high-confidence predictions, 90 were correct, establishing a 98.9% accuracy rate for that segment. The model issued 7 predictions with confidence values between 0.5 and 0.9, yielding 5 correct classifications and 2 errors.&lt;/p&gt;

&lt;p&gt;Setting an automated execution threshold at 0.7 confidence would have approved 94% of incoming customer messages while maintaining a 98.9% accuracy mark on the automated volume. The remaining 6 ambiguous items would have been flagged for secondary evaluation. TypeSafe's documentation suggests initial baseline thresholds of 0.7 for yes outcomes and 0.3 for no outcomes on noul questions, and advises testing thresholds on your own data. Across all 100 test items in our benchmark, Jev 1.13.0 and Jev 1.14.0 selected the identical winning intent label every time.&lt;/p&gt;
&lt;h2&gt;
  
  
  How do you call Jev through Tokely?
&lt;/h2&gt;

&lt;p&gt;Tokely provides access to jev-1.14.0 and jev-1.13.0 via the standard POST /v1/systemone schema at &lt;a href="https://api.tokely.me/v1/systemone" rel="noopener noreferrer"&gt;https://api.tokely.me/v1/systemone&lt;/a&gt; using a single Tokely API key. Tokely accepts text states with noul, choice and score questions, up to 64 per request. Developers can bundle multiple queries into a single payload, a technique that TypeSafe's developer cookbook reports was 12.2x cheaper and 10.0x faster than issuing separate API requests in its internal testing.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl https://api.tokely.me/v1/systemone &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &lt;/span&gt;&lt;span class="nv"&gt;$TOKELY_API_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Content-Type: application/json"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{
    "model": "jev-1.14.0",
    "state": "Do you guys accept mastercard or visa?",
    "questions": {
      "intent": {
        "type": "choice",
        "instructions": "Which intent does this bank customer message express?",
        "criteria": {
          "visa_or_mastercard": "visa or mastercard",
          "card_linking": "card linking",
          "top_up_limits": "top up limits"
        }
      },
      "is_urgent": {"type": "noul", "instructions": "The message conveys urgency"}
    }
  }'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A common mistake in unofficial guides is placing fields named question, options, or scale inside a question. The official TypeSafe API schema requires instructions, alongside a criteria field for choice and score evaluations. For choice questions, criteria must be formatted as an object mapping string identifiers to detailed descriptions, while score questions require criteria formatted as an ordered list of level definitions.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should teams do with this?
&lt;/h2&gt;

&lt;p&gt;Engineering teams should deploy Jev when the task requires discrete categorization, binary filtering, or rating scales, and where request latency affects production workflows. Routing pipelines, user intent classification, feature gating, and content moderation fit this profile directly. In our benchmark, Jev matched the accuracy of small LLMs while operating at roughly half or less of their median response times, all while returning strictly conforming structured objects.&lt;/p&gt;

&lt;p&gt;Development teams should use the returned confidence scores to build layered fallback pipelines. Requests exceeding an empirically validated confidence cutoff can process without human intervention, while ambiguous items route automatically to human review queues or larger generative models. Calibrating this boundary on task-specific test sets allows systems to maintain high classification standards on production traffic.&lt;/p&gt;

&lt;p&gt;Architects should avoid assuming Jev is universally the cheapest alternative across every possible classification workload. Jev tallies billable input tokens for every option description contained in its criteria definitions, meaning tasks with dozens of lengthy definitions can cost as much as lightweight LLMs like GPT-4.1 nano. Engineering teams should run cost audits using their own production prompt distributions before committing to a single architecture. Tokely provides a single unified API key to access Jev, Claude, GPT, and Gemini, enabling direct head-to-head testing across models: &lt;a href="https://tokely.me/models/jev-1.14.0" rel="noopener noreferrer"&gt;Jev 1.14.0 on Tokely&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;Is Jev an LLM? No: TypeSafe says System One models do not write replies, produce code or explain their reasoning; they return structured answers.&lt;/p&gt;

&lt;p&gt;Can I call Jev with the OpenAI SDK? No, /v1/systemone is a different format; use plain HTTP, TypeSafe's Python or TypeScript SDK, or LangChain4j.&lt;/p&gt;

&lt;p&gt;How much does Jev cost? $0.042 per 1M input tokens at TypeSafe, $0.0294 on Tokely, output free.&lt;/p&gt;

&lt;p&gt;Which version should I use? jev-1.14.0 is the newest and the target of jev-latest; TypeSafe says it gives 60 days' notice before jev-1.13.0 is deprecated; pin a version in production.&lt;/p&gt;

&lt;p&gt;Does Jev accept images? TypeSafe offers images and the box type as experimental features behind the TypeSafe-Danger-Zone-Images header; through Tokely, Jev takes text with noul, choice and score questions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Methodology and limitations
&lt;/h2&gt;

&lt;p&gt;This benchmark evaluated 100 messages spanning 10 intents drawn from a single English-language public dataset. Adjusting the task context, target language, prompt phrasing, or option counts could alter comparative rankings, and performance gaps of one or two correct answers fall within statistical noise. All tests executed as sequential, single-request calls on November 2, 2026, originating from a Tokely test host in Finland routing through the Tokely gateway engine. Five LLM requests experienced retries due to host CPU saturation on our test server, with reported latencies reflecting the timing of the final successful transaction.&lt;/p&gt;

&lt;p&gt;LLM prompts contained the identical list of 10 intent descriptions embedded in a system instruction, evaluated at temperature 0 with a 400 output token limit, without prompt engineering or fine-tuning for any specific endpoint. Cost numbers reflect official list prices multiplied by the token counts reported in each API response, excluding provider volume discounts, prompt caching tiers, batch discounts, and localized taxes unless specifically noted. The quickstart comparison assumes LLMs consume token counts equivalent to Jev's format, which our empirical data demonstrates is not the case in practice. TypeSafe's latency and cost claims come from its own evaluations.&lt;/p&gt;

&lt;h2&gt;
  
  
  Data and citation
&lt;/h2&gt;

&lt;p&gt;Benchmark datasets and cost breakdown sheets are freely available for external verification: per-model benchmark results can be accessed at &lt;a href="https://tokely.me/blog-media/jev-typesafe-benchmark-2026/jev-benchmark-2026-11.csv" rel="noopener noreferrer"&gt;jev-benchmark-2026-11.csv&lt;/a&gt;, while the list-price comparison across quickstart workloads is published at &lt;a href="https://tokely.me/blog-media/jev-typesafe-benchmark-2026/decision-cost-2026-11.csv" rel="noopener noreferrer"&gt;decision-cost-2026-11.csv&lt;/a&gt;. Primary documentation sources include the &lt;a href="https://docs.typesafe.ai/models" rel="noopener noreferrer"&gt;TypeSafe documentation&lt;/a&gt;, the official launch article &lt;a href="https://typesafe.ai/blog/introducing-system-one-models-and-jev" rel="noopener noreferrer"&gt;Introducing System One Models and Jev&lt;/a&gt;, and the &lt;a href="https://github.com/PolyAI-LDN/task-specific-datasets" rel="noopener noreferrer"&gt;Banking77 dataset&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Cite as: Tokely (2026). Jev by TypeSafe vs Small LLMs: Accuracy, Speed and Cost per Decision (2026 Benchmark). &lt;a href="https://tokely.me/blog/jev-typesafe-benchmark-2026" rel="noopener noreferrer"&gt;https://tokely.me/blog/jev-typesafe-benchmark-2026&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/jev-typesafe-benchmark-2026" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>machinelearning</category>
      <category>benchmark</category>
    </item>
    <item>
      <title>Claude Account Bans After ID Verification: What Happened in October 2026</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Fri, 30 Oct 2026 15:23:43 +0000</pubDate>
      <link>https://dev.to/tokely/claude-account-bans-after-id-verification-what-happened-in-october-2026-4mij</link>
      <guid>https://dev.to/tokely/claude-account-bans-after-id-verification-what-happened-in-october-2026-4mij</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Since October 29, 2026, users with Russian passports report that their Claude accounts are banned right after they complete identity verification through Persona, Anthropic's verification partner. Reports include paying Pro and Max subscribers and Russian citizens who live in supported countries such as New Zealand, Georgia and Armenia. Anthropic has not commented. This is the third reported wave of Claude bans affecting Russian users in 2026, after May and early October.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened on October 29, 2026?
&lt;/h2&gt;

&lt;p&gt;On October 29, &lt;a href="https://meduza.io/en/feature/2026/10/29/claude-users-say-their-accounts-were-banned-after-verification-showed-a-russian-passport" rel="noopener noreferrer"&gt;Meduza&lt;/a&gt;, &lt;a href="https://istories.media/news/2026/10/29/claude-blokiruet-akkaunti-grazhdan-rf-posle-protseduri-identifikatsii/" rel="noopener noreferrer"&gt;iStories&lt;/a&gt;, &lt;a href="https://t-j.ru/news/claude-kyc-explained/" rel="noopener noreferrer"&gt;T-Zhurnal&lt;/a&gt; and &lt;a href="https://united24media.com/world/a-russian-passport-can-reportedly-get-you-banned-from-claude-even-abroad-23927" rel="noopener noreferrer"&gt;UNITED24 Media&lt;/a&gt; published user reports with the same pattern. Claude stops answering and asks the user to verify their identity. The user uploads a Russian passport and takes a selfie. The account is banned shortly after, in one Telegram report "within a minute."&lt;/p&gt;

&lt;p&gt;One case, first posted on Reddit, involves a Russian citizen living in New Zealand on a four-year visa. He paid for Claude, used Claude Code, was charged two days before the ban, and lost access right after uploading his Russian international passport. Meduza also cites complaints from users with Russian documents who live in Georgia and Armenia.&lt;/p&gt;

&lt;p&gt;A ban notice quoted by Meduza reads: "Our automated systems detected a large number of signals associated with your account that violate our Usage Policy." It did not say which rule was broken. A user on X said that after the ban he could only export his chats, and his appeal was rejected.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does Claude identity verification work?
&lt;/h2&gt;

&lt;p&gt;Anthropic describes the process in its help article &lt;a href="https://support.claude.com/en/articles/14328960-identity-verification-on-claude" rel="noopener noreferrer"&gt;Identity verification on Claude&lt;/a&gt;, dated August 11, 2026. The key points:&lt;/p&gt;

&lt;p&gt;Anthropic uses Persona Identities as its verification partner and says it is "rolling out identity and business verification for a few use cases." The article does not say that every user will be asked.&lt;/p&gt;

&lt;p&gt;You need an original, physical, government-issued photo ID, such as a passport, driver's license or national ID card, plus a selfie. Digital or mobile IDs, photocopies, screenshots, student cards and bank cards are not accepted. Meduza describes the flow as choosing the region of the document, uploading a photo of it and completing a face scan.&lt;/p&gt;

&lt;p&gt;The ID and selfie are collected and held by Persona, not on Anthropic's systems. The help article links an appeal form for bans and a separate form for failed verification. It does not mention nationality, visas, residency or refunds.&lt;/p&gt;

&lt;p&gt;According to iStories, Anthropic warned in June 2026 that it could request a passport and selfie from July, and said the check was already used on accounts from countries where Claude is not officially available.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who is affected?
&lt;/h2&gt;

&lt;p&gt;Based on the published reports, the bans follow verification with a Russian passport. The reported cases include people who live in Russia and use a VPN, and Russian citizens who live in supported countries: New Zealand, Georgia and Armenia.&lt;/p&gt;

&lt;p&gt;Meduza reports that the ban also reaches people who do not live in Russia but lack a residence permit elsewhere. iStories reports that Russians who live in supported countries are affected as well. The New Zealand case, a long-term visa holder, matches the broader iStories description.&lt;/p&gt;

&lt;p&gt;Users from mainland China are also asked to verify before they can send messages. Some report bans after uploading a passport, while others with Chinese passports say they passed. UNITED24 cites unverified Telegram claims that Russian driver's licenses passed when another country was selected in the form. None of this is confirmed by Anthropic.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is this the first wave of bans?
&lt;/h2&gt;

&lt;p&gt;No. Russian media describe at least three waves in 2026.&lt;/p&gt;

&lt;p&gt;May 2026: &lt;a href="https://www.cnews.ru/news/top/2026-05-08_nejroset_claude_poshla_vojnoj" rel="noopener noreferrer"&gt;CNews&lt;/a&gt; reported on May 8, citing Baza, that Anthropic blocked several hundred accounts of Russian users without warning. Owners of blocked profiles reported subscription refunds.&lt;/p&gt;

&lt;p&gt;Early October 2026: &lt;a href="https://ru.themoscowtimes.com/2026/10/02/polzovateli-ii-ot-claude-v-rossii-pozhalovalis-na-blokirovku-akkauntov-a207652" rel="noopener noreferrer"&gt;The Moscow Times&lt;/a&gt; reported on October 2, citing The Bell, that Russian users began losing access from October 1. Notices cited suspicious signals of rule violations. One user had paid $200 per month for Claude Max for over a year and was connecting through a virtual server in Helsinki. Hong Kong users on VPNs reported similar losses of access.&lt;/p&gt;

&lt;p&gt;Late October 2026: The current wave, tied to Persona verification with Russian documents.&lt;/p&gt;

&lt;p&gt;For scale, The Moscow Times cites Anthropic's own transparency reporting: from January to June 2026, Anthropic banned 11.4 million accounts across all countries, received about 398,000 appeals and restored about 42,000 accounts.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why is Anthropic banning these accounts?
&lt;/h2&gt;

&lt;p&gt;Anthropic has not explained the current bans publicly. Meduza writes that what drives them "remains unclear," and iStories says Anthropic has not explained the reasons.&lt;/p&gt;

&lt;p&gt;What is on the record is Anthropic's &lt;a href="https://www.anthropic.com/supported-countries" rel="noopener noreferrer"&gt;Supported Regions Policy&lt;/a&gt;. It states that "any country or region not listed is unsupported." Russia, Belarus, mainland China and Hong Kong are not on the list. The policy covers use by people physically located in an unsupported region, and use by companies headquartered in an unsupported region or majority owned or controlled from one. The version published on the page shows an effective date of November 12, 2026.&lt;/p&gt;

&lt;p&gt;The policy text is based on location, headquarters and ownership. It does not mention citizenship. That is why bans of Russian citizens who live in New Zealand or Georgia surprised users. Explanations offered by experts quoted in the press, such as frequent IP and region changes through VPNs, stricter checks of unverified accounts, or payment patterns, remain unconfirmed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do you get a refund for a banned Claude subscription?
&lt;/h2&gt;

&lt;p&gt;Sometimes, but nothing guarantees it. CNews reported refunds after the May wave, and UNITED24 says subscription payments were refunded in some October cases. Meduza's New Zealand case says the user was charged two days before the ban, with no refund mentioned. Anthropic's help article does not cover refunds for banned accounts. Use the appeal form linked in the help article to raise both the ban and the payment.&lt;/p&gt;

&lt;h2&gt;
  
  
  What can you do if your Claude account is banned?
&lt;/h2&gt;

&lt;p&gt;Appeal first. Anthropic's help article links an appeal form. Appeals do succeed: about 42,000 of roughly 398,000 appeals in the first half of 2026 led to restored accounts, about one in ten.&lt;/p&gt;

&lt;p&gt;Export your data. Users report that chat export can still work after a ban. Do it before anything else, especially if you keep project files or long conversations in Claude.&lt;/p&gt;

&lt;p&gt;Check where you use Claude from. The Supported Regions Policy depends on where you are physically located and where your company is based. If you work from a supported country, keep your account details, billing and location consistent with that.&lt;/p&gt;

&lt;p&gt;Separate the app from the API. A claude.ai subscription is a consumer account. Claude models are also available through the &lt;a href="https://docs.anthropic.com" rel="noopener noreferrer"&gt;Claude API&lt;/a&gt;, Amazon Bedrock, Google Cloud Vertex AI and API platforms such as &lt;a href="https://tokely.me/docs/models" rel="noopener noreferrer"&gt;Tokely&lt;/a&gt;, where you pay per token and connect tools like Claude Code with an API key. Each platform has its own account terms, so read them for your situation.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;Does Anthropic ban everyone with a Russian passport? Anthropic has made no such statement, and its published policy does not mention citizenship. The reports describe bans right after verification with a Russian passport, including for people who live in supported countries.&lt;/p&gt;

&lt;p&gt;Is identity verification required for all Claude users? No. Anthropic says it is rolling verification out "for a few use cases." Users report that Claude stops answering until they verify, so in practice it acts as a gate on affected accounts.&lt;/p&gt;

&lt;p&gt;Does Anthropic keep my passport photo? According to its help article, the ID and selfie are collected and held by Persona, not on Anthropic's systems.&lt;/p&gt;

&lt;p&gt;Can a banned Claude account be restored? Sometimes. Use the appeal form in Anthropic's identity verification help article. In the first half of 2026, about 42,000 accounts were restored after roughly 398,000 appeals.&lt;/p&gt;

&lt;p&gt;Is Russia a supported country for Claude? No. Russia, Belarus, mainland China and Hong Kong are not on Anthropic's list of supported regions.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/claude-account-bans-identity-verification-2026" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>claude</category>
      <category>security</category>
      <category>privacy</category>
    </item>
    <item>
      <title>Are Chinese AI Models Getting More Expensive? API Prices by Generation (2026)</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Thu, 29 Oct 2026 02:30:28 +0000</pubDate>
      <link>https://dev.to/tokely/are-chinese-ai-models-getting-more-expensive-api-prices-by-generation-2026-35lf</link>
      <guid>https://dev.to/tokely/are-chinese-ai-models-getting-more-expensive-api-prices-by-generation-2026-35lf</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Research scope:&lt;/strong&gt; This study compares official API list prices verified October 29, 2026. DeepSeek is the only price history: its August 1 (archived page), August 16 and September 10, 2026 price tables. For the other developers, generations are compared at the prices listed on October 29, 2026; earlier versions are not historical launch prices.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Partly, yes. DeepSeek V4 Flash output costs $1.32 per 1M tokens at peak hours, 4.7x the $0.28 single rate on its August 1, 2026 price page, and the newest Kimi and GLM flagships list at 2.15x to 2.34x their predecessors, a gap we call the generation premium. Kimi K3.1 Pro lists at $2 input and $10 output, the same as GPT-6.1 Sol and Claude Sonnet 5.5.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did we measure?
&lt;/h2&gt;

&lt;p&gt;We collected official API list prices per 1M tokens (input, cached input and output) for 24 models from five Chinese developers: DeepSeek, Alibaba (Qwen), Moonshot AI (Kimi), Z.ai (GLM) and MiniMax. For comparison we added six US reference models from OpenAI and Anthropic and two DeepSeek models as resold by Alibaba Cloud. Every price comes from the developer's own pricing page, verified October 29, 2026.&lt;/p&gt;

&lt;p&gt;We used the standard tier and the lowest context band. Qwen prices are Alibaba Cloud Model Studio prices for the Singapore (International) region. To compare models with one number, we use a blended price that weights three input tokens to one output token.&lt;/p&gt;

&lt;p&gt;For DeepSeek we also have dated price tables: its pricing page as captured on August 1, 2026, and the price tables in its August 13 and September 10, 2026 announcements. That makes DeepSeek the only developer in this study where we describe a price change over time. Everything else is a comparison of prices listed on October 29, 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 1: DeepSeek's peak output price is 4.7x its August 1 rate
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp6y6ob8l2xfytysqt4zq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp6y6ob8l2xfytysqt4zq.png" alt="Bar chart of DeepSeek output prices per 1M tokens: V4 Flash $0.28 on August 1, $0.66 off-peak and $1.32 peak from August 16; V4.1 Flash $0.60 off-peak and $1.20 peak from September 10; V4 Pro $0.87 on August 1, $1.98 off-peak and $3.96 peak from August 16." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;DeepSeek output price per 1M tokens in its August 1 (archived page), August 16 and September 10, 2026 price tables. Peak hours: 01:00 to 04:00 and 06:00 to 10:00 UTC.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;On August 1, 2026, DeepSeek listed one rate per model. V4 Flash cost $0.14 per 1M input tokens on a cache miss, $0.0028 on a cache hit and $0.28 for output. V4 Pro cost $0.435 input, $0.003625 on a cache hit and $0.87 output. The same page said that peak and off-peak pricing was coming, with peak prices at 2x.&lt;/p&gt;

&lt;p&gt;DeepSeek's August 13 announcement set new prices from 16:00 UTC on August 16, 2026. V4 Flash moved to $0.22 input and $0.66 output off-peak, and $0.44 input and $1.32 output at peak. V4 Pro moved to $0.66 input and $1.98 output off-peak, and $1.32 input and $3.96 output at peak. Peak hours are 01:00 to 04:00 and 06:00 to 10:00 UTC.&lt;/p&gt;

&lt;p&gt;Against the August 1 rates, V4 Flash output costs 4.7x at peak and 2.4x off-peak. V4 Pro output costs 4.6x at peak and 2.3x off-peak, and V4 Pro peak input is 3.0x. These V4 Pro prices are the ones DeepSeek still lists on October 29.&lt;/p&gt;

&lt;p&gt;On September 10, 2026, DeepSeek released V4.1 Flash with its own table: $0.15 input, $0.003 cache hit and $0.60 output off-peak, and $0.30, $0.006 and $1.20 at peak. Peak hours now apply on weekdays only; weekends and Chinese public holidays are off-peak. V4.1 Flash output is still 2.1x the August 1 V4 Flash rate off-peak and 4.3x at peak. The $1.32 output price quoted in recent coverage matches the August 16 peak rate of V4 Flash, and Alibaba Cloud Singapore still lists deepseek-v4-flash-0731 at $0.44 input and $1.32 output in busy hours.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 2: The generation premium
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F04x8x8r86e3vzafikztn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F04x8x8r86e3vzafikztn.png" alt="Bar chart of blended prices per 1M tokens: Kimi K2.6 $1.71, K3 $6.00, K3.1 Pro $4.00; GLM-4.7 $1.00, GLM-5 $1.55, GLM-5.3 $2.15; Qwen-Max $2.80, Qwen3.7-Max $3.75, Qwen3.8-Max $3.00." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Blended price (3 input tokens to 1 output token) per 1M tokens, standard list prices on October 29, 2026. Qwen: Alibaba Cloud Singapore region.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;We define the generation premium as the blended price of a developer's newest flagship divided by the blended price of its last earlier generation, at the prices listed on the same day. On October 29, 2026, it is 2.34x for Kimi and 2.15x for GLM.&lt;/p&gt;

&lt;p&gt;Kimi K2.6 lists at $0.95 input and $4 output, $1.71 blended. Kimi K3 lists at $3 and $15, $6.00 blended or 3.5x K2.6. Kimi K3.1 Pro lists at $2 and $10, $4.00 blended or 2.34x K2.6. Kimi's pricing page says the K2 series closes to new users on October 31, 2026 and will be retired by the end of December 2026, so new accounts start from the K3 price level.&lt;/p&gt;

&lt;p&gt;GLM-4.5, GLM-4.6 and GLM-4.7 all list at $0.60 input and $2.20 output, $1.00 blended. GLM-5 lists at $1 and $3.20, 1.55x. GLM-5.1, GLM-5.2 and GLM-5.3 all list at $1.40 and $4.40, $2.15 blended or 2.15x GLM-4.7.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 3: Qwen and MiniMax break the pattern
&lt;/h2&gt;

&lt;p&gt;In Alibaba's Singapore region, Qwen-Max lists at $1.60 input and $6.40 output, $2.80 blended. Qwen3.7-Max lists at $2.50 and $7.50, $3.75 blended. Qwen3.8-Max lists at $2 and $6, $3.00 blended, which is 1.07x Qwen-Max and below Qwen3.7-Max.&lt;/p&gt;

&lt;p&gt;The Qwen Plus line shows the same mix. Qwen-plus lists at $0.40 input and $1.20 output without thinking ($4 with thinking), $0.60 blended. Qwen3.5-Plus lists at $0.40 and $2.40, Qwen3.6-Plus at $0.50 and $3, and Qwen3.7-Plus at $0.40 and $1.60, $0.70 blended or 1.17x qwen-plus, with a limited-time 20% discount on top.&lt;/p&gt;

&lt;p&gt;For Qwen, the region matters more than the generation. In Alibaba's China (Beijing) region, Qwen-Max lists at $0.345 input and $1.377 output and Qwen3.8-Max at $1.65 and $4.951, a 4.1x blended gap. In Singapore the same pair differs by 1.07x.&lt;/p&gt;

&lt;p&gt;MiniMax M3 lists at $0.30 input and $1.20 output for inputs up to 512K tokens, after a discount the page labels permanent, from $0.60 and $2.40. MiniMax M3.1 Flash lists at $0.15 and $0.60.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 4: Kimi K3.1 Pro lists at the same price as GPT-6.1 Sol and Claude Sonnet 5.5
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F00fcin1ed53p8cs5y59s.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F00fcin1ed53p8cs5y59s.png" alt="Bar chart of blended prices per 1M tokens: Claude Opus 5.5 $8.00, Kimi K3 $6.00, Kimi K3.1 Pro, GPT-6.1 Sol and Claude Sonnet 5.5 $4.00 each, Qwen3.8-Max $3.00, GLM-5.3 $2.15, GPT-6.1 Terra $2.00, DeepSeek V4 Pro $1.98 peak and $0.99 off-peak, MiniMax M3 $0.53." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Blended price per 1M tokens for Chinese and US flagship models, standard list prices on October 29, 2026.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Kimi K3.1 Pro, OpenAI GPT-6.1 Sol and Anthropic Claude Sonnet 5.5 all list at $2 input and $10 output, $4.00 blended. On cached input, Kimi K3.1 Pro lists at $0.20, while GPT-6.1 Sol and Sonnet 5.5 list at $0.10. Kimi K3, at $3 and $15, lists at 1.5x Sonnet 5.5. Claude Opus 5.5 lists at $4 and $20, $8.00 blended.&lt;/p&gt;

&lt;p&gt;Below that price point are Qwen3.8-Max at $3.00 blended, GLM-5.3 at $2.15 (0.54x Sonnet 5.5) and GPT-6.1 Terra at $1 input and $5 output, $2.00 blended. DeepSeek V4 Pro is $1.98 blended at peak and $0.99 off-peak, and MiniMax M3 is $0.53. The cheapest flagship-class options in this study are still Chinese, but the newest Kimi flagship sits at the US price point.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 5: Small US models list below Chinese flash models
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0njoa6t5gp2c76wdhgv2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0njoa6t5gp2c76wdhgv2.png" alt="Bar chart of blended prices per 1M tokens for small models: GPT-6 Luna and Claude Haiku 5.5 $0.200, Qwen3.8-Flash $0.230, GLM-5.3-Flash $0.237, DeepSeek V4.1 Flash $0.263 off-peak and $0.525 peak, MiniMax M3.1 Flash $0.263." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Blended price per 1M tokens for small and fast models, standard list prices on October 29, 2026. Cached input not included.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;GPT-6 Luna and Claude Haiku 5.5 both list at $0.10 input and $0.50 output, $0.200 blended (Haiku 5.5 for prompts up to 100K tokens). Qwen3.8-Flash in Singapore lists at $0.15 and $0.47, $0.230 blended, and GLM-5.3-Flash at $0.15 and $0.50, $0.237. DeepSeek V4.1 Flash off-peak and MiniMax M3.1 Flash both list at $0.15 and $0.60, $0.263 blended or 1.31x GPT-6 Luna. DeepSeek V4.1 Flash at peak is $0.525.&lt;/p&gt;

&lt;p&gt;Chinese small models keep a clear lead on cached input. DeepSeek V4.1 Flash cache hits cost $0.003 per 1M tokens off-peak, against $0.01 for GPT-6 Luna and Haiku 5.5, and MiniMax M3.1 Flash cache reads cost $0.015. Workloads that resend a long, repeated prefix, such as agents with large system prompts, pay less on DeepSeek.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should teams do with this?
&lt;/h2&gt;

&lt;p&gt;On DeepSeek, price by the hour. Off-peak rates are half of peak, and peak runs 01:00 to 04:00 and 06:00 to 10:00 UTC on weekdays, so batch jobs scheduled outside those windows pay the lower rate. Also check where you buy: Alibaba Cloud Singapore lists DeepSeek V4 Pro at a flat $2.40 input and $4.80 output, 1.8x DeepSeek's own peak input price and 3.6x its off-peak input price.&lt;/p&gt;

&lt;p&gt;Re-check the assumption that a Chinese model is always the cheaper choice, model by model. Kimi K3.1 Pro lists at the same price as GPT-6.1 Sol and Sonnet 5.5, and small US models list below Chinese flash models, while DeepSeek off-peak, MiniMax M3 and GLM-5.3 still list well below US flagships. Teams on Kimi K2 models should plan for the cutoff for new users on October 31, 2026.&lt;/p&gt;

&lt;p&gt;Tokely gives one API key for DeepSeek, Qwen, Kimi, GLM, MiniMax, OpenAI, Anthropic and other models, so you can compare and switch them in one place: &lt;a href="https://tokely.me/models" rel="noopener noreferrer"&gt;Tokely models&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;Are Chinese AI APIs still cheaper than OpenAI and Anthropic? Not across the board. DeepSeek V4 Pro off-peak ($0.99 blended), MiniMax M3 ($0.53) and GLM-5.3 ($2.15) list below Claude Sonnet 5.5 and GPT-6.1 Sol ($4.00), but Kimi K3.1 Pro lists at the same $2 input and $10 output, and GPT-6 Luna and Claude Haiku 5.5 ($0.200) list below the Chinese flash models in this study.&lt;/p&gt;

&lt;p&gt;Why are the newest Qwen, Kimi and GLM flagships priced higher than earlier versions? This study compares list prices and does not cover the reasons behind them. What the price pages show on October 29, 2026 is a generation premium of 2.34x for Kimi and 2.15x for GLM, while Qwen3.8-Max in Singapore lists at 1.07x Qwen-Max.&lt;/p&gt;

&lt;p&gt;Which Chinese models list close to their earlier versions? MiniMax M3 lists at $0.30 input and $1.20 output after a permanent 50% discount, Qwen3.8-Max in Singapore lists at 1.07x Qwen-Max, and Qwen3.7-Plus at 1.17x qwen-plus.&lt;/p&gt;

&lt;p&gt;Did DeepSeek raise its API prices? Yes. From 16:00 UTC on August 16, 2026, DeepSeek replaced single rates with peak and off-peak prices: V4 Flash output went from $0.28 to $0.66 off-peak and $1.32 at peak, and V4 Pro output from $0.87 to $1.98 and $3.96. V4.1 Flash, released September 10, lists at $0.60 off-peak and $1.20 at peak.&lt;/p&gt;

&lt;p&gt;How can I pay less for Chinese models? Send DeepSeek traffic outside peak hours (01:00 to 04:00 and 06:00 to 10:00 UTC on weekdays), reuse long prompt prefixes so they bill at cache-hit rates such as DeepSeek's $0.003 per 1M tokens, compare regions on Alibaba Cloud, and check reseller prices against the developer's own page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Methodology and limitations
&lt;/h2&gt;

&lt;p&gt;Prices are official list prices verified October 29, 2026, and every row in the CSV carries a source URL. We used the standard tier and the lowest context band unless noted. Batch discounts, cache-write fees, enterprise contracts, free quotas, taxes and limited-time promotions are excluded: the Qwen3.7-Plus 20% discount is not applied, while MiniMax's permanent 50% discount is applied because the page lists it as the standard rate. Qwen uses Singapore prices, and other regions differ.&lt;/p&gt;

&lt;p&gt;Generations are ordered by version number. Except for DeepSeek, this study does not track price history: earlier-generation prices are the ones listed on October 29, 2026. DeepSeek's August 1 prices come from an archived copy of its pricing page (Internet Archive, captured August 1, 2026). The 3:1 blend is our assumption, and output-heavy workloads change the ratios. We did not measure quality, speed or tokens per task, which differ between models.&lt;/p&gt;

&lt;h2&gt;
  
  
  Data and citation
&lt;/h2&gt;

&lt;p&gt;Both datasets are free to download: list prices for 34 model rows with source URLs, &lt;a href="https://tokely.me/blog-media/chinese-ai-model-api-prices-2026/chinese-ai-model-api-prices-2026.csv" rel="noopener noreferrer"&gt;chinese-ai-model-api-prices-2026.csv&lt;/a&gt;, and DeepSeek's dated price tables, &lt;a href="https://tokely.me/blog-media/chinese-ai-model-api-prices-2026/deepseek-api-price-history-2026.csv" rel="noopener noreferrer"&gt;deepseek-api-price-history-2026.csv&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Cite as: Tokely (2026). Are Chinese AI Models Getting More Expensive? API Prices by Generation (2026). &lt;a href="https://tokely.me/blog/chinese-ai-model-api-prices-2026" rel="noopener noreferrer"&gt;https://tokely.me/blog/chinese-ai-model-api-prices-2026&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/chinese-ai-model-api-prices-2026" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>api</category>
      <category>deepseek</category>
    </item>
    <item>
      <title>Web Search API Pricing for AI Agents: 8 Providers Compared (2026)</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Tue, 27 Oct 2026 08:40:15 +0000</pubDate>
      <link>https://dev.to/tokely/web-search-api-pricing-for-ai-agents-8-providers-compared-2026-eh8</link>
      <guid>https://dev.to/tokely/web-search-api-pricing-for-ai-agents-8-providers-compared-2026-eh8</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Research scope:&lt;/strong&gt; This study compares official list prices and API docs of web search APIs and model-native search tools as of October 27, 2026. It is a price snapshot: model tokens, result quality and latency were not measured. DeepSeek per-request billing starts November 1, 2026.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Web search API list prices span from $0.75 to $35 per 1,000 searches across 13 pricing tiers from eight providers. This creates a 47x spread between the lowest and highest cost options. Model-native tools carry the grounding premium, listing at 2x to 2.8x the median standalone search API.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did we measure?
&lt;/h2&gt;

&lt;p&gt;This comparison tracks 13 price tiers across eight providers, dividing them into seven standalone search API tiers and six search tools integrated directly into model APIs. The standalone options cover DeepSeek, Perplexity, Exa, Brave, and Tavily. The model-native group includes search tools inside OpenAI, Anthropic, and Google Gemini APIs.&lt;/p&gt;

&lt;p&gt;For each tier, we recorded the list price per 1,000 search requests, the maximum results returned per request, whether page content or a dedicated page-fetch endpoint is available, the price of that fetch feature, and any free monthly tier allowance. Every figure comes directly from each provider's official pricing documentation, verified on October 27, 2026. All listed prices exclude model token charges. The complete dataset is available as a CSV file below.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 1: A 47x spread between the cheapest and most expensive search
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsz9fq5j816672h3iaey2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsz9fq5j816672h3iaey2.png" alt="Bar chart of list prices per 1,000 searches for 13 tiers from 8 providers, from DeepSeek at $0.75 to Gemini 2.5 grounding at $35." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;List price per 1,000 search requests for 13 tiers from 8 providers. Black: standalone search APIs; grey: search tools inside model APIs. Model tokens excluded. Verified October 27, 2026.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;List prices per 1,000 search requests begin at $0.75 and reach $35. DeepSeek Search lists at $0.75, Perplexity Search fast lists at $1, Exa lite or instant lists at $4, Brave Search lists at $5, and Perplexity Search standard lists at $5. Moving up the range, Exa auto or fast lists at $7, Tavily basic lists at $8 based on one credit at $0.008, the OpenAI web search tool lists at $10, and the Anthropic web search tool lists at $10.&lt;/p&gt;

&lt;p&gt;At the high end, Google grounding for Gemini 3 and newer lists at $14, Tavily advanced lists at $16 for two credits, the OpenAI web search preview tool for non-reasoning models lists at $25, and Google grounding for Gemini 2.5 lists at $35 per 1,000 grounded prompts. Dividing $35 by $0.75 yields a 46.7 ratio, establishing an approximate 47x spread between the extremes. DeepSeek bills only for successful requests. Its per-request billing begins at 00:00 Beijing time on November 1, 2026, with calls routed through DeepSeek Harness, Claude Code, or Codex remaining free until that timestamp.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 2: The grounding premium
&lt;/h2&gt;

&lt;p&gt;Across the default tiers of the five standalone APIs, list prices are DeepSeek at $0.75, Brave at $5, Perplexity at $5, Exa auto at $7, and Tavily basic at $8. The median price across these default standalone tiers is $5 per 1,000 searches. Built-in model tools carry "the grounding premium": search tools built into model APIs (OpenAI, Anthropic, Google) list at 2 to 2.8x the median standalone search API, and 13 to 19x DeepSeek.&lt;/p&gt;

&lt;p&gt;OpenAI at $10 and Anthropic at $10 sit at exactly 2x the standalone median, while Google grounding for Gemini 3 at $14 sits at 2.8x. Compared to DeepSeek at $0.75, these native model tools are 13.3x and 18.7x more expensive per 1,000 requests. Beyond request fees, OpenAI bills search content tokens at regular model token rates, with an exception for the preview tool on non-reasoning models where content tokens are free. Anthropic counts search results as input tokens, both in the turn that ran the search and in later turns of the conversation.&lt;/p&gt;

&lt;p&gt;Model-native tools remove the need for a separate search API integration. In Anthropic's implementation, citations are always enabled, and the cited text, title, and URL fields do not count toward token usage. These tools allow the model to trigger queries autonomously during generation. Anthropic bills one use per search regardless of the number of returned results, and searches that encounter errors are not billed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 3: Reading pages, not just searching, changes the ranking
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flsknjmdg2u0ixwk794xk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flsknjmdg2u0ixwk794xk.png" alt="Bar chart of fees for 1,000 lookups of one search plus three page reads: DeepSeek $3, Perplexity $5, Exa lite $7, Exa auto $10, Anthropic $10, Tavily $12.80." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Tool fees for 1,000 lookups of one search plus three page reads. Model tokens for the page text are extra in every option.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Evaluating full agent workflows requires looking beyond query pricing. Defining a standard agent lookup as one search plus reading three target result pages reveals a different cost hierarchy. At 1,000 lookups, counting only tool and fetch fees, DeepSeek Search costs $3.00, calculated as $0.75 for search plus three Fetch requests at $0.75 each. Perplexity Search costs $5.00 flat because search results already include extracted page text bounded by max_tokens_per_page.&lt;/p&gt;

&lt;p&gt;Exa lite reaches $7.00 per 1,000 lookups, consisting of $4 for search plus three text pages at $1 per 1,000 pages. Exa auto totals $10.00, combining its $7 search price with $3 for three text page fetches. Anthropic web search also totals $10.00, pairing its $10 search fee with web fetch at no extra tool charge. Fetched page text is billed as model input tokens, which Anthropic docs estimate at roughly 2,500 tokens for an average 10 kB web page.&lt;/p&gt;

&lt;p&gt;Tavily basic reaches $12.80 per 1,000 lookups, combining its $8 search fee with Extract billed at one credit per five URLs, which equals $1.60 per 1,000 pages. Brave Search is omitted from this comparison because it returns snippets, with up to five extra snippets per result, and lists no page-fetch product on its pricing page. Across every provider, model tokens required to ingest fetched page text are billed separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 4: Per result, DeepSeek is 17x cheaper than the next API
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe2k0kkxenthok8qyyj7g.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe2k0kkxenthok8qyyj7g.png" alt="Bar chart of price per 1,000 returned results: DeepSeek $0.015 with 50 results per request, Perplexity fast $0.05, Brave and Perplexity $0.25, Exa lite and Tavily basic $0.40, Exa auto $0.70, Tavily advanced $0.80." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;List price per request divided by the most results one request returns within that price.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Comparing the list price against the maximum results delivered in a single request changes provider unit economics. DeepSeek costs $0.015 per 1,000 returned results based on its cap of 50 results per query. Perplexity fast costs $0.05 per 1,000 results with a 20-result cap. Brave Search costs $0.25 per 1,000 results with 20 results, matching Perplexity standard at $0.25 per 1,000 results for 20 results.&lt;/p&gt;

&lt;p&gt;Exa lite lists at $0.40 per 1,000 results, covering 10 included results, with additional results priced at $1 per 1,000. Tavily basic costs $0.40 per 1,000 results across 20 results. Exa auto costs $0.70 per 1,000 results with 10 results included, while Tavily advanced lists at $0.80 per 1,000 results across 20 results. At $0.015, DeepSeek is 16.7x cheaper per result than Brave or Perplexity standard at $0.25, and 3.3x cheaper than Perplexity fast at $0.05.&lt;/p&gt;

&lt;p&gt;Returned payloads also vary in structure. DeepSeek includes a rerank score from 0 to 3, an authority tier from 0 to 4, and an extracted summary between 600 and 800 characters targeted at model consumption. For Perplexity, a single billed search request can accept up to five queries at once while counting as one unit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding 5: Free tiers cover prototypes, not production
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fham8hjvht79lw4bfzp60.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fham8hjvht79lw4bfzp60.png" alt="Bar chart of free monthly searches: Gemini 3 grounding 5,000, Exa 2,500 Lite searches, Brave 1,000, Tavily 1,000 basic searches." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Free monthly allowance in default-tier searches, as listed on each pricing page.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Free monthly allowances differ widely across providers. Google grounding provides 5,000 free search requests per month shared across Gemini 3 and newer model tiers. Exa offers $10 in monthly platform credits, translating to up to 2,500 Lite searches. Brave provides $5 in monthly credits, which covers 1,000 searches at its $5 per 1,000 rate. Tavily includes 1,000 API credits each month, providing 1,000 basic search calls.&lt;/p&gt;

&lt;p&gt;An agent architecture executing 3,000 lookups per month, or about 100 per day, exceeds the free allocations of Exa, Brave, and Tavily. Only Google's Gemini 3 grounding allowance covers this monthly query volume without payment. We found no monthly free search allowance on the DeepSeek, OpenAI, and Anthropic pages we checked.&lt;/p&gt;

&lt;p&gt;Rate limit ceilings also introduce practical boundaries between APIs. Brave lists 50 queries per second for its Search plan. DeepSeek assigns accounts a cap of 100 queries per second for its Search API and 25 queries per second for its Fetch endpoint.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should teams do with this?
&lt;/h2&gt;

&lt;p&gt;For high-volume agents that execute multiple web searches per user task, standalone search APIs cost less per search. At $0.75 to $8 per 1,000 queries, these tools run at a fraction of the $10 to $14 per 1,000 fees charged by native model tools. A standalone API also lets the developer filter, rank, and truncate raw web data before injecting it into the prompt context.&lt;/p&gt;

&lt;p&gt;For low-volume applications or rapid prototyping, native model tools remove infrastructure complexity. Paying the grounding premium adds $2 to $9 per 1,000 queries over a $5 standalone baseline and avoids a separate search dependency. The model manages its own search invocations without intermediate orchestration code.&lt;/p&gt;

&lt;p&gt;Engineering teams must calculate full page reads and input tokens when estimating production expenses. A multi-step lookup that reads three full web pages generates $3 to $12.80 in tool charges alone per 1,000 operations before any token billing occurs. Tokely gives one API key for OpenAI, Anthropic, Google, DeepSeek and other models, so the model side of an agent can be priced and switched in one place: &lt;a href="https://tokely.me/pricing" rel="noopener noreferrer"&gt;Tokely pricing&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Methodology and limitations
&lt;/h2&gt;

&lt;p&gt;This research reflects official list prices and API documentation verified on October 27, 2026, with every data point linked to a source URL in the companion dataset. Default tiers represent the pricing applied when a request omits optional parameters, whereas Perplexity fast and Exa lite require explicit opt-in configuration. DeepSeek pricing applies to production billing starting November 1, 2026.&lt;/p&gt;

&lt;p&gt;This analysis excludes enterprise contracts, private volume discounts, Tavily's $30 monthly Project plan (4,000 credits at $7.50 per 1,000 basic searches), Exa Answer ($5 per 1,000 requests), specialized research agents, answer endpoints, model token charges, and taxes. The lookup model assumes one search plus three page fetches per task. Tavily Extract bills per five successful URLs, meaning a three-URL batch may incur rounding effects. We did not benchmark search latency, index coverage, or result quality.&lt;/p&gt;

&lt;h2&gt;
  
  
  Data and citation
&lt;/h2&gt;

&lt;p&gt;The complete dataset containing 13 provider tiers, prices per 1,000 requests, maximum result limits, fetch pricing, free tiers, and direct documentation links verified on October 27, 2026, is available for download: &lt;a href="https://tokely.me/blog-media/web-search-api-pricing-2026/web-search-api-prices-2026.csv" rel="noopener noreferrer"&gt;web-search-api-prices-2026.csv&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Cite as: Tokely (2026). Web Search API Pricing for AI Agents: 8 Providers Compared (2026). &lt;a href="https://tokely.me/blog/web-search-api-pricing-2026" rel="noopener noreferrer"&gt;https://tokely.me/blog/web-search-api-pricing-2026&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/web-search-api-pricing-2026" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>api</category>
      <category>webdev</category>
    </item>
    <item>
      <title>DeepSeek Open-Sourced the Engine Behind Its API. Is Self-Hosting V4.1 Flash Cheaper Than Paying per Token?</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Sun, 25 Oct 2026 18:15:57 +0000</pubDate>
      <link>https://dev.to/tokely/deepseek-open-sourced-the-engine-behind-its-api-is-self-hosting-v41-flash-cheaper-than-paying-per-3ki7</link>
      <guid>https://dev.to/tokely/deepseek-open-sourced-the-engine-behind-its-api-is-self-hosting-v41-flash-cheaper-than-paying-per-3ki7</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Renting a dedicated cluster to self-host DeepSeek V4.1 Flash costs more than the public API for almost every team. You cross the 76% line, where hardware rental beats DeepSeek's off-peak API price of $0.60 per 1M output tokens, only if you maintain more than 76% sustained GPU utilization day and night. Below that threshold, or with monthly spend under $880,000, paying per token is cheaper.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did DeepSeek open-source on October 20?
&lt;/h2&gt;

&lt;p&gt;DeepSeek published DeepInfer on October 20, 2026, under the Apache 2.0 license. DeepSeek describes the software as the high-performance inference framework that powers DeepSeek's large-scale production services. By October 25, the GitHub repository reached about 22,300 stars, and the Hacker News discussion passed 2,300 points.&lt;/p&gt;

&lt;p&gt;The framework supports one model: DeepSeek-V4.1-Flash. Its default checkpoint is DeepSeek-V4.1-Flash-1017, released on October 17, 2026, with 763B parameters, a 1M-token context window, and MIT-licensed weights. The official API serves this checkpoint under the model ID deepseek-flash.&lt;/p&gt;

&lt;p&gt;DeepInfer was originally built mainly on vLLM, incorporating ideas from SGLang and TensorRT-LLM. DeepSeek also released deepseek-recipe, which converts Chat Completions, Responses, and Messages API requests into model tokens matching the behavior of the official DeepSeek API.&lt;/p&gt;

&lt;p&gt;The engine includes specialized kernels such as FlashMLA, DeepGEMM, and DeepEP. It provides attention data parallelism alongside MoE expert parallelism, expert load balancing, speculative decoding with draft tokens, confidence-scheduled verification, and asynchronous scheduling. It also supports structured outputs using regex, JSON schema, or EBNF grammars. Batch-invariant inference and deterministic sampling work on NVIDIA hardware only.&lt;/p&gt;

&lt;h2&gt;
  
  
  What hardware does DeepInfer need?
&lt;/h2&gt;

&lt;p&gt;DeepInfer requires NVIDIA SM100 architecture GPUs or Huawei Ascend 950 NPUs. NVIDIA compute capability 10.0 corresponds to B200 and GB200 accelerators. The host environment requires Linux, GCC 13 or newer, Python 3.12, and CUDA 13 on NVIDIA or CANN 9.2 on Ascend.&lt;/p&gt;

&lt;p&gt;Inference splits prefill and decode across separate hardware configurations. DeepSeek runs prefill on standard 8-GPU servers, while decode requires 64 to 128 GPU supernodes. The published decode benchmark ran across 64 GPUs within a single scale-up domain, which in NVIDIA's lineup means a rack-scale system such as the GB200 NVL72, which links 72 Blackwell GPUs in one NVLink domain.&lt;/p&gt;

&lt;p&gt;DeepSeek states that one prefill node and one decode node form a deployable setup. However, DeepSeek recommends running decode at an expert parallelism of 64 or higher with a 1:1 prefill to decode GPU ratio. That makes 64 prefill GPUs plus 64 decode GPUs the smallest efficient deployment unit.&lt;/p&gt;

&lt;p&gt;DeepSeek's production setup also leans on a large KV cache store. DeepSeek provisions 14.4 TB of logical KV cache storage per GPU on roughly 100 PiB of SSDs, retaining cached prefixes for 3 days on agent traffic and 7 days on chatbot traffic. DeepSeek specifies storage servers containing 20 SSDs of 30.73 TB each. Without this storage layer, the system recomputes repeated prompt prefixes instead of loading them from cache.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is not in the release?
&lt;/h2&gt;

&lt;p&gt;DeepInfer covers offline inference, but it does not supply a complete production service. DeepSeek lists three missing architectural elements needed for full production serving.&lt;/p&gt;

&lt;p&gt;First, the release omits the distributed KV cache management system. Second, while most of the engine side is implemented, it lacks the full disaggregation pipeline across vision encoders, prefill nodes, and decode nodes. Third, it omits production load balancing across data-parallel replicas.&lt;/p&gt;

&lt;p&gt;DeepSeek states that its KV cache management and load balancing code remains tied to internal cluster infrastructure and is not fully open. Engineering teams that want to replicate the official API service must build routing and caching layers independently.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much does the smallest cluster cost to rent?
&lt;/h2&gt;

&lt;p&gt;The smallest efficient deployment unit of 128 Blackwell GPUs costs $1,222.40 per hour on CoreWeave on-demand pricing. That equals $29,337.60 per day and $880,128 across a 30-day month.&lt;/p&gt;

&lt;p&gt;This setup pairs 64 B200 GPUs across 8 HGX B200 instances for prefill at $8.60 per GPU-hour with 64 GB200 NVL72 GPUs for decode at $10.50 per GPU-hour. HGX B200 instances cost $68.80 per hour for 8 GPUs, totaling $550.40 per hour. GB200 NVL72 instances cost $42.00 per hour for 4 GPUs, totaling $672.00 per hour.&lt;/p&gt;

&lt;p&gt;Renting an entire 72-GPU NVL72 rack rather than a 64-GPU slice raises the cluster price to $1,306.40 per hour, or $940,608 per month. For comparison, Lambda lists HGX B200 clusters between $8.87 and $9.86 per GPU-hour under commitments ranging from 2 weeks to 1 year.&lt;/p&gt;

&lt;p&gt;The absolute minimum deployable unit of 1 prefill node and 1 decode node with 16 B200 GPUs costs $137.60 per hour, or $99,072 per month. None of these figures include KV cache storage servers, inter-rack networking, data egress, or engineering staff.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does self-hosting beat the API price?
&lt;/h2&gt;

&lt;p&gt;A 128-GPU cluster running DeepInfer delivers about 740,700 output tokens per second under DeepSeek's documented production settings. That figure multiplies 14,466 tokens per second per GPU across 64 decode GPUs, discounted to the 80 percent of the offline benchmark that DeepSeek says its load balancing reaches. Running continuously for 24 hours yields roughly 64 billion output tokens per day.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6no4dlrqa5m2sw95gk80.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6no4dlrqa5m2sw95gk80.png" alt="Line chart: self-hosted cost per 1M output tokens falls from $2.29 at 20% utilization to $0.46 at 100%. It drops below the DeepSeek off-peak API price of $0.60 at 76% utilization, below the Tokely flat price of $0.80 at 57% and below the DeepSeek peak price of $1.20 at 38%." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Cost per 1M output tokens of a rented 128-GPU cluster (64 B200 + 64 GB200, CoreWeave on-demand) at DeepSeek's benchmark throughput, against per-token prices checked October 25, 2026. The whole cluster cost is charged to output tokens.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Dividing the cluster lease across output volume gives a unit cost of $0.46 per 1M output tokens at 100 percent utilization. At 50 percent utilization, the cost climbs to $0.92 per 1M output tokens. At 20 percent utilization, the cost reaches $2.29 per 1M output tokens.&lt;/p&gt;

&lt;p&gt;Comparing these costs to DeepSeek's off-peak output rate of $0.60 per 1M output tokens establishes the 76% line. A rented 128-GPU cluster must maintain at least 76 percent sustained utilization around the clock to undercut the off-peak API. Against an output price of $0.80 per 1M output tokens, break-even sits at 57 percent utilization, dropping to 38 percent against the peak API rate of $1.20 per 1M output tokens.&lt;/p&gt;

&lt;p&gt;This comparison assigns the entire cluster lease to output generation and assumes inputs are free, which favors the API. Factoring in a workload with 4M input tokens per 1M output tokens, with half of the input tokens served from cache, raises the off-peak API bill to $0.906 per 1M output tokens. Under this adjusted input mix, the break-even utilization threshold drops to about 51 percent.&lt;/p&gt;

&lt;p&gt;The absolute budget sets a clear ceiling on whether self-hosting makes sense. A 128-GPU cluster costs $29,337.60 every 24 hours whether processing requests or idling, which buys 48.9 billion output tokens on the off-peak API. If your monthly DeepSeek V4.1 Flash API bill sits below $880,000, paying per token costs less than renting this cluster regardless of utilization.&lt;/p&gt;

&lt;p&gt;Downsizing to the 16-GPU setup of 2 nodes does not lower the break-even threshold. DeepSeek's benchmark data shows 8-GPU expert parallelism produces about 12,600 tokens per second per GPU at 64 concurrent requests. Factoring in 80 percent load balancing yields 7 billion output tokens per day, translating to $0.47 per 1M output tokens at 100 percent load and a 79 percent break-even threshold against off-peak API pricing.&lt;/p&gt;
&lt;h2&gt;
  
  
  How does DeepSeek make money at $0.60 per million tokens?
&lt;/h2&gt;

&lt;p&gt;In its deployment documentation, DeepSeek reports that a single production cluster serves 155 trillion tokens per day, generating US$38 of revenue per GPU-hour at off-peak valley pricing. This figure is DeepSeek's own unaudited claim. DeepSeek does not disclose how many total GPUs make up that cluster, and US$38 reflects gross revenue rather than profit.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxr93mswpykq6qmb1upju.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxr93mswpykq6qmb1upju.png" alt="Bar chart: DeepSeek reports revenue of $38 per GPU-hour at off-peak prices; CoreWeave rents a GB200 NVL72 GPU for $10.50 and an HGX B200 GPU for $8.60 per hour on demand." width="800" height="463"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;DeepSeek's reported revenue per GPU-hour at off-peak prices (first-party, unaudited) against CoreWeave on-demand rental prices, checked October 25, 2026.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;CoreWeave lists comparable B200 and GB200 hardware between $8.60 and $10.50 per GPU-hour on demand. That spread between raw hardware rental costs and DeepSeek's $38 per GPU-hour revenue explains how DeepSeek charges $0.60 per 1M output tokens. DeepSeek pools demand from its whole user base and keeps its accelerators busy at a scale a single team rarely reaches.&lt;/p&gt;

&lt;p&gt;DeepSeek's benchmark results show how concurrency drives that revenue density. At 256 requests per GPU, a 64-GPU decode cluster achieves about 26,000 output tokens per second per GPU, with individual streams receiving 100 tokens per second. Dropping concurrency to 8 requests per GPU raises individual user speeds to 325 tokens per second but reduces cluster efficiency to 2,600 tokens per second per GPU. The benchmark fixes draft-token acceptance at 75 percent.&lt;/p&gt;

&lt;p&gt;Prefill clusters show similar scaling under a 131,072 context length. Running prefill across 4 GPUs yields between 60,000 and 89,000 uncached input tokens per second per GPU depending on batch size. Without enough traffic to keep batches full, a private cluster runs small batches, and each GPU produces fewer tokens per dollar.&lt;/p&gt;
&lt;h2&gt;
  
  
  Who should self-host DeepSeek V4.1 Flash?
&lt;/h2&gt;

&lt;p&gt;Self-hosting DeepSeek V4.1 Flash makes sense for four specific groups of developers. First, teams that must keep prompts and outputs inside their own private infrastructure for compliance reasons require dedicated hardware. For these organizations, data containment justifies the engineering overhead.&lt;/p&gt;

&lt;p&gt;Second, engineering teams that require bit-identical outputs need to deploy DeepInfer directly. DeepInfer delivers batch-invariant inference and deterministic sampling on NVIDIA SM100 systems, ensuring that variations in batch size or concurrent load do not alter output tokens.&lt;/p&gt;

&lt;p&gt;Third, companies with steady traffic large enough to keep at least 128 Blackwell GPUs busy around the clock can achieve lower costs. If your application sends continuous traffic that stays above the 76% line every hour of the week, private hosting beats per-token rates.&lt;/p&gt;

&lt;p&gt;Fourth, commercial inference providers can build competitive hosting businesses. Combining MIT-licensed weights with an Apache 2.0 inference engine permits any host to sell V4.1 Flash endpoints. For everyone else, per-token APIs remain cheaper, especially since DeepSeek's off-peak window covers about 79 percent of the week.&lt;/p&gt;
&lt;h2&gt;
  
  
  How do you use DeepSeek V4.1 Flash without a cluster?
&lt;/h2&gt;

&lt;p&gt;Developers who want to avoid provisioning 128 Blackwell GPUs can access the model directly through Tokely. Tokely lists &lt;a href="https://tokely.me/models/deepseek-v4.1-flash" rel="noopener noreferrer"&gt;DeepSeek V4.1 Flash on Tokely&lt;/a&gt; at $0.20 input, $0.004 cached input, and $0.80 output per 1M tokens.&lt;/p&gt;

&lt;p&gt;These prices remain the same at any hour, removing the need to schedule jobs around DeepSeek's peak windows. Tokely's $0.80 output price beats DeepSeek's peak rate of $1.20 per 1M output tokens while providing consistent per-token billing without cluster management. Tokely prices can change, and the &lt;a href="https://tokely.me/models" rel="noopener noreferrer"&gt;Tokely models&lt;/a&gt; catalog shows current rates.&lt;/p&gt;

&lt;p&gt;The platform uses an OpenAI-compatible interface. A single API key and shared balance route requests to Claude, GPT, Gemini, Kimi, and over 130 other models, letting teams change models by editing the model parameter.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;from&lt;/span&gt; &lt;span class="n"&gt;openai&lt;/span&gt; &lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;OpenAI&lt;/span&gt;

&lt;span class="n"&gt;client&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;OpenAI&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;base_url&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;https://api.tokely.me/v1&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;YOUR_TOKELY_API_KEY&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;reply&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;chat&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;completions&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;model&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;deepseek-v4.1-flash&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;messages&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;[{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;role&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;user&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;content&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Summarize this incident report in five lines.&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;}],&lt;/span&gt;
    &lt;span class="n"&gt;max_tokens&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;2048&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;reply&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;choices&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;].&lt;/span&gt;&lt;span class="n"&gt;message&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;content&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Methodology and limitations
&lt;/h2&gt;

&lt;p&gt;This analysis prices hardware at CoreWeave's on-demand list prices checked on October 25, 2026, with Lambda's term prices shown for comparison. Reserved capacity costs less per hour, which would lower the break-even utilization.&lt;/p&gt;

&lt;p&gt;Throughput figures come from DeepSeek's published offline benchmarks running on a 131,072-token context length with speculative decoding draft-token acceptance fixed at 75 percent. In live production environments with varying query patterns, draft acceptance and output throughput will fluctuate. The figure of 12,600 tokens per second per GPU for the 16-GPU setup was read directly from DeepSeek's benchmark chart.&lt;/p&gt;

&lt;p&gt;The cost models exclude KV cache storage, inter-rack networking, cloud data egress, and engineering personnel. Real production workloads experience uneven demand curves, meaning continuous 24/7 utilization serves as a theoretical upper bound rather than everyday reality.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;p&gt;Data in this analysis comes from &lt;a href="https://github.com/deepseek-ai/DeepInfer" rel="noopener noreferrer"&gt;DeepInfer on GitHub&lt;/a&gt;, the &lt;a href="https://github.com/deepseek-ai/DeepInfer/blob/main/doc/inference_deployment_qa.md" rel="noopener noreferrer"&gt;DeepSeek V4.1 Flash inference deployment Q&amp;amp;A&lt;/a&gt;, model weights on &lt;a href="https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017" rel="noopener noreferrer"&gt;DeepSeek-V4.1-Flash-1017 on Hugging Face&lt;/a&gt;, the &lt;a href="https://api-docs.deepseek.com/quick_start/pricing/" rel="noopener noreferrer"&gt;DeepSeek API pricing&lt;/a&gt; schedule, &lt;a href="https://www.coreweave.com/pricing" rel="noopener noreferrer"&gt;CoreWeave GPU pricing&lt;/a&gt;, and &lt;a href="https://lambda.ai/pricing" rel="noopener noreferrer"&gt;Lambda GPU pricing&lt;/a&gt;. Hardware details come from &lt;a href="https://www.nvidia.com/en-us/data-center/gb200-nvl72/" rel="noopener noreferrer"&gt;NVIDIA GB200 NVL72&lt;/a&gt; specifications and the &lt;a href="https://developer.nvidia.com/cuda-gpus" rel="noopener noreferrer"&gt;NVIDIA CUDA GPU compute capability&lt;/a&gt; table. Reception: the &lt;a href="https://news.ycombinator.com/item?id=50163277" rel="noopener noreferrer"&gt;Hacker News discussion&lt;/a&gt;. For the U.S. policy side, see our earlier post &lt;a href="https://tokely.me/blog/deepseek-federal-ban-alternatives" rel="noopener noreferrer"&gt;DeepSeek Banned From U.S. Federal Agencies&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/deepseek-deepinfer-self-hosting-cost" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>opensource</category>
      <category>devops</category>
    </item>
    <item>
      <title>Agent Skills Moves to the Agentic AI Foundation: What Developers Need to Know</title>
      <dc:creator>Tokely — AI API Platform</dc:creator>
      <pubDate>Sat, 24 Oct 2026 05:02:22 +0000</pubDate>
      <link>https://dev.to/tokely/agent-skills-moves-to-the-agentic-ai-foundation-what-developers-need-to-know-1g90</link>
      <guid>https://dev.to/tokely/agent-skills-moves-to-the-agentic-ai-foundation-what-developers-need-to-know-1g90</guid>
      <description>&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Anthropic donated the Agent Skills standard to the Agentic AI Foundation on October 22, 2026. This transfer places the skill specification under neutral Linux Foundation governance alongside the Model Context Protocol. Developers can build skills using simple local directories, Markdown instructions, and executable scripts, then run them across dozens of supported agent clients and model backends without encountering platform lock-in.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did Anthropic donate on October 22?
&lt;/h2&gt;

&lt;p&gt;On October 22, 2026, Anthropic transferred the Agent Skills standard and all related assets to the Agentic AI Foundation. The donation includes the core specification, the Agent Skills name and logo, the official GitHub organization, and the agentskills.io domain. Anthropic stated that it is committed to keeping Agent Skills open, community-driven, and vendor-neutral.&lt;/p&gt;

&lt;p&gt;The Agentic AI Foundation operates as a project under the Linux Foundation to host vendor-neutral agent standards. Anthropic, Block, and OpenAI co-founded the foundation in 2025 to create a shared home for open agent infrastructure. The foundation already hosts the Model Context Protocol, which Anthropic donated in an earlier governance transfer.&lt;/p&gt;

&lt;p&gt;Anthropic first launched Agent Skills inside its Claude products in October 2025. Two months later, in December 2025, Anthropic published the underlying format as an open standard for the developer community. Donating the assets to the Agentic AI Foundation completes the transition from a single-vendor feature to a neutral industry specification.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who maintains Agent Skills now?
&lt;/h2&gt;

&lt;p&gt;Two Lead Maintainers, David Soria Parra and Mahesh Murag, now guide the Agent Skills project. Individual software engineers from Anthropic, Google, OpenAI, and other technology companies maintain the specification on their own behalf rather than through corporate representation.&lt;/p&gt;

&lt;p&gt;Development teams do not need to join the Agentic AI Foundation to use the standard or contribute code to the repository.&lt;/p&gt;

&lt;p&gt;Anyone who wants to suggest changes to the specification can send feedback through the project's Discord server.&lt;/p&gt;

&lt;h2&gt;
  
  
  How widely is the standard used?
&lt;/h2&gt;

&lt;p&gt;More than 70 agent platforms have integrated the Agent Skills specification across their production tools. That adoption footprint includes major coding agents and developer environments such as ChatGPT, Cursor, GitHub Copilot, and VS Code.&lt;/p&gt;

&lt;p&gt;According to Anthropic, developers have published 1 million skills and end users have installed nearly 280 million skills across those integrated platforms. These are Anthropic's own figures and are not independently audited.&lt;/p&gt;

&lt;p&gt;For skill authors, that means one package format across competing platforms. Developers who author a skill can deploy that package directly to multiple editors and command-line agents without rewriting instructions for each client.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is inside a skill?
&lt;/h2&gt;

&lt;p&gt;A skill is a directory containing at minimum a SKILL.md file with YAML frontmatter followed by standard Markdown instructions. The directory can also house optional subdirectories by convention, including scripts for executable code, references for documentation loaded on demand, and assets for templates, images, or data files.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;api-cost-check/
├── SKILL.md
├── scripts/
│   └── estimate.py
└── references/
    └── prices.md
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;File references inside SKILL.md should be relative paths from the skill root, kept one level deep. The specification advises against long chains of nested references.&lt;/p&gt;

&lt;p&gt;The YAML frontmatter defines two required fields: name and description. The name field takes a string between 1 and 64 characters containing only lowercase letters, digits, and single hyphens. It must match the parent directory name exactly, with no leading hyphens, trailing hyphens, or double hyphens.&lt;/p&gt;

&lt;p&gt;The description field accepts 1 to 1,024 characters explaining what the skill accomplishes and when the agent should select it. Authors should write clear descriptions with relevant keywords, because the agent runtime inspects this text to decide which skill fits a given user prompt.&lt;/p&gt;

&lt;p&gt;Frontmatter also supports four optional fields. The license field names the distribution license, while compatibility accepts up to 500 characters outlining environment requirements. Authors can provide arbitrary string key-value pairs through the metadata map, or specify an experimental allowed-tools list containing space-separated pre-approved tools.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="nn"&gt;---&lt;/span&gt;
&lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;api-cost-check&lt;/span&gt;
&lt;span class="na"&gt;description&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Estimates&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;the&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;API&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;cost&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;of&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;a&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;prompt&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;or&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;batch&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;job&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;before&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;it&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;runs.&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;Use&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;when&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;the&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;user&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;asks&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;what&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;a&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;request,&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;batch&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;or&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;agent&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;run&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;will&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;cost&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;on&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;a&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;given&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;model."&lt;/span&gt;
&lt;span class="na"&gt;license&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Apache-2.0&lt;/span&gt;
&lt;span class="na"&gt;metadata&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;author&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;example-org&lt;/span&gt;
  &lt;span class="na"&gt;version&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s"&gt;1.0"&lt;/span&gt;
&lt;span class="nn"&gt;---&lt;/span&gt;

&lt;span class="gh"&gt;# API cost check&lt;/span&gt;
&lt;span class="p"&gt;
1.&lt;/span&gt; Count input tokens and estimate output tokens.
&lt;span class="p"&gt;2.&lt;/span&gt; Read per-1M-token prices from references/prices.md.
&lt;span class="p"&gt;3.&lt;/span&gt; Run scripts/estimate.py and report the cost per request and per 1,000 requests.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Developers can verify their directory structure and schema formatting before distributing a package. Running skills-ref validate ./my-skill through the skills-ref reference library checks that the frontmatter is valid and follows the naming rules.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does progressive disclosure keep context small?
&lt;/h2&gt;

&lt;p&gt;Roughly 100 tokens of metadata per skill enter the context window when an agent session initializes. The runtime loads only the name and description fields at startup, allowing an agent to index dozens of capabilities without consuming substantial context space.&lt;/p&gt;

&lt;p&gt;The agent defers reading the rest of the package until the user prompt triggers that specific skill. The full body of SKILL.md loads into the active prompt only upon activation, and the specification recommends keeping that body under 5,000 tokens and under 500 lines of text.&lt;/p&gt;

&lt;p&gt;Files located inside the scripts, references, and assets subdirectories remain unloaded until the activated instructions specifically call for them. This phased approach prevents large documentation files and scripts from bloating context during unrelated prompts.&lt;/p&gt;

&lt;p&gt;Fifty installed skills add about 5,000 tokens of metadata at session start. At an input price of $2 per 1M tokens before prompt caching, loading metadata for all 50 skills costs roughly $0.01 per session.&lt;/p&gt;

&lt;h2&gt;
  
  
  How are skills different from MCP?
&lt;/h2&gt;

&lt;p&gt;The Model Context Protocol connects an agent to external tools and live data stores through client-server connections. In contrast, an Agent Skill packages procedural instructions, executable scripts, and static reference files that an agent runtime reads directly from disk.&lt;/p&gt;

&lt;p&gt;MCP relies on active server processes that expose tool definitions, resources, and prompt templates over standard communication protocols. A skill functions as a static file bundle that informs the model how to complete a specific task using tools already available on the host.&lt;/p&gt;

&lt;p&gt;Both standards now operate under the Agentic AI Foundation as complementary building blocks. A skill can direct an agent on when and how to call an MCP server, while the MCP server handles the protocol communication with remote systems.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is on the roadmap, and why does security matter?
&lt;/h2&gt;

&lt;p&gt;The proposed starting roadmap for Agent Skills focuses on three areas: versioned releases, a formal specification proposal process, and security guidance for authors and users. A structured release cycle will help tool builders maintain compatibility as the format matures under foundation governance.&lt;/p&gt;

&lt;p&gt;Security guidance represents an immediate priority because a skill can include arbitrary code in its scripts directory. When a skill's instructions tell the agent to run those scripts, they run with whatever access the agent has on that machine.&lt;/p&gt;

&lt;p&gt;Installing a skill therefore means trusting the author who packaged it. Malicious or poorly tested scripts can modify local files, execute dangerous shell commands, or expose sensitive project data. Developers should always review the contents of the scripts directory before installing third-party skills into their environments.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you use skills with any model through one API key?
&lt;/h2&gt;

&lt;p&gt;Claude Code reads personal skills from ~/.claude/skills//SKILL.md and project-level skills from .claude/skills//SKILL.md inside the root of a repository.&lt;/p&gt;

&lt;p&gt;Skills are plain text files evaluated by the agent client rather than the upstream model provider. Because the client parses the frontmatter and passes the instructions to the model, the same skill files work whichever model the client calls, although results still depend on the model.&lt;/p&gt;

&lt;p&gt;Developers can run Claude Code through the Tokely API gateway by setting two environment variables. The skill directories stay exactly as they are.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;skills-ref validate ./api-cost-check
&lt;span class="nv"&gt;ANTHROPIC_BASE_URL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;https://api.tokely.me &lt;span class="nv"&gt;ANTHROPIC_AUTH_TOKEN&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s1"&gt;'&amp;lt;YOUR_TOKELY_API_KEY&amp;gt;'&lt;/span&gt; claude
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A single Tokely API key and unified balance grants access to Claude, GPT, Gemini, and Kimi models, including Kimi K3.1 Pro. The gateway exposes an Anthropic-compatible endpoint for Claude Code and an OpenAI-compatible endpoint for other agent clients, so a team can test the same skill on several models from one account. You can view all supported options on the &lt;a href="https://tokely.me/models" rel="noopener noreferrer"&gt;Tokely models&lt;/a&gt; page or read our guide on using &lt;a href="https://tokely.me/blog/claude-code-cheaper-api" rel="noopener noreferrer"&gt;Claude Code with a cheaper API&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;p&gt;Read the announcement details at &lt;a href="https://www.anthropic.com/news/donating-agent-skills-to-the-agentic-ai-foundation" rel="noopener noreferrer"&gt;Anthropic's announcement&lt;/a&gt; and explore technical definitions in the &lt;a href="https://agentskills.io/specification" rel="noopener noreferrer"&gt;Agent Skills specification&lt;/a&gt;. Further context appears in &lt;a href="https://simonwillison.net/2026/Oct/22/donating-agent-skills/" rel="noopener noreferrer"&gt;Simon Willison's note&lt;/a&gt; and our setup tutorial for &lt;a href="https://tokely.me/blog/claude-code-cheaper-api" rel="noopener noreferrer"&gt;Claude Code with a cheaper API&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://tokely.me/blog/agent-skills-agentic-ai-foundation" rel="noopener noreferrer"&gt;tokely.me&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>opensource</category>
      <category>claude</category>
    </item>
  </channel>
</rss>
