Build or Replaced
Today: Agents can now create Cloudflare accounts, buy domains, and deploy | StarFighter 16-Inch | DNSSEC disruption affecting .de domains – Resolved Episode date: 2026-05-06.
Download MP3 →The brainstorming skill is for software design — the user has provided a complete, unambiguous spec. I'll write the script directly. JOSH: It's Wednesday, May 6th. This is Build or Be Replaced — powered by ScanBrief.dev. I'm Josh, here with Erik Anderson. ERIK: Agents are buying domains, spinning up infrastructure, and deploying to production. No human required. We're going to talk about what that actually means. JOSH: Stick around — Erik's got an AI pro tip at the end about picking the right interface before you pick a model. [pause] JOSH: First headline — Coinbase is cutting 14% of its workforce. ERIK: About 1,100 people. Crypto exchange economics are brutal right now — revenue compression, regulatory pressure, and automation keeps getting more convincing. When you cut that deep, you're betting the remaining headcount plus better tooling holds the output steady. [beat] JOSH: Next — DNSSEC on .de domains had a major disruption. Resolved, but it was widespread. ERIK: DNS is invisible until it breaks. DNSSEC adds a cryptographic trust layer on top — when that fails, legitimate traffic stops. .de is one of the largest country-code TLDs. An incident there isn't a Germany-only problem. It's a reminder that the internet's trust infrastructure is thinner than people think. [beat] JOSH: And Gemma 4 just got a 3x inference speed boost through multi-token prediction. ERIK: Instead of predicting one token at a time, the model drafts several simultaneously, then verifies them. Speculative decoding with MTP drafters. Same output quality, 3x faster. If you're running local inference, this matters — the bottleneck has always been memory bandwidth, not compute. This directly attacks that. [pause] JOSH: Okay, let's go deep. The big one today — agents can now autonomously create Cloudflare accounts, register domains, and deploy production applications. Co-designed with Stripe? ERIK: Yeah. Cloudflare and Stripe worked on a protocol together. An agent — with the right authorization — can spin up a Cloudflare account, set up DNS, buy a domain, generate API tokens, manage subscriptions, and push a live application. Nobody touches it. JOSH: What is the protocol actually doing? ERIK: Defining a structured set of actions the agent can take and the permissions model behind them. Stripe handles the billing side — the agent can provision paid services and manage subscriptions programmatically. Cloudflare handles the infrastructure side. Together, that's the two biggest pieces of a production deployment that used to require a human with a credit card and a login. [beat] JOSH: So what does that unlock? ERIK: Full autonomous deployment pipelines. PrimeBus ran 2,124 automation events today across five projects. It detects test failures, generates fix variants, runs tests, merges the winners. But the boundary stops at the code level. The domain, the Cloudflare config, the billing — those still have a human owner. With this protocol, you hand an agent a budget, a spec, and an authorization scope, and it returns with a live URL. JOSH: That's a fundamentally different kind of automation. ERIK: It is. Most automation is process automation — speeding up steps a human was already taking. This is infrastructure autonomy. The agent isn't executing your runbook faster. It's making provisioning decisions. That's a different trust level. [beat] JOSH: Is that dangerous? ERIK: Depends entirely on the authorization model. The risk isn't the agent — it's the human who grants a scope wider than intended because it's easier than thinking through the permissions carefully. If you give an agent unrestricted Cloudflare API access and it does something unexpected, that's a scope problem. Least privilege applies to agents the same way it applies to service accounts. You wouldn't give a cron job root. Don't give an agent a scope it doesn't need. JOSH: Where does this go from here? ERIK: Cloudflare and Stripe didn't build this for fun. Companies are laying rails because there's a destination in mind. Autonomous SaaS products. Agents that spin up, operate, and manage their own infrastructure. The deployment step was the last manual bottleneck in a fully autonomous software system. It just got removed. [pause] JOSH: Let's talk cost. There's a benchmark showing computer use — vision-based agents — are 45 times more expensive than structured APIs for the same tasks. ERIK: Someone ran the comparison on admin panel work. Vision approach — agent sees the screen, figures out what to click, clicks it, checks what changed. Versus hitting a structured API endpoint. Forty-five times the cost. Same result. JOSH: Why is vision so much more expensive? ERIK: Tokens. Every screenshot is image tokens. The model processes the full visual frame, reasons about UI state, decides what to do, takes an action, processes the next screenshot. You're paying for visual reasoning on every single step. A structured API call skips all of that — one request, one response, done. [beat] JOSH: So when does vision actually make sense? ERIK: Last resort. When there is genuinely no API, no structured output format, no programmatic access to the data or the action you need. Legacy vendor portals from 2003. Government systems that never got modernized. Anything where the only interface is a browser someone built assuming a human would sit in front of it. That's the correct use case. JOSH: And people are using it as the default? ERIK: Some are. Because it's flexible — works on anything with a UI. But flexibility has a price. ScanBrief pulled and scored 49 items across 56 sources this morning. If I ran that through a vision scraper instead of structured ingestion, the cost difference would end the project. I've got 88 services running on the production server right now. I can't absorb 45x overhead on any of them. [beat] JOSH: What should builders actually take from this? ERIK: Audit your interfaces before you build. Is there an API? Use it. Structured output? Use it. Webhook? Use it. If none of those exist, you're in vision territory — but you should know that going in and size the cost accordingly. The interface is a cost and reliability decision, not just a technical one. Most people treat it like a technical detail and then wonder why the bill is wrong. [pause] JOSH: Last one — Telus is using AI to alter call center agent accents in real time. While they're on the phone with customers. ERIK: That's a strange one to drop on a Wednesday. JOSH: What's actually happening? ERIK: Real-time voice conversion. The agent speaks normally. The audio runs through a model that shifts the accent toward something considered neutral by the system — which in practice means North American. The customer hears a modified voice. The agent knows their voice is being altered. JOSH: Is that fixing the problem or hiding it? ERIK: Routing around it. The bias some callers have toward non-native accents doesn't go away — the caller just doesn't have the information to trigger it. Telus probably gets better satisfaction scores. The agent still knows what's happening to their voice. Both things are true at the same time. [beat] JOSH: What's interesting to you technically? ERIK: Real-time low-latency voice conversion at call center scale is hard. The latency budget for phone audio is tight — you can't process a full sentence and play it back, you're converting on the fly. If Telus is doing this in production at volume, the model quality and pipeline architecture is more sophisticated than the headline suggests. That part is worth paying attention to, separate from the ethics question entirely. JOSH: It's automation applied to the worker, not replacing the worker. ERIK: That's the edge case nobody talks about enough. Automation that modifies a human's output while the human is still there. Where that goes as voice models improve — that's a harder question than accent modification. [pause] ERIK: This episode is sponsored by Prime Automation Solutions. If you're still doing it manually, we automate it. Also, special on a website — $250. primeautomationsolutions.com [pause] JOSH: Alright, what's the AI pro tip today? ERIK: Pick your interface before you pick your model. Most builders start with the model — which Claude, which Gemini, which local model — then figure out how to wire it up. Backwards. The interface dictates the architecture, the cost, and the reliability ceiling. If there's a structured API, use it. Structured output format, use it. Webhook, use it. If the only option is a UI and you need automation, that's when you decide whether vision is worth 45x. The model selection comes after the interface decision, not before. Get the interface right and the rest of the architecture gets easier. That's your tip. Use it. [pause] ERIK: If you're building toward financial independence through automation, my first book walks through the whole path. Free chapter at erikandersonbook.com. [pause] JOSH: One more thing — we started a Discord for builders. If you're shipping AI, automation, or anything that makes a human obsolete — come hang out. Link at buildorbereplaced.dev. ERIK: Post what you built. We'll post what we're building. Real wins, real builds, no fluff. [pause] ERIK: Build or be replaced. JOSH: If you want these signals in your inbox every morning, scanbrief.dev. See you tomorrow.