Metered billing on Stripe was quietly rebuilt: the usage-records API is removed, and meters are the only supported path. Here's the working end-to-end flow — meter, price, subscription, usage events, invoice — with real code.
A founder-grade walkthrough: enable pgvector on the Postgres you already run, embed your rows, add an HNSW index, and ship semantic search this afternoon — with the copy-paste SQL and code.
A from-scratch, code-heavy walkthrough: a typed output model, tools with @agent.tool, dependency injection, sync/async/streaming runs, and what V2's capabilities model actually changes in the code you write.
A founder-practical build guide: generate hundreds of unique, indexable pages from one Next.js template with generateStaticParams, per-page metadata, and ISR — and the one rule (data density per page) that decides whether Google indexes them or deletes them.
One thin interface between your app and any model provider turns the next price hike, outage, or migration into a one-line config change instead of a rewrite. Here's the whole pattern, in copy-paste TypeScript.
Kimi K2.7 Code landed in Copilot's model picker on July 1. Every other model there is a black box you rent. This is the first one whose weights are on Hugging Face — the first row with a way out.
Jujutsu (jj) keeps Git's storage and pushes to GitHub like nothing changed — but throws out the parts that make Git hard: the staging area, detached HEAD, and merge conflicts that block you. Here's what actually changes when you switch.
Now that AI images cost cents per thousand, the constraint isn't the model — it's the plumbing. Here's a copy-paste pipeline that caches by prompt hash, falls back across providers, and caps your spend before the invoice does.
You wouldn't ship a payments flow with zero tests. Most teams ship LLM features with exactly that. Here's the smallest real eval harness — deterministic assertions plus an LLM-as-judge — with copy-paste promptfoo and Python.
The reflex is to swap in a cheaper model and hope users don't notice. Skip that. The biggest savings never touch the model your customers see — they're in how you send the calls, not which model you send them to. Five moves, ordered by return, none of which lowers quality.
The model you pick today will be overpriced in a quarter. A founder's playbook for keeping your AI stack swappable — the abstraction to route through, the eval set that lets you switch safely, and the three-line code change that future-proofs you.
xAI's new coding model undercuts the field on the rate card. But for anyone running agent loops, the number that actually moves your bill is how many tokens it burns to finish the job.
The real choice isn't which login screen looks nicer — it's the billing unit. One charges per user, one charges per returning user, and one charges nothing. Here's how that decides for you.
You don't need to hire a marketer, a support rep, a designer, and a bookkeeper before you have revenue. Here are seven AI-native tools that let one founder run all of it — what each does, who it's for, how to start, and what it actually costs.
Model prices are falling, but a falling price only helps if your architecture can capture it. Five open-source tools — a router, a metering layer, a local meeting recorder, an agent multiplexer, and an autonomous pentester — that let a founder actually pocket the savings the price war is handing out.
The June 29 release flips vLLM's rebuilt execution core on by default and lands a Rust serving front-end. The throughput comes from deleting the CPU–GPU sync, not from a hotter matmul.
HNSW and DiskANN treat an index as a build artifact you periodically tear down and rebuild. SPFresh-class indexes — like Weaviate's HFresh — treat it as a living structure that rebalances as you write. The axis that decides which you need isn't recall. It's your write pattern.
max_num_batched_tokens looks like a throughput setting. It's really a fairness dial between the one user who pasted a novel and everyone else's token cadence.
The library named after TensorRT is deleting TensorRT. The June 30 release candidate is the last to support the compiled engine backend; the next version removes it. The lesson isn't about NVIDIA — it's about which tradeoff keeps winning.
DeepSeek shipped a 1.6-trillion-parameter model under MIT and let vLLM and SGLang publish the serving recipes the same day. The weights are free and portable. The throughput that makes them economical is neither.
Kubernetes already solved "declare a workload, let a mesh own the network." Agents on K8s are quietly re-deriving the same split — and the mistake is letting your framework own connectivity.
Once prefill and decode live on separate GPU pools, you have to decide how many of each. The number isn't a property of your model — it's a property of your traffic, and it drifts.
Text, dense, and sparse now live in a single Pinecone index. But a search request ranks by exactly one score, so 'true hybrid' fusion quietly moves back into your code.
The universal advice is 'front-load your static system prompt so it gets prefix-cached.' In a tool-using or RAG agent, one mid-context insertion throws that whole cache away. CacheBlend keeps it anyway.
Once you split prefill and decode onto separate GPUs, something has to ferry gigabytes of KV cache between them. NIXL and Mooncake are the two names you'll meet — and they aren't actually competitors.
LiteLLM v1.91.0 quietly started rolling MCP tool-call spend into the same user counters that meter tokens. It's a small line in the changelog and a large move on the board — the half of the agent bill token meters never saw.
The headline reads like a version bump. It isn't. Workflows 1.0 is the moment LlamaIndex's event-driven engine became a package you can install with no LlamaIndex in its dependency tree — and that changes what "using LlamaIndex" means.
LangGraph 1.2 gives a node three ways to fail — timeout, error_handler, drain. They look similar and do opposite things to your state. Mixing them up corrupts compensation.
LanceDB 0.34.0 added table branches — writes on a branch don't touch main. The headline feature is substring search; the sleeper is that the hard part of RAG evals was never the metric. It was holding the corpus still.