NEW Basalt + Qwen3.8 Flash-Next Changes EVERYTHING

Show Notes

Watch the video: https://www.youtube.com/watch?v=hPh6Td3IvgA

Basalt runtime + Qwen3.8 Flash-Next just posted 665 tokens per second on structured output, 354 on prose - free weights, open runtime, single GPU. Your OpenAI bill does not know yet.
Playbooks + my answers, free - Church of SEO Jesus: https://www.skool.com/church-of-seo-jesus

What you get in this video:
- Why 80% of your current API spend (classification, extraction, scoring, tagging) is the grunt tier that just got repriced
- The exact split: Basalt + Qwen3.8 Flash-Next for schemas, Claude and GPT for reasoning and prose
- The P&L math: a $1,000 OpenAI invoice becomes a ~$100 GPU rental on the grunt tier (estimated, swap your real numbers)
- The one sentence you give your developer on Monday to return a working bake-off by Friday
- The match-rate kill switch: 95% migrate, 85% hybrid, 70% stay put

Sources:
- Reddit r/LocalLLaMA thread (the only cited source): https://www.reddit.com/r/LocalLLaMA/comments/1x223ai/basalt_flashnext_at_665_toks_structured_354_prose/
- OpenAI pricing (for the vendor side of the math): https://platform.openai.com/docs/pricing
- Anthropic pricing: https://www.anthropic.com/pricing

Flag: hardware, batch size and quantization are not stated in the headline Reddit post. Treat the exact 665 figure as estimated until an independent reproduction lands. The thesis survives if the number halves.

Chapters:
00:00 Basalt + Qwen3.8 Flash-Next posts 665 tok/s on Reddit
00:27 What Basalt runtime and Qwen3.8 Flash-Next actually are
01:30 Structured output is the boring 80% of your API bill
02:10 The P&L math: $1,000 OpenAI bill becomes a $100 GPU box
02:40 Soft subscribe + pinned comment pointer
03:08 Verify the 665 and 354 numbers yourself on Reddit
03:25 What is estimated vs measured in this video
03:45 The workloads that migrate: enrichment, parsing, tagging, review mining
04:02 GPT-4o-mini vs hosted Qwen3.8 Flash-Next cost walk
04:44 Who gets undercut first: agencies, SaaS COGS, markup floors
05:08 What does NOT move: reasoning, long context, Claude-grade prose
05:28 The router rule: schema goes open, paragraph stays paid
05:48 Why prose at 354 tok/s is the warning sign
06:12 The Monday-to-Friday bake-off instruction
06:46 Match-rate kill switch: 95%, 85%, 70%
07:08 Hosting warning: pay a vendor's margin before you learn devops
07:34 Why first movers eat the pricing in their category
07:48 Church of SEO Jesus: the bake-off script and router code
08:12 Next: the free runtime that broke the quiet pricing agreement

Audio edition of the Stewart Vickers AI YouTube video of the same name. Full transcript on this episode page.

What is Stewart Vickers AI?

The audio edition of the Stewart Vickers AI YouTube channel. Each episode takes one AI release - a model, a tool, a price cut - and translates it into money for business owners: what got cheaper, who got undercut, and what to do about it this week. Operator credibility over theory, specific numbers over vibes. Every episode links the original video and the free Church of SEO Jesus community where the prompts and workflows live.

A reddit post went up last night, one sentence. 8 flash next, 665 tokens PR second, structured, 354 pros, 665 tokens PR second, on a free Modal, your API bill does not know yet, free weights, open runtime, single GPU. The competitor who moves first eats your pricing. If you are paying OpenAI or Anthropic for classification, extraction, scoring or tagging, the PR token math on 80% of your bill just changed. Here is what happened, what it means for your P&L, and the exact instruction you give your developer on Monday. Basalt is an open runtime.

A runtime is the engine that makes a Modal answer when you call it. Think of it as the printer driver that decides how fast your paper comes out. Vendor AP is ship their own closed one. Basalt is one you host yourself, and it just Post-it a throughput number nobody else in the open stack has matched this year. 8 flash next is the Modal, Alibaba's open weighty line, the small fast tier, free to download, no license fee, no PR call bill. Structured output means JSON, fields with names, values with types.

The boring 80% of what your business pays an API to do every single day. Pull a company name off an invoice, score a lead 1 to 10, tag a product, extract a phone number, label a review, classify a support ticket. Every one of those jobs is a tiny prompt and a tight schema. Tight schemas are what the 665 number was measured on. The Modal only has to pick the next legal token inside a fixed shape, so the maths runs faster than when to write a sentence from scratch. Here is the number that matters to the P&L.

If 80% of your current IPI spend is classification and extraction, and your developer can host this stack on a rented GPU for $100 a month, your variable cost on that 80% drops toward the electricity bill. A $1,000 monthly open AI invoice becomes a $100 GPU rental plus margin, not in 6 months, inside a quarter. If your API bill is one of the biggest line items on your P&L, hit subscribe. I cover every Qwen drop and every open waiter runtime that lands the same day it ships, so the next cost cut finds you instead of you finding it on an invoice 3 months late. The copy paste commands and config for this video sit in the pinned comment, auto Post-it. The church of S E O Jesus, my free school community, is where the playbook versions of these videos live, and where I answer when your bake off breaks.

Link below. Open the Reddit thread yourself right now at the URL in the description. Look at the title and the top comment thread. The 665 and 354 numbers are right there, and so is every objection the community already raised. The proof is on the page, not me telling you. One flag before we go further.

The thread fetched short when I researched this, so hardware, batch size and quantization level are not stated in the headline. Call those estimated until an independent reproduction lands. The thesis survives if the exact number halves. 330 tokens a second on a free Modal still eats a vendor API alive on volume. Lead enrichment, invoice passing, product tagging, review mining, bulk rewriting of your own catalogue. Each one is thousands of small identical prompts a day running on autopilot in the background of your product.

Each one is paid for at vendor rates right now. Walk a lead scoring job that burns 10 million tokens a month on GPG-4o-mini. At ReDetail that line costs you around $150 before egress fees. 8 flash next endpoint at 665 tokens a second is a GPU occupied for roughly 4 hours over the month. 4 hours of H100 time runs about $10. Same output, same JSON, 1 tenth the bill.

I am estimating the egress line and the GPU rate. Swap your real numbers in before you tell your accountant. The incumbent here is any founder paying vendor rates on volume classification. Agencies passing open AI costs through to clients at a markup of two or three times. SaaS teams whose cost of goods line is dominated by inference. All of them are standing on a floor that moved last night.

The customer paying the markup will find out and the agency that moves first wins the renegotiation. Here is what does not move onto Basalt. Reasoning that needs clawed or an o-series Modal, long context work over whole legal documents. A sales email that has to sound like a human wrote it. The next move in a complex workflow. Anything a frontier Modal earns its price on, keep paying for.

The split is grunt tier open, judgment tier paid. Not either or. Both in the same product, routed by prompt type. Your developer picks the router. Simple rule. If the output is a schema the Modal has to fill, send it open.

If the output is a paragraph a human will read, keep it on the paid API. Prose at 354 tokens a second is the warning sign. Fast is not the same as right. A wrong extraction at 665 tokens a second costs more in cleanup than a correct one at 60. Bake off before you migrate. The 665 number is a ceiling, not a guarantee, and I am calling it that until an independent reproduction hits.

Next, the exact sentence you give your developer on Monday that returns a working comparison by Friday. Export the last 30 days of API logs for your two highest volume prompt types. Classification first, extraction second. Hand your developer or your agency three things. The raw logs, the current monthly bill for those two jobs, and one question. 8 flash next endpoint?

Replay these prompts through it with the same expected JSON schema, and tell me by Friday what the match rate and cost delta look like. Match rate is the kill switch. If the open Modal gets the same answer 95% of the time, migrate the grunt tier and keep the and check back next quarter. If it gets 85%, keep the paid API on the records where confidence is low and ride the open stack on the rest. The decision is a spreadsheet, not an opinion. One warning on the hosting side.

If you do not have an engineer who has deployed a GPU workload before, do not learn on this. 8 flash next behind an API will exist by the time you watch this. Pay them a layer of margin to run the box, keep your bake-off focused on the cost PR million tokens line, not on DevOps. The win is still a tenfold cut on the grunt tier even after a vendor's margin. The founders who move first inside a category always eat the pricing. The ones who wait for a vendor to announce a cut discover their competitor already underbid them to the customer, and the customer never comes back.

The church of SEO Jesus is my free school community, and the link sits in the description. Inside, the bake-off script I just walked, the router rule written out as code, the match rate scoring sheet, and the exact prompt mixes my own clients use to split grunt tier from judgment tier. Members post their monthly API bills, I point at the three jobs to migrate first. Free, runtime that broke the frontier lab's quiet pricing agreement, and why the next invoice from OpenAI is going to read differently.