Three platforms every founder shipping image, video, or voice AI ends up comparing — and the real axis isn't price per hour. It's how much of the stack each one hands you, which quietly decides your bill, your cold starts, and how much code you own.
Article 50 of the EU AI Act is enforceable August 2, 2026. If you deploy a chatbot or an AI voice agent to EU users, the 'you're talking to an AI' duty lands on you — not your model vendor. Here's the short version, a checklist, and the disclosure to ship.
The Digital Omnibus delayed the Act's hardest rules to 2027. Article 50 was not one of them: if your product generates images, audio, video, or text, you must now mark it so a machine can detect it was AI-made. Here's the obligation, the December grace you might still have, and the one standard the Commission has already blessed.
These two rock-bottom models aren't fighting for one slot — one is the cheap text-and-tool workhorse, the other is the first cheap-enough pair of eyes, and the deciding question is whether your loop reads pixels.
No new architecture, no bigger model — just another round of post-training. DeepSeek says its $0.14/M budget model now beats its flagship preview on all nine agent benchmarks. Every number is vendor-stated. Here's what a founder should actually do with that.
Both Anthropic and Google will now run the agent loop for you — no while-loop, no state file, no scheduler. But they hand you very different things. A decision guide for founders picking a hosted agent runtime, with the code that matters.
Qwen3.7 Flash lists a 1M-token window at ~$0.03/$0.13 per million tokens. The tempting conclusion — stop compacting, just dump everything in — is half right. Cheap context fixes the bill. It does nothing for the rot.
The AI-agent research at Black Hat this week rhymes on one point: the guardrail you wrapped around the model isn't where you get owned. Three verified briefings, and the founder fix each one implies.
On August 6, AWS moves Agent Registry out of preview and out of the bedrock-agentcore namespace into a dedicated agent-registry namespace — quietly making agent discovery a hyperscaler default.
A registry tells you what agents and tools exist; a gateway controls how traffic to them is routed, authed, and governed. Buy the wrong one and you solve a problem you don't have.
Five verified moves a team of one should act on this week: a token bill that just dropped 5×, a compliance deadline that lands on you and not your model vendor, a billion-dollar bet on governing what your agents can touch, Nvidia turning compute into equity, and where the agent money is actually going.
Last week the headlines were specs and model weights. This week the signal is capital and access — a record raise into an open-weight lab, the frontier lab widening who gets in, and the cheap-multimodal floor dropping again. For a team of one, your inputs got cheaper and your competition got better funded.
You turned on speculative decoding and your endpoint got slower. That's not a bug — it's the design. Spec decode trades spare compute for lower latency, and above a certain batch size you've run out of spare compute. Here's where the line is and how to measure yours.
The per-million number on a model's pricing page is the worst predictor of your bill. Three variables — cache hit rate, output-to-input ratio, and how many turns the loop runs — decide what an agent task actually costs. Here's the worksheet that turns them into a number.
The reason your enterprise deal stalls at 'we can't send customer data to an LLM' isn't the model — it's that you can only promise the host never sees the prompt. Tinfoil runs the model inside a hardware enclave with remote attestation, so you can prove it instead.
What Test Companion is, who it's for, how to start (it's in free Alpha), and the honest catch — BrowserStack put a test-writing, failure-diagnosing, self-healing agent inside your editor, wired to a 30,000-device real cloud.
The deal is verbal-yes until their security team sends the questionnaire. Here's the exact list of artifacts that unblocks it — SOC 2, a DPA, a subprocessor register, and the AI-specific answers that are new in 2026 — and the order to get them in without torching six weeks.
The generative-agents researcher behind 'Smallville' just closed a $200M Series B, five months after a $100M A. Simulated users are now a funded category. The founder question isn't whether to use them — it's which decision you let them near.
OpenAI's July 29 engineering note says it used GPT-5.6 Sol inside Codex to rewrite its own inference kernels and redesign its speculative-decoding draft model — 20% cheaper serving, 15%+ faster tokens. The part a solo founder can copy isn't the frontier model. It's the two things that made it safe.
Luna's price fell to $0.20/$1.20 per million tokens, Terra dropped 20%, and 'Priority Processing' quietly became 'Fast mode.' If you picked a model or set a price in early July, the math you used is already stale.
python-1.13.0 and dotnet-1.16.0 landed July 30. The headline isn't a smarter agent — it's reusable session stores and checkpoints that replay from the original input *and* the human approvals, so a long run survives a restart without asking your operator twice.
Streamable HTTP hands your client a Last-Event-ID header that promises to resume a dropped stream. It resumes nothing unless the server kept the events — and the SDK's default store loses them the moment your process restarts.
An MCP server and a REST API aren't rivals doing the same job. Choose by who the caller is and who decides to call — a developer at build time, or a model in the moment.
Anthropic's harness for agents that run for hours doesn't add memory to the model. It writes the state to disk — a progress file, an init script, and a commit per feature — so a fresh context window can read where the last one stopped.
Your MCP server works in the chat window — but does tools/list still return the right schema after your last refactor? Here's the three-layer way to test one: interactive Inspector, a scriptable CLI check, and a programmatic client you can run in CI.
Wire your agent's cost, latency, and quality scores to threshold alerts that page Slack, trigger a GitHub Action, or hit a webhook — so a regression finds you, not the other way around.
SGLang 0.5.16 shipped DSpark: a speculative-decoding scheme that stops guessing a fixed draft length and lets each verify window size itself from the draft's own confidence. Here are the three flags that turn it on and when it actually pays.
Every model that wants to run your agent now quotes a tool-use score. Here's how to tell which of those numbers predicts a reliable agent in production — and why a 90% on the leaderboard can still fail one call in three when it matters.
A new model claims #1 on a coding leaderboard almost every week. Here's how to tell which of those numbers should move your model choice — and which are marketing that happens to be true.