---
title: The second reader arrived, and only one of them signs
canonical: https://thebeat.dev/issues/2026-Q3/
published: 2026-10-06
covers_from: 2026-07-01
period: quarterly
covers: 2026-Q3
tags:
  - pricing
  - docs
  - dx
  - metrics
collection: issues
site: https://thebeat.dev/
license: https://creativecommons.org/licenses/by/4.0/
---

# The second reader arrived, and only one of them signs

> Across the quarter the free tier, the pricing page and the docs were each rebuilt for a reader that is software. The quarter's own evidence says which of those rebuilds get counted, and which one was an afternoon's insurance.

Thirteen weeks of launches read at the time as thirteen stories. Read whole, they are one. Every surface a developer marketer owns gained a second reader, an agent, and vendors rebuilt the signup, the price and the docs for it. The buyer did not change. The person who claims what the agent built is still the one who signs, and the quarter's numbers say that person is skeptical of the agent that found you. Build for the reader you can count, and put the pitch where the human arrives.

## 1. Put the signup after the first success, and the pitch on the claim page

The quarter's one movement took four launches to show its shape. Railway
[let anyone deploy without an account](https://blog.railway.com/p/deploy-without-account)
on August 17: 60 minutes to build, 24 hours to claim, a $3 cap on LLM credit.
Neon shipped
[Claimable Neon](https://neon.com/blog/an-agent-provisions-a-neon-backend-a-human-claims-it-later)
on September 10: an agent reads `neon.com/auth.md`, runs `neon claim create`,
and gets a Postgres project with no human account, capped at 100 MB, 1 GB of
transfer and 72 hours. Railway followed with
[`ssh railway.new`](https://railway.com/changelog/2026-09-25-free-vms-without-an-account)
on September 25. And on October 2 Neon
[resized its free plan](https://neon.com/blog/neon-free-plan-1-gb-per-project)
to 1 GB per project across 100 projects, because it is "creating new projects
at a rate of more than one per second".

Each week filed one of those as a feature. Together they are a new shape for
the free tier: not a signup, but a cap, a clock and a claim.

Why now? Because the first reader changed. Across the docs Mintlify hosts,
agents were
[66% of July's traffic](https://www.mintlify.com/blog/state-of-docs-traffic),
213 million agent requests against 105 million human page loads, up from
15.2% at the start of the year (Mintlify's own hosts). Stack Overflow's
[2026 survey](https://survey.stackoverflow.co/2026/community), published
this week from 30,903 developers, has 70% asking an AI agent when they are
stuck and 53% learning from AI tools. The agent reads your docs first, and
now it can build on you before anyone has typed an email address.

Here is the strongest case against the quarter's thesis, and it is a good
one. The buyer did not change. In G2's
[July survey of more than 1,000 B2B software buyers](https://company.g2.com/news/buyer-behavior-2026),
9% would let an agent execute a purchase within guardrails and 2% without
pre-approval. And the developer behind the agent is not sold on it: in the
Stack Overflow survey
[6 in 10 cite a reason to avoid AI](https://survey.stackoverflow.co/2026/ai)
at work, and 48% trust it only when they can check the answer themselves.
So the agent-as-buyer, the story W28 opened in July, did not arrive. What
arrived is narrower and more useful: the agent runs the trial, and a
skeptical human signs.

That is exactly why the claim step is the right shape and the agent checkout
is not. Neon says why it chose anonymity over an allowlist: "Which agents
discover the file? What do they request? How far do they get?" A signup form
counts people. A claim counts agents, and then counts the people who kept
what the agent built. It is the first activation event a machine reader
produces that a vendor can report.

Am I affected? If an agent can call your API and step one is "create an
account", yes. What does the agent get for free? Not a card. Three numbers
and a deadline. What does the human get? A page that says what was built,
what it costs after the clock, and why to keep it. That page is where your
buyer meets you for the first time, and today it is a login form.

The trade-off is real. Anonymous provisioning is an abuse surface, and the
caps are the abuse control. Railway's $3 cap is a pricing decision written
as a security one. Make yours the same way, and publish it.

**Your move:**

- Write the unclaimed tier as three numbers on the pricing page: storage,
  transfer, hours. Add the dollar cap on anything metered inside it.
- Publish what an agent may do with no key. `/auth.md` if you can, a
  paragraph in `llms.txt` if you cannot.
- Treat the claim page as a landing page. What the agent built, what it costs
  from tomorrow, in plain text. Count discovered, created and claimed as one
  funnel, and publish the claim rate.

Takeaway: for a human the signup was the front door. For an agent it is the
exit. The page at the exit is your new home page.

## 2. Price the unit the buyer counts, and ship the cap a quarter before the meter

The pricing thread moved three times in thirteen weeks, and each move was
away from the token. On July 20 GitHub priced
[Code Quality](https://github.blog/changelog/2026-07-20-github-code-quality-is-now-generally-available/)
at $10 per active committer plus a meter for the AI parts, the seat-plus-meter
shape the quarter started with. On September 1 Atlassian
[metered automation steps](https://www.atlassian.com/blog/company-news/expanded-usage-based-pricing),
a unit with no model behind it: 400 a month per Jira Standard user included,
[$0.50 per 1,000 above that](https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/),
billing from December 3, with the usage view and the admin limits shipped the
day of the announcement. On September 16 Sourcegraph billed
[Agentic Batch Changes per merged changeset](https://sourcegraph.com/blog/agentic-batch-changes-pricing),
nothing for a diff the team rejects, and Canva merged 50-plus pull requests in
the beta.

Then the model vendors stopped quoting the rate. Anthropic cut Opus 5.5 to
[$4 and $20 per million tokens](https://claude.com/pricing) from $5 and $25,
and led with "40% less on typical workloads". OpenAI halved GPT-6 Sol to
[$2 and $10](https://venturebeat.com/technology/openai-releases-gpt-6-sol-and-luna-models-slashing-api-costs-50-or-more),
confirmed permanent, and pitched $0.27 per task on one benchmark. DigitalOcean
wrapped raw agent meters in
[plans](https://www.digitalocean.com/blog/introducing-agent-droplets): $5 of
credit with no card, $50 a month at 15% off usage, $200 at 20% off, "no seat
charges".

Why did the rate stop carrying the claim? Because it stopped holding still.
Vercel's gateway put the average price per token
[down 23.2% in August](https://vercel.com/blog/ai-gateway-production-index-september-2026),
the third monthly fall in a row, with open-weight models at 56% of tokens and
14% of spend (Vercel's own traffic). And
[HarnessTax](https://harnesstax.github.io/), from UC Berkeley and Arena, ran
seven models through three coding-agent harnesses and found the same model
costing up to five times as much per resolved task while success rates
moved by about two points. A token rate is someone else's price list,
multiplied by a harness your customer did not choose.

Am I affected? If your pricing page carries a token, a credit or a compute
unit, yes. What replaces it? The unit your buyer already reports upward.
Intercom's Fin is [$0.99 per outcome](https://www.intercom.com/pricing), with
the outcome defined on the page in three lines and one charge per
conversation. A merged pull request is the coding version. A resolved ticket
is Atlassian's.

Two trade-offs, and the second is the one the quarter exposed. Outcome
pricing means you eat every failed attempt while the customer decides what
"merged" means, so the rate has to carry the merge ratio. That suits an
enterprise contract and not a $20 seat, which is why Sourcegraph's number is
not on its [pricing page](https://sourcegraph.com/pricing): "Starting at
$16K. Includes credits for AI features." It was not there in September and it
is not there today. An outcome price a buyer cannot read is a token meter with
better copy.

The second trade-off is sequence. Atlassian shipped the limit three months
before the bill. GitHub shipped the bill first: every Copilot Business and
Enterprise seat has been
[prepaid since October 1](https://github.blog/changelog/2026-08-28-upcoming-changes-to-github-copilot-policies-and-billing/),
with the promotional credits that hid the meter gone a month earlier and
prices unchanged. The first week was quiet. One public bill-shock post by the
end of October decides which order was honest.

**Your move:**

- Pick the unit your buyer reports upward, merged PRs, resolved tickets,
  deployed apps, and price one SKU on it by year end, with the rate and the
  definition of the unit in the same sentence.
- Put one worked bill on the pricing page: what your quickstart's first hour
  costs at list, with the workload written out. Restate every rate cut as its
  effect on that bill.
- If anything you sell will meter in the first half of 2027, ship the usage
  page and the admin limit this quarter, and date the bill.

Takeaway: a rate is the vendor's number. A bill is the buyer's. The cap is
the promise that makes the meter a price instead of a surprise.

## 3. We told you to ship llms.txt three times. Here is what it bought

This is the call the quarter corrected, and the corrected read changes what
you do with a week of someone's time. [W28](/issues/2026-W28) put `llms.txt`
beside OpenAPI as a machine-readable surface to publish. [W31](/issues/2026-W31)
narrowed that to "an afternoon's insurance for the agent surface" after
Google said in writing that it
["doesn't use them"](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide).
[W35](/issues/2026-W35) kept the file and threw out the proof, after a
satirical cats.txt collected every citation a vendor shows you. Three issues,
three narrowings, and none of them said what the file is for.

The quarter's last fortnight answered that. Gauge's instrumented sessions
opened a site's `llms.txt` in
[36.3% of build tasks and 0.5% of vendor-selection tasks](https://www.withgauge.com/blog/how-to-write-a-good-llms-txt-file)
(Gauge sells agent analytics and states no session count). A week later its
crawler logs showed that of roughly 600,000 requests carrying the
ChatGPT-User agent across more than 500 million bot events,
[none asked for the file](https://www.withgauge.com/resources/llms-txt-doesnt-help-ai-search-visibility)
(no period or site count stated). The crawler that produces citations never
reads it. The agent that already chose you does.

And the citation itself has a clock. Profound followed 883,000 pages through
seven engines for a year: the median page
[loses half its citation share within 11 days](https://www.tryprofound.com/blog/the-half-life-of-an-ai-citation-is-11-days)
of its peak, 78% do so within two weeks, and the engines barely agree with
each other, with correlations of 0.03 to 0.09 (Profound sells the tracker).
Pages cited by five or more engines were 5.5 times as likely to still be
above half their peak after eight weeks.

So what should the July move have been? The quarter says: the docs page that
explains your bill. Profound asked six engines
[7,600 pricing questions](https://www.tryprofound.com/blog/what-ai-agents-really-think-about-your-pricing)
about Cloud 100 companies. The company's own pricing page came first in 12%
of answers. Vendr came first in 18.7%, Reddit in 18.6%, G2 in 15.9%. Only 57
of 77 public pricing pages were fully readable to a bot. The exception was
Plaid, whose billing docs were cited in 70% of its answers against 64% for
its pricing page, and those docs publish no prices. They define the billing
model and say which numbers are not public. The same firm's August study of
[158,000 brand claims](https://www.tryprofound.com/blog/where-do-inaccurate-ai-claims-come-from)
found 54% of brands with an inaccurate claim citing their own site, and
pricing was 12% of claims and 24% of the inaccuracies. The engine quotes your
forgotten page with confidence.

Am I affected? If your plan for AI answers is a file and one content sprint,
yes. The file serves one reader at one step. The pitch belongs on the pages
the engines cite, and those pages need renewing.

The counter-case is that nobody has a conversion number for any of this, and
that is still true. Val Town's
[July datum](https://blog.val.town/aeo), most new Pro signups with a known
source arriving via AI, mostly Claude, is the only attributed figure any
vendor published all quarter, and it is a self-reported share, not a rate.
Which is the point: fund the pile you can attribute, and treat the rest as
hygiene.

**Your move:**

- Strip the pitch out of `llms.txt`. Make it a routing index for an agent
  already building on you: the quickstart, the reference, the billing page.
- Write the billing page in the docs. Plain HTML, one question per heading,
  every public number in the text, one plain line for each number that is
  not public. No tabs, nothing rendered client-side.
- Put a refresh date on every page that carries a citation and republish its
  facts monthly. Run the free check on all seven engines, and protect the
  pages that show up on five.

Takeaway: the file serves the agent that already picked you. The citation is
a lease. The docs page that explains your bill is what gets read at the pick.

## 4. Proof is a launch format now: a date, a number and the script

In July proof meant a dogfooding post. By October it had a shape with three
parts, and the fourth vendor to use it shipped the part the first three did
not.

Vercel put
[up to $1 million](https://vercel.com/blog/one-million-dollar-hacker-challenge-for-vercel-sandbox)
on breaking its sandbox, two weeks on HackerOne, $50,000 cap per report. The
tally reached the press on September 15:
[1,285 reports](https://www.securityweek.com/1-million-sandbox-challenge-uncovers-linux-kernel-flaws/),
one critical, seven high, 15 medium, 49 low, 19 informative, about $325,000
committed, and the two most serious bugs in the Linux kernel's networking
stack rather than Vercel's code. Docker rewrote its homepage to "Trust Docker
for the Agents You Don't", still the hero today, and shipped
[Cloud Sandboxes billed by the second](https://www.docker.com/blog/docker-cloud-sandboxes-wearedevelopers-recap/)
with its Kit spec under Apache 2.0 and a promise to the CNCF. Postman ran its
own monitor against a coding agent on one laptop from August 12 to September
9 and published the count against itself:
[22 secrets across 33 requests to 18 hosts](https://blog.postman.com/what-passport-found-in-3-weeks-of-ai-agent-traffic),
while the project's `.env` held four.

Then GitHub shipped the part the others left out. Its security agent
[found 24 Android vulnerabilities](https://github.blog/security/how-we-found-24-android-vulnerabilities-using-our-open-source-ai-security-agent),
and the post includes the taskflows, one command to run them on your own
repository (`./scripts/audit/run_mobile.sh myorg/myrepo`), an estimate of an
hour or two on a medium project, and the cost: a Copilot licence and a lot of
premium requests. The receipt ships with the script.

Why does this format work on this audience? Because the audience validates
by habit. Stack Overflow's survey has 48% trusting AI only when they can
check the answer. A number a reader can rerun is the only claim that survives
that reader. A number without a method is an adjective with digits, and the
quarter produced those too: a "97% of users pay us $0" with no denominator, a
"48% fewer tokens" resting on one task run twice.

The trade-off is that proof is necessary and not sufficient. Reputation
filled the room for Block's Buzz in July and the room still said no. And a
wager is only half a campaign until the result ships: Vercel's program page
promised a write-up of the attack techniques, the CVEs are pending, and as of
today that post does not exist.

**Your move:**

- Put one proof asset on next quarter's launch calendar with a date and a
  number: a pen test, a postmortem, a migration with its costs named.
- Ship the method with it. The script, the rubric or the sample, so a reader
  can rerun the number instead of taking it.
- Print the number that cuts against you beside the one that flatters, with
  your reading of why it is fine.

Takeaway: a claim that costs you something reads as proof. A claim a reader
can rerun reads as fact.

## Quick hits

- **Nobody priced the data clause after Meta.**\
  [W32](/issues/2026-W32) read Muse Code's contributor tier, $0.10 and $0.20
  per million tokens against $1.25 and $4.25
  [for training on your prompts](https://www.macrumors.com/2026/08/05/meta-muse-code-for-mac/),
  as a number every vendor now had to answer. By the August 31 clock no
  incumbent shipped or ruled out a tier, and the terms that did positioning
  work in Q3 were the unit and the window, not the data. Keep "we don't
  train on your code" at full price. [Thread](/threads/how-ai-features-get-priced).
- **The passive seat stayed a GitHub one-off, and the measurement thread closes.**\
  [W30](/issues/2026-W30) called a second vendor by end of Q3 and none came.
  The thread's question has its answer: report influenced pipeline,
  activation, first-party usage and AI-answer presence, and expect nobody
  else to, because
  [88% of engineering leaders say they measure AI ROI and 39% do it formally](https://www.slashdata.co/post/75-of-professional-developers-are-using-ai-assisted-tools-insights-on-developer-tools-usage-and-me)
  and
  [60.7% of DevRel teams](https://www.stateofdeveloperrelations.com/2024devrelreport)
  still name proving impact as their top challenge. The gap is
  organisational, and public evidence cannot close it.
  [Resolved](/threads/measuring-influence-not-attribution).
- **The MCP migration call expired on a date the spec made impossible.**\
  [W31](/issues/2026-W31) gave hosts until the end of September to publish a
  migration plan. The
  [2026-07-28 spec](https://blog.modelcontextprotocol.io/posts/2026-07-28/)
  carries a twelve-month minimum window, so nothing can be removed before
  July 2027 and no host had a forcing date. The call was built on a deadline
  the policy did not contain, and it moves to the end of the year with that
  reason. [Thread](/threads/agents-as-the-first-reader).
- **The deprecation ledger closed the quarter's cases as announced.**\
  GitHub Models went from
  [announcement to dead in 29 days](https://github.blog/changelog/2026-07-30-github-models-is-now-retired);
  Spark [froze on August 4 with export by the 31st](https://github.blog/changelog/2026-08-04-upcoming-deprecation-of-github-spark-on-github-com/);
  Cerebras' free tier became
  [$5 of credit, 30 days, card required](https://www.cerebras.ai/pricing);
  HCP Vagrant's registry
  [ends new boxes October 1, support November 2, operations December 31](https://developer.hashicorp.com/hcp/docs/vagrant/hcp-vagrant-eol),
  the dates [W37](/issues/2026-W37) corrected from a June 2027 the archive
  had carried. Publish your window before you need it; the twelve-month end
  of the ledger is the one that reads as infrastructure.
- **Community and events still return the most, say the marketers.**\
  In Draft.dev's
  [2026 Developer Marketing Survey](https://draft.dev/2026-developer-marketing-survey)
  64% of developer-marketing leaders say community and events deliver their
  highest return and 62% are raising budgets, while 96% have tried AI and 7%
  find it very useful (a content vendor's panel, size unstated). The channel
  the quarter's launches ignored is the one practitioners still fund first.

## Watch

1. **A claim rate is published by December 31.** Neon or Railway publish
   discovered, created and claimed for the anonymous tier, or a third vendor
   ships a claim-later tier, checkable by fetching
   [`/auth.md`](https://workos.com/auth-md) from Supabase, PlanetScale and
   Vercel by October 31 as [W37](/issues/2026-W37) asked. A rate confirms the
   agent free tier as a category and gives the referral loop its second
   datum. No number by year end means two vendors ran an experiment, and the
   loop closes.
2. **The outcome unit reaches a public price by December 31.** A dollar
   figure per merged changeset on
   [sourcegraph.com/pricing](https://sourcegraph.com/pricing), or a second
   coding agent billing per merge. Either makes outcome pricing a
   pricing-page claim. Silence leaves it a sales motion wearing the words,
   and a quiet October for Copilot's prepaid seats would say the meter was
   explained.
3. **Vercel publishes the techniques write-up by November 30.** The
   [program page](https://vercel.com/blog/one-million-dollar-hacker-challenge-for-vercel-sandbox)
   promised it, the kernel fixes are under private review, and the CVEs are
   pending. A published report completes the campaign and sets the bar for
   every attack-me launch after it. Nothing by the end of November means the
   wager was the campaign.

## Sources

- [Railway — Railway for Everyone: deploy for free without a Railway account](https://blog.railway.com/p/deploy-without-account)
- [Railway changelog — Free VMs without an account](https://railway.com/changelog/2026-09-25-free-vms-without-an-account)
- [Neon — Claimable Neon: provisioned by agents, claimed by humans](https://neon.com/blog/an-agent-provisions-a-neon-backend-a-human-claims-it-later)
- [Neon — 100 projects for free, with 1 GB of Postgres storage each](https://neon.com/blog/neon-free-plan-1-gb-per-project)
- [Mintlify — The state of docs traffic: a 2026 midyear report](https://www.mintlify.com/blog/state-of-docs-traffic)
- [Stack Overflow — 2026 Developer Survey, AI](https://survey.stackoverflow.co/2026/ai)
- [Stack Overflow — 2026 Developer Survey, Community](https://survey.stackoverflow.co/2026/community)
- [G2 — 2026 Buyer Behavior Report (announcement)](https://company.g2.com/news/buyer-behavior-2026)
- [GitHub changelog — Code Quality is now generally available](https://github.blog/changelog/2026-07-20-github-code-quality-is-now-generally-available/)
- [Atlassian — Atlassian's usage-based pricing](https://www.atlassian.com/blog/company-news/expanded-usage-based-pricing)
- [Atlassian Support — How is my automation usage calculated](https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/)
- [Sourcegraph — Coding agents usually can't price on outcomes. Ours can.](https://sourcegraph.com/blog/agentic-batch-changes-pricing)
- [Sourcegraph — Pricing](https://sourcegraph.com/pricing)
- [Claude — Pricing](https://claude.com/pricing)
- [VentureBeat — OpenAI releases GPT-6 Sol and Luna, slashing API costs 50% or more](https://venturebeat.com/technology/openai-releases-gpt-6-sol-and-luna-models-slashing-api-costs-50-or-more)
- [Vercel — AI Gateway Production Index, September 2026](https://vercel.com/blog/ai-gateway-production-index-september-2026)
- [HarnessTax — How Much Does the Harness Matter for Coding Agents?](https://harnesstax.github.io/)
- [DigitalOcean — Introducing Agent Droplets](https://www.digitalocean.com/blog/introducing-agent-droplets)
- [Intercom — Pricing](https://www.intercom.com/pricing)
- [GitHub changelog — Upcoming changes to GitHub Copilot policies and billing](https://github.blog/changelog/2026-08-28-upcoming-changes-to-github-copilot-policies-and-billing/)
- [Google Search Central — AI features and your website](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)
- [Gauge — How to write a good llms.txt file](https://www.withgauge.com/blog/how-to-write-a-good-llms-txt-file)
- [Gauge — llms.txt doesn't help AI search visibility](https://www.withgauge.com/resources/llms-txt-doesnt-help-ai-search-visibility)
- [Profound — The half-life of an AI citation is 11 days](https://www.tryprofound.com/blog/the-half-life-of-an-ai-citation-is-11-days)
- [Profound — What AI agents really think about your pricing](https://www.tryprofound.com/blog/what-ai-agents-really-think-about-your-pricing)
- [Profound — Where do inaccurate AI claims come from?](https://www.tryprofound.com/blog/where-do-inaccurate-ai-claims-come-from)
- [Val Town — On AEO](https://blog.val.town/aeo)
- [SecurityWeek — $1 million sandbox challenge uncovers Linux kernel flaws](https://www.securityweek.com/1-million-sandbox-challenge-uncovers-linux-kernel-flaws/)
- [Vercel — $1 million hacker challenge for Vercel Sandbox](https://vercel.com/blog/one-million-dollar-hacker-challenge-for-vercel-sandbox)
- [Docker — Docker Cloud Sandboxes: recap from WeAreDevelopers](https://www.docker.com/blog/docker-cloud-sandboxes-wearedevelopers-recap/)
- [Postman — What Passport found in 3 weeks of AI agent traffic](https://blog.postman.com/what-passport-found-in-3-weeks-of-ai-agent-traffic)
- [GitHub — How we found 24 Android vulnerabilities using our open source AI security agent](https://github.blog/security/how-we-found-24-android-vulnerabilities-using-our-open-source-ai-security-agent)
- [MacRumors — Meta Muse Code pricing](https://www.macrumors.com/2026/08/05/meta-muse-code-for-mac/)
- [SlashData — Insights on developer tools usage and measuring AI ROI](https://www.slashdata.co/post/75-of-professional-developers-are-using-ai-assisted-tools-insights-on-developer-tools-usage-and-me)
- [State of Developer Relations — 2024 report](https://www.stateofdeveloperrelations.com/2024devrelreport)
- [Model Context Protocol — The 2026-07-28 specification](https://blog.modelcontextprotocol.io/posts/2026-07-28/)
- [GitHub changelog — GitHub Models is now retired](https://github.blog/changelog/2026-07-30-github-models-is-now-retired)
- [GitHub changelog — Upcoming deprecation of GitHub Spark](https://github.blog/changelog/2026-08-04-upcoming-deprecation-of-github-spark-on-github-com/)
- [Cerebras — Pricing](https://www.cerebras.ai/pricing)
- [HashiCorp — HCP Vagrant Registry end of life](https://developer.hashicorp.com/hcp/docs/vagrant/hcp-vagrant-eol)
- [Draft.dev — 2026 Developer Marketing Survey](https://draft.dev/2026-developer-marketing-survey)
- [WorkOS — auth.md, open protocol for agent registration](https://workos.com/auth-md)

## Related

- [Week 28 — The agent reading your docs is starting to shop](https://thebeat.dev/issues/2026-W28/)
- [Week 29 — Incumbents start shipping for the agent-as-buyer](https://thebeat.dev/issues/2026-W29/)
- [Week 30 — The AI seat gets a price, and the empty ones get counted](https://thebeat.dev/issues/2026-W30/)
- [Week 31 — Twelve months or six weeks, the deprecation window is the positioning now](https://thebeat.dev/issues/2026-W31/)
- [Week 32 — The coding agent became a commodity, now the terms are the pitch](https://thebeat.dev/issues/2026-W32/)
- [Week 33 — The rail is the product now](https://thebeat.dev/issues/2026-W33/)
- [Week 34 — The trust surface is the campaign now](https://thebeat.dev/issues/2026-W34/)
- [Week 35 — The agent's front door is a tool, not a file](https://thebeat.dev/issues/2026-W35/)
- [Week 36 — Your docs are production now](https://thebeat.dev/issues/2026-W36/)
- [Week 37 — Your free tier now has a claim step](https://thebeat.dev/issues/2026-W37/)
- [Week 38 — Price the merge, not the token](https://thebeat.dev/issues/2026-W38/)
- [Week 39 — Quote the bill, not the rate](https://thebeat.dev/issues/2026-W39/)
- [Week 40 — An AI citation is rented, and the lease is 11 days](https://thebeat.dev/issues/2026-W40/)
- [Thread — When an agent is the first reader of your docs](https://thebeat.dev/threads/agents-as-the-first-reader/)
- [Thread — How AI features get priced](https://thebeat.dev/threads/how-ai-features-get-priced/)
- [Thread — Proof over adjectives](https://thebeat.dev/threads/proof-over-adjectives/)
- [Thread — Measuring DevRel by influence, not attribution (resolved)](https://thebeat.dev/threads/measuring-influence-not-attribution/)

---

Part of [The Beat — developer marketing, on the record](https://thebeat.dev/). Content license: CC BY 4.0 — quote it, link the canonical page.