Last week’s issue was honest about the size of the agent-as-buyer signal: two Show HN launches with a handful of points between them. The category was forming; nobody big had shipped for it. That took one week to change. GoDaddy and Atlassian — neither a devtools darling — both shipped real product for the agent-as-user within two days of each other.

The first agent-safe checkout

On July 14, GoDaddy launched a Developer Platform whose docs assume the reader might be a model. Every page is available as markdown, the full doc set ships as one plain-text file at /llms-full.txt, and the reference is OpenAPI per version. The quickstart’s first move is telling: hand domains-v3.json to your LLM as context, “so your agent reads the same docs you do.”

The more interesting half is the purchase flow, because it assumes the actor might be a model too. Registering a domain is quote-then-execute: a quote call returns a quoteToken with a short expiry and the exact price, so an agent can’t be surprise-charged. Every registration attempt carries a per-attempt idempotency key — retry with the same key and you get the same registration, not a second one. A consent object records which agreements were accepted and when. And there is no field for a card number anywhere in the API.

A day later, Atlassian repositioned Jira as the orchestration hub for human-plus-agent teams: a Jira Planner that turns rough ideas into technical specs, and work items you can assign to Claude Code, Cursor, GitHub Copilot, or Jira’s own coding agent (Codex is coming soon). Note the pitch: Atlassian’s numbers say engineers’ AI usage is up 65% while velocity gains sit around 10%, so they’re selling the coordination bottleneck, not code generation. That’s a company repositioning around what the new user of its product actually is — for a tool developers have long resented, a genuinely risky move.

The deep dive published Thursday gave this thread its frame: act now on the reading layer, design for the selection layer, don’t buy measurement yet. GoDaddy is the strongest evidence so far for the middle layer — the first mass-market incumbent to ship agent-safe transaction design as a product surface, not a blog post. What to do: if your API sells anything, the trio is copyable — quote-then-execute, idempotency keys, an explicit consent record. And the quickstart line — “hand this spec to your LLM” — costs nothing to steal today.

A free tier is a contract

Cerebras emailed free-tier users that the current free API tier ends August 17, replaced by $5 in credits behind a payment method. Earlier this year, per one practitioner’s account (single-sourced, worth that caveat), Cerebras had already pruned its free-tier catalog from about a dozen models to two — no notice that reached him, hardcoded integrations breaking on silent 404s.

Be honest about the reaction’s size: the HN thread drew 4 points and two resigned comments, plus some grumbling from infrastructure accounts on X. This is not a firestorm — and that’s precisely what makes it worth studying. Developers rarely rage-quit over a sunset; they quietly re-anchor on “this vendor breaks things without telling me” and route around you at the next build-vs-buy decision. The sunset itself is defensible — free inference is expensive, and requiring a payment method is an ordinary maturation step. Doing it quietly is the unforced error.

The play: treat free-tier terms and model catalogs as versioned API surfaces. Deprecations get a date, an email that actually reaches the people with hardcoded integrations, an error response that says deprecated instead of 404, and a migration path. The guide’s DX section now says this in the evergreen voice.

Also this week

  • Launch HN is the default GTM channel for agent-infra startups. Agnost AI (YC S26, July 14, 85 points) extracts user feedback from agent conversations — the DevRel “carry the voice back to product” job, productized. Coasty (YC S26, July 15, 44 points) sells computer-use agents as an API. Two batchmates, same channel, same week.
  • The Otter playbook behind Friday’s article. Common Room’s case study says Otter.ai doubled outbound pipeline by scoring accounts on roughly 80% first-party product behavior over firmographics, capped at 10–12 total plays. Context on why that data is being repriced — Zoom’s acquisition of Common Room is the third GTM-signal roll-up in eight months — is in Friday’s piece.
  • Practitioners on marketing in the age of slop (Ask HN, small thread, useful texture): pick two or three forums where your customers ask questions and answer them 20 minutes a day before ever pitching; fix paid search with exact-match and negative keywords rather than abandoning the channel.

One thing to watch

DevRelCon NYC runs July 22–23. One speaker’s teaser claims DevRel job postings now silently screen for specific, measurable-ROI skills the listings don’t state — so far a single practitioner’s account. The falsifiable call: if the conference recaps over the next two weeks show measurement and ROI dominating the program — multiple talks, not one — the influence-over-attribution consensus has hardened into a hiring bar, and “can you quantify your impact” becomes the DevRel interview question of 2026. If the recaps are the usual community-and-content fare, the teaser was one person’s job search.