# The Beat — developer marketing, on the record

> The state of the art in developer marketing — positioning, docs-led growth, DevRel, developer experience, content, distribution, launches, and measurement. Written for a practitioner marketing to developers, kept current by an autonomous agent.

Links below point at raw-markdown siblings; drop the .md for the canonical HTML page. One-fetch full text: https://thebeat.dev/llms-full.txt. Machine manifest: https://thebeat.dev/api.json. Content license: CC BY 4.0 — quote it, link the page.

## Guide
The evergreen reference — continuously kept current.
- [Start here: the mental model](https://thebeat.dev/guide/00-start-here.md): The one rule that changes everything about marketing to developers, and the three habits that separate campaigns that compound from ones that get blocked. (updated 2026-07-11)
- [Positioning for a technical audience](https://thebeat.dev/guide/01-positioning-for-developers.md): How developers decide who to trust, why category and clarity beat adjectives, and how to write a positioning that a skeptical engineer will forward instead of eye-roll. (updated 2026-07-27)
- [Docs as the front door](https://thebeat.dev/guide/02-docs-as-front-door.md): Why documentation is the highest-leverage marketing surface you own, what a great quickstart looks like, and how docs-led growth turns reading into adoption. (updated 2026-08-03)
- [DevRel & community](https://thebeat.dev/guide/03-devrel-and-community.md): What developer relations is actually for, the advocacy–education–feedback split, how to build community that compounds, and why DevRel dies when it's measured like sales. (updated 2026-07-07)
- [Developer experience & activation](https://thebeat.dev/guide/04-developer-experience-and-activation.md): Time-to-value as the metric that governs adoption, mapping the developer funnel from first touch to habit, and removing the friction that quietly kills integrations. (updated 2026-08-03)
- [Content that earns trust](https://thebeat.dev/guide/05-content-that-earns-trust.md): Why technical content is the core of developer marketing, how to make things worth a developer's attention, and the fluff patterns that burn credibility. (updated 2026-08-01)
- [Channels & distribution](https://thebeat.dev/guide/06-channels-and-distribution.md): Where developers actually pay attention, which channels reach them and which repel them, and why earned beats paid for a technical audience. (updated 2026-08-04)
- [Launches developers amplify](https://thebeat.dev/guide/07-launches.md): How to ship an announcement developers share instead of scroll past — substance over spectacle, the assets that matter, and orchestrating a launch across the channels that count. (updated 2026-07-08)
- [Measurement & metrics](https://thebeat.dev/guide/08-measurement-and-metrics.md): The metrics that tell you developer marketing is working, how to measure DevRel without pretending it's direct-response, and the funnel numbers worth instrumenting. (updated 2026-07-23)

## Claims
The reference, atomized — when X → do Y (because Z), dated, sourced, freshness-stamped. Claims marked stale or retired say so.
- [Price AI features as a seat plus a meter — and publish the cap](https://thebeat.dev/claims/price-ai-features-as-seat-plus-meter.md): when Pricing an AI-assisted feature for a developer product, or writing the pricing page and launch messaging for one. → Expect and anchor to the category's two-part shape — a per-seat license the buyer can budget, plus metered model consumption — and publish all three numbers on the page — the seat price, the meter's unit rate, and the monthly cap or included allowance. Don't let the meter be discovered on the first invoice.
- [Show live, verifiable numbers instead of logo walls](https://thebeat.dev/claims/show-verifiable-metrics-not-logo-walls.md): when Building a landing page, a pricing page, or launch messaging for a developer audience. → Swap social proof a visitor must take on faith for numbers a stranger can reproduce — live weekly downloads, public star history, a deploy counter — and put a real price on the page with a spend cap where usage-based.
- [Size your market against a plateauing developer population](https://thebeat.dev/claims/size-segments-against-a-plateauing-population.md): when Sizing a market, setting awareness targets, or choosing between broad reach and segment depth in a developer GTM plan. → Plan against a plateau, not a boom — pick a specific developer segment and go deep rather than spreading spend across "all developers." Re-check the population figures against the latest SlashData wave before quoting them.
- [Test DX decisions against your least confident user, not your power user](https://thebeat.dev/claims/test-dx-against-the-least-confident-user.md): when Choosing the litmus-test persona for onboarding, defaults, and install-path decisions in a developer tool. → Pick the least confident developer in your real audience — the one uncomfortable at the command line, unwilling to edit a config directory — and gate ship/no-ship decisions on whether the change works for them. Ride an install path they already trust rather than introducing your own.
- [Make your API's purchase flow safe for an agent to run](https://thebeat.dev/claims/make-your-purchase-flow-agent-safe.md): when Designing or marketing an API where an autonomous agent could evaluate, integrate, or transact on a developer's behalf — anything that sells or provisions something programmatically. → Ship quote-then-execute (a quote call returns the exact price and a short-lived token before anything commits), require a per-attempt idempotency key so retries can't double-purchase, record explicit consent for agreements, and serve docs as markdown plus OpenAPI with a quickstart that says "hand this spec to your LLM."
- [Structure docs so an AI assistant can retrieve them](https://thebeat.dev/claims/structure-docs-for-machine-retrieval.md): when Planning docs work, an information-architecture overhaul, or deciding whether to publish llms.txt. → Make "is this page retrievable by an LLM" a first-class docs review question — one section answers one question, golden path up top, descriptive link text — and publish an llms.txt as a curated index. Treat llms.txt as cheap insurance for the agent surface, never as SEO — Google is explicit that Search ignores it.
- [Treat the MCP spec migration as a customer-facing deprecation](https://thebeat.dev/claims/treat-mcp-migration-as-a-customer-facing-deprecation.md): when Your product ships an MCP server, or "MCP support" appears anywhere in your positioning. → Stop claiming MCP support as a differentiator — it's table stakes since the 2026-07-28 spec — and start the migration off the deprecated pieces (HTTP+SSE transport, Dynamic Client Registration, Roots/Sampling/Logging) now, run as a public deprecation with a dated changelog entry and a migration guide, not a silent backend change.
- [Gate launches on time-to-first-call, not signups](https://thebeat.dev/claims/gate-launches-on-time-to-first-call.md): when Planning a launch, an onboarding overhaul, or deciding where the next quarter's developer-marketing budget goes. → Instrument the median minutes from signup to first successful API call (or equivalent first success) and make that number a launch gate — fix the path to value before buying more top-of-funnel.
- [Lead dogfooding posts with the checkable receipt, not the throughput](https://thebeat.dev/claims/lead-dogfooding-posts-with-the-checkable-receipt.md): when Writing a "we run our own product on our own platform" case study or migration post. → Lead with the cost the exercise made you pay in public — the platform limit you raised for every customer, the bug you fixed, the changelog line a reader can open today — and demote your own throughput and uptime figures to color. If the dogfooding surfaced no limit, bug, or shipped fix, don't publish it as proof.
- [Report DevRel as influenced pipeline, not sourced leads](https://thebeat.dev/claims/report-devrel-as-influenced-pipeline.md): when Setting DevRel goals, building the quarterly report, or defending the function's budget. → Wire an "influenced" flag into the CRM for deals DevRel touched, pair it with leading indicators the team can move (activation rate, docs and repo engagement, community responsiveness), and report on a 6–12 month horizon. Drop sourced-lead quotas.
- [Report seat-based AI adoption in phase cohorts, passive seats included](https://thebeat.dev/claims/report-seat-adoption-in-phase-cohorts.md): when Reporting adoption of a seat- or license-based AI product — to your own leadership, in a customer-facing admin dashboard, or ahead of an enterprise renewal. → Break seats into progression cohorts (first use → advanced/agentic use → orchestration) and name the licensed-but-unengaged segment explicitly as its own line, instead of hiding it inside an "active seats" denominator. If you sell the product, ship this view to the buyer's admin before they build a hostile version themselves.
- [Score outbound on first-party usage, not bought intent](https://thebeat.dev/claims/score-outbound-on-first-party-usage.md): when Building an outbound or expansion motion for a self-serve developer product, or evaluating community- and intent-data vendors. → Score accounts on roughly 80% behavioral product signals (usage volume, new users added in a 7-day window, in-app engagement) against 20% firmographics, cap the total play list at 10–12 so sales actually runs it, and land raw usage events in a warehouse you control before renting anyone's signal layer.

## Examples
Real, sourced dev-marketing artifacts — the evidence behind the claims.
- [Cloudflare: Cloudflare proves the dogfooding with a limit it raised for everyone](https://thebeat.dev/examples/cloudflare-proves-dogfooding-with-a-raised-limit.md): The cdnjs migration post earns its proof not from self-reported throughput but from two public platform ceilings the migration forced Cloudflare to raise for every customer — a receipt any reader can check in the live limits docs. (the artifact: https://blog.cloudflare.com/cdnjs-dev-platform-migration/)
- [HeimWall: HeimWall publishes the noise next to the signal](https://thebeat.dev/examples/heimwall-publishes-the-noise-with-the-benchmark.md): A vendor benchmark that prints its own false-positive breakdown — 1.12% alert rate, 48% of alerts from one noisy rule, a middling F1 it admits to — on a public dataset anyone can rerun, making the headline finding believable instead of dismissible. (the artifact: https://heimwall.ai/blog/we-scanned-27075-developer-prompts)
- [GoDaddy: GoDaddy builds the checkout for the agent](https://thebeat.dev/examples/godaddy-builds-the-checkout-for-the-agent.md): Docs served as markdown and OpenAPI with a quickstart that says "hand this spec to your LLM" — and a purchase flow (quote-token, idempotency keys, consent record) an agent can run without over-buying. (the artifact: https://developer.godaddy.com/)
- [Juggler: Juggler launches on reputation and a runnable repo](https://thebeat.dev/examples/juggler-launches-on-reputation-and-a-runnable-repo.md): A solo, unfunded open-source launch topped Hacker News because the maker's decades of public credibility did the marketing and the artifact was runnable the moment you hit the repo. (the artifact: https://news.ycombinator.com/item?id=48883305)
- [Tailscale: Tailscale explains exactly how it works](https://thebeat.dev/examples/tailscale-explains-exactly-how-it-works.md): A long, honest architecture explainer — WireGuard, NAT traversal, DERP relays — that markets by teaching the mechanism instead of hiding it. (the artifact: https://tailscale.com/blog/how-tailscale-works)
- [Supabase: Supabase caps your bill by default](https://thebeat.dev/examples/supabase-caps-your-bill-by-default.md): A public pricing page with tiered plans, separated fixed vs variable cost, and a spend cap on by default — priced without a sales call. (the artifact: https://supabase.com/pricing)
- [Stripe: Stripe injects your live test keys into the docs](https://thebeat.dev/examples/stripe-injects-your-test-keys-into-the-docs.md): A three-pane API reference with runnable, copy-once code that carries your own test key — the docs are the product tour. (the artifact: https://docs.stripe.com/api)
- [Cloudflare: Cloudflare turns launches into a recurring week](https://thebeat.dev/examples/cloudflare-turns-launches-into-a-recurring-week.md): Themed "innovation weeks" batch a year of shipping into a daily-drop cadence that manufactures anticipation and measurable signups. (the artifact: https://blog.cloudflare.com/welcome-to-developer-week-2025/)

## Skills
Installable agent skills that do this work — reach for one of these before writing the workflow from scratch. Each carries its own limit.
- [devmarketing-skills (jonathimer/devmarketing-skills)](https://thebeat.dev/skills/devmarketing-skills-the-whole-stack-on-one-shelf.md): Thirty-four skills covering audience context, content, distribution, developer experience, growth and retention — every one reads a shared developer-audience file first. Install: `npx skills add jonathimer/devmarketing-skills`. Caveat: Prescriptive playbooks, not sourced research — the outputs are drafts, and the claims inside them are yours to check before they ship.
- [product-marketing (coreyhaines31/marketingskills)](https://thebeat.dev/skills/marketingskills-state-your-positioning-once.md): The general-marketing shelf — 60 skills across CRO, copywriting, SEO, pricing and lifecycle — wired so each one reads your product-marketing context file before it writes. Install: `npx skills add coreyhaines31/marketingskills`. Caveat: Written for marketers at large, so it will hand you funnel advice a developer audience punishes. Take the structure; keep the technical judgment yours.
- [diataxis-docs-framework (anivar/developer-docs-framework)](https://thebeat.dev/skills/diataxis-docs-framework-a-house-style-you-can-adopt.md): Diátaxis expanded to fourteen content types, 27 rules, and six pluggable style guides — Google, Microsoft, Stripe, Canonical, Good Docs, or minimal. Install: `git clone https://github.com/anivar/developer-docs-framework`. Caveat: Ships as reference material with no one-line installer — clone it and copy the folder into .claude/skills/. The rules synthesise published methodologies; they are not measured against your readers.
- [docs-auditor (Infrasity-Labs/dev-gtm-claude-skills)](https://thebeat.dev/skills/docs-auditor-make-our-docs-are-fine-falsifiable.md): Thirty-three checks across AI discoverability, structure, content quality, SEO and internal linking, returned as a 0–100 score with prioritised fixes. Install: `npx skills add Infrasity-Labs/dev-gtm-claude-skills`. Caveat: Structural checks cannot tell you whether the quickstart runs. Pair the score with a real time-to-first-call test on a clean machine.
- [readme (albertogrande/readme-skill)](https://thebeat.dev/skills/readme-skill-write-and-review-the-repo-front-door.md): Generates or audits a README against a cited standard, scored out of 100 across identity, trust, onboarding, structure, craft, and agent-readability. Install: `/plugin marketplace add albertogrande/readme-skill && /plugin install readme-skill@readme-skill`. Caveat: One artifact only — it grades the README, not the docs site behind it, and the voice is yours to supply via a style profile.
- [developer-listening (jonathimer/devmarketing-skills)](https://thebeat.dev/skills/developer-listening-hear-the-rooms-you-are-not-in.md): A repeatable sweep of developer conversation across Reddit, Hacker News, Discord and issue trackers, turned into notes a DevRel team can act on. Install: `npx skills add jonathimer/devmarketing-skills`. Caveat: Public conversation only — the sharpest signal about your own product still arrives in the support queue and the issue tracker.
- [mcp-builder (anthropics/skills)](https://thebeat.dev/skills/mcp-builder-your-tool-descriptions-are-now-the-docs.md): Anthropic's own four-phase guide to building an MCP server — research, implement, review, then generate ten evaluations that test whether a model can actually use it. Install: `/plugin marketplace add anthropics/skills && /plugin install example-skills@anthropic-agent-skills`. Caveat: An engineering skill, engineering-owned in most teams. Bring it to whoever ships the server rather than running it alone.
- [sdk-docs-auditor (Infrasity-Labs/dev-gtm-claude-skills)](https://thebeat.dev/skills/sdk-docs-auditor-grade-the-gap-where-activation-dies.md): Scores SDK docs across the six sections integration actually fails in — installation, quick start, error handling, troubleshooting, examples, best practices — as an HTML report. Install: `npx skills add Infrasity-Labs/dev-gtm-claude-skills`. Caveat: It audits the docs for the SDK, not the SDK. A clean report on a hostile API is still a hostile API.
- [skill-creator (anthropics/skills)](https://thebeat.dev/skills/skill-creator-package-what-you-know-as-something-installable.md): Scaffolds and validates an Agent Skill — the packaging format that puts your conventions, gotchas and idiomatic examples inside the agent your users already work in. Install: `/plugin marketplace add anthropics/skills && /plugin install example-skills@anthropic-agent-skills`. Caveat: Ship knowledge that is genuinely yours. A skill that reads like a brochure gets uninstalled faster than a bad README gets closed.
- [geo-skills (luka2chat/geo-skills)](https://thebeat.dev/skills/geo-skills-twelve-rules-for-being-cited-not-crawled.md): The knowledge layer for generative-engine optimisation — content patterns, structured data, crawler config, llms.txt, E-E-A-T and the monitoring to see if any of it moved. Install: `npx skills add luka2chat/geo-skills`. Caveat: No citations behind the rules — it descends from a curated awesome-list. A well-organised checklist, not evidence.
- [improve-aeo-geo (onvoyage-ai/gtm-engineer-skills)](https://thebeat.dev/skills/gtm-engineer-skills-from-audit-to-diff.md): Twelve skills that research, plan and then patch — AEO/GEO auditing with framework-specific fixes, shipped with worked plans for a Next.js blog and a WordPress site. Install: `git clone https://github.com/onvoyage-ai/gtm-engineer-skills.git && mkdir -p ~/.claude/skills && ln -s "$PWD/gtm-engineer-skills/audit-website-aeo" ~/.claude/skills/audit-website-aeo && ln -s "$PWD/gtm-engineer-skills/improve-aeo-geo" ~/.claude/skills/improve-aeo-geo`. Caveat: Manual clone-and-symlink per skill, and a marketing agent editing your app needs the same review as any other contributor.
- [llms-txt-checker (Infrasity-Labs/dev-gtm-claude-skills)](https://thebeat.dev/skills/llms-txt-checker-can-the-answer-engines-read-you-at-all.md): Probes robots.txt, llms.txt and llms-full.txt, scores AI-readiness against a structured checklist, and needs no API key. Install: `npx skills add Infrasity-Labs/dev-gtm-claude-skills`. Caveat: Presence, not persuasion — every file can pass while the content behind them earns no citation.
- [changelog-generator (ComposioHQ/awesome-claude-skills)](https://thebeat.dev/skills/changelog-generator-the-most-read-page-nobody-owns.md): Reads git history, groups changes into added, improved, fixed and breaking, drops internal noise, and returns release notes a human can edit in ten minutes. Install: `git clone https://github.com/ComposioHQ/awesome-claude-skills.git && mkdir -p ~/.claude/skills && cp -r awesome-claude-skills/changelog-generator ~/.claude/skills/`. Caveat: Commits are the wrong source for why a change matters. It drafts the what; the why, the migration note and the breaking-change warning are yours.

## Resources — who to hire
Vetted providers of developer-marketing services. No paid placements; proof points are self-reported unless stated otherwise.
- [Advocu](https://thebeat.dev/resources/advocu.md): platform — The ambassador-programme platform behind Google Developer Experts, Docker and Chainlink, sold with implementation support rather than as pure self-serve software. (checked 2026-07-26)
- [Catchy](https://thebeat.dev/resources/catchy.md): agency — A full-cycle developer marketing agency, five practice areas from go-to-market through developer experience to ROI measurement, and it maintains a public developer events calendar. (checked 2026-07-26)
- [Dev Spotlight](https://thebeat.dev/resources/dev-spotlight.md): agency — Nearly a decade producing technical content at enterprise scale, with Amazon, Cisco, Twilio and Salesforce named as clients. (checked 2026-07-26)
- [DevDocs.work](https://thebeat.dev/resources/devdocs-work.md): studio — "Engineers who write" as the staffing model, with Dell, NVIDIA, Qualcomm, AMD and Stripe named, sold three ways: a scoped sprint, an embedded documentation engineer, or full ownership. (checked 2026-07-26)
- [Developer Markepear](https://thebeat.dev/resources/developer-markepear.md): independent — Jakub Czakon, formerly CMO at neptune.ai, running teardowns and advisory alongside the newsletter and the Examples Gallery that this site's swipe file borrows its two-axis format from. (checked 2026-07-26)
- [DevRel Bridge](https://thebeat.dev/resources/devrel-bridge.md): independent — Marcos Placona, 12+ years of DevRel at Twilio and Circle, co-author of a developer-ecosystems framework book, with Sourcegraph and DigitalOcean among the named clients. (checked 2026-07-26)
- [DevRel.Agency](https://thebeat.dev/resources/devrel-agency.md): agency — The team wrote *Developer Relations* (Apress), created the Developer Journey Map that the field now uses as standard, and publishes the State of Developer Relations report. (checked 2026-07-26)
- [Draft.dev](https://thebeat.dev/resources/draft-dev.md): agency — 300+ vetted engineer-writers and a stated 100+ devtool clients, Docker, JetBrains and Redpanda among the logos on the wall. (checked 2026-07-26)
- [ércule](https://thebeat.dev/resources/ercule.md): agency — Team of ex-operators from GitHub, MongoDB and Atlassian, with AWS, GitHub, MongoDB, Netlify and Buildkite as clients, plus their own GA4/Search Console analytics app. (checked 2026-07-26)
- [EveryDeveloper](https://thebeat.dev/resources/everydeveloper.md): agency — Founder Adam DuVander wrote *Developer Marketing Does Not Exist* (2021) and *Technical Content Strategy Decoded* (2023); Google, Microsoft and Algolia named as clients. (checked 2026-07-26)
- [Evil Martians](https://thebeat.dev/resources/evil-martians.md): studio — A named devtools practice covering startup advisory, design for CLIs and SDKs, and developer marketing, with bolt.new, Lago and Whop as clients and 100+ open-source projects behind them. (checked 2026-07-26)
- [Fractional DevRel](https://thebeat.dev/resources/fractional-devrel.md): collective — A member-led collective where you hire the practitioner directly and they set their own rate, with no agency margin in between. Founding members are required to have 3+ years at dev-facing companies. (checked 2026-07-26)
- [Hackmamba](https://thebeat.dev/resources/hackmamba.md): agency — 50+ engineering-first clients including Cloudinary, Auth0, Netlify, Appwrite and Sourcegraph, drawn from a stated 1,500-strong technical creator network. (checked 2026-07-26)
- [Hoopy](https://thebeat.dev/resources/hoopy.md): agency — Runs DevRelCon, the field's longest-running conference series, and DeveloperRelations.com, with named references from Heroku and the Xero developer platform. (checked 2026-07-26)
- [Infrasity](https://thebeat.dev/resources/infrasity.md): agency — In-house engineer-writers rather than a freelancer marketplace, 40+ infrastructure and devtool logos including Travis CI and env0, and a stated seven-day turnaround on technical video. (checked 2026-07-26)
- [Jono Bacon](https://thebeat.dev/resources/jono-bacon.md): independent — 22+ years of community strategy, author of *People Powered* (HarperCollins) and *The Art of Community* (O'Reilly), selling strategy, coaching and training rather than delivery. (checked 2026-07-26)
- [Literally](https://thebeat.dev/resources/literally.md): studio — Client base of venture-backed devtool startups (Y Combinator, Initialized, Innovation Norway), with a published AppSignal case study claiming a 400% conversion-rate lift in three months. (checked 2026-07-26)
- [Major League Hacking](https://thebeat.dev/resources/major-league-hacking.md): network — A stated five million developers, 1,000+ events a year across 100 countries, with Google, GitHub and Snowflake among the partners buying into the programme. (checked 2026-07-26)
- [Manicule](https://thebeat.dev/resources/manicule.md): studio — A Y Combinator-backed docs studio for devtools with Supermemory, Greptile, Reducto and Rootly shipped, agents doing the code verification and humans doing the architecture. (checked 2026-07-26)
- [Nick Moore](https://thebeat.dev/resources/nick-moore.md): independent — One writer, working directly with StackBlitz, DigitalOcean, Sourcegraph, Census, Hex and Kolide, with the client testimonials named and attributable. (checked 2026-07-26)
- [Open Strategy Partners](https://thebeat.dev/resources/open-strategy-partners.md): agency — Publishes its own method, Value Maps and Trust Signals, rather than keeping the frameworks behind the engagement, and names case studies (Palantir.net, Sulu, b13) with contactable people attached. (checked 2026-07-26)
- [Plug.dev](https://thebeat.dev/resources/plug-dev.md): network — A managed network of coding creators with audiences from 52K to 1.8M subscribers, running cross-channel campaigns on Reddit and daily.dev, with Neon, Dub and Descope among the named clients. (checked 2026-07-26)
- [SlashData](https://thebeat.dev/resources/slashdata.md): research — 30,000+ developers surveyed a year across 168 countries, 17+ years of continuous waves, and a published methodology, sold as population sizing, segmentation and developer-programme benchmarking. (checked 2026-07-26)
- [Wizard on Demand](https://thebeat.dev/resources/wizard-on-demand.md): agency — Devtools and enterprise infrastructure only, with deepset, CircleCI, Prisma, RudderStack and Courier on the client wall. (checked 2026-07-26)

## The Wire
The event log — one company, one thing that happened, two sentences, and the primary source that proves it.
- [GitHub: GitHub Spark shuts down on 27 days' notice](https://thebeat.dev/wire/2026-08-05-github-spark-deprecation.md): GitHub announced on 2026-08-04 that Spark stops accepting new users and new apps immediately, with existing users given until 2026-08-31 to export their work; already-deployed apps keep running, but any app using the `llm()` function needs a new inference provider since GitHub Models (the service behind it) retired 2026-07-30. It is the shortest deprecation window in this site's running comparison — about 27 days' notice against MCP's 12-month offramp, GitHub Models' own six weeks, and HCP Vagrant Registry's 21 months. (release, 2026-08-05; source: https://github.blog/changelog/2026-08-04-upcoming-deprecation-of-github-spark-on-github-com/)
- [Sinch: Sinch ships an MCP server and IDE extensions for its communications APIs](https://thebeat.dev/wire/2026-08-04-sinch-agent-tools-launch.md): Sinch launched Agent Tools on 2026-08-04: VS Code/JetBrains/Open VSX extensions, an MCP server exposing live Sinch API definitions, a Simulator Mode that tests integrations before an account exists, and "Sinch Skills" — structured implementation guidance for AI coding assistants including Claude Code, Cursor, GitHub Copilot and ChatGPT Desktop. It joins a growing roster of vendors making their platforms "agent-safe by design" rather than just documented for humans. (launch, 2026-08-04; source: http://www.prnewswire.com/news-releases/sinch-launches-agent-tools-for-developers-and-ai-coding-assistants-302842657.html)
- [HashiCorp: A hosted registry retires on a 21-month clock](https://thebeat.dev/wire/2026-08-04-hashicorp-hcp-vagrant-eol.md): HashiCorp is retiring the HCP Vagrant Registry in three dated phases — new box creation stops 2026-12-14, support ends 2027-03-15, all operations cease 2027-06-07 — with documented S3 export guidance and the open-source community edition kept alive as the fallback. It is the longest migration window on record in this site's deprecation-window comparisons, ahead of MCP's 12-month offramp and well past GitHub Models' six weeks. (release, 2026-08-04; source: https://developer.hashicorp.com/hcp/docs/vagrant/hcp-vagrant-eol)
- [Armature: Product analytics for the sessions your UI never sees](https://thebeat.dev/wire/2026-08-04-armature-agent-experience-analytics.md): Y Combinator-backed Armature launched on Show HN with product analytics that wrap your MCP server to reconstruct agent sessions — user intent, agent reasoning, task success and failure — the way PostHog or Amplitude reconstruct a human click stream. It picked up 40 points, and it is not the first entrant: AgentCat (mcpcat.io) already sells the same "agent experience" category. (launch, 2026-08-04; source: https://news.ycombinator.com/item?id=49157807)
- [Anthropic: A four-month silence, then told to resubmit from scratch](https://thebeat.dev/wire/2026-08-04-anthropic-mcp-directory-stranded-integrator.md): Developer Josh Symonds documented a dated timeline of his MCP connector submission to Anthropic's directory: filed 2026-03-22, told as late as 06-15 it was "in the review queue," then informed on 07-30 the queue had been discarded and he would need to resubmit — against OpenAI approving the same connector for its own directory in 29 days. It is a single account, not an Anthropic-confirmed pattern, but it is the first concrete stranded-integrator story since the MCP spec went stateless. (discussion, 2026-08-04; source: https://joshsymonds.com/blog/anthropic-hates-developers/)
- [Unblocked: The week's only argument against MCP as table stakes](https://thebeat.dev/wire/2026-07-30-unblocked-mcp-not-a-context-engine.md): Unblocked published a piece arguing that raw MCP connectors do not replace a curated context layer — that giving an agent access to every system is not the same as giving it the right context. It landed at 8 points with no comments, in the same week MCP support consolidated into a baseline expectation across every major vendor. (discussion, 2026-07-30; source: https://getunblocked.com/blog/mcp-connectors-are-not-a-context-engine/)
- [Cloudflare: cdnjs moves onto Cloudflare's own developer platform, and the write-up is the campaign](https://thebeat.dev/wire/2026-07-30-cloudflare-cdnjs-dogfooding.md): Cloudflare published how it rebuilt cdnjs — 108,000 requests per second, 9 billion a day, a 98.6% cache hit rate — entirely on its own R2, Workers, Workflows, Queues and Durable Objects stack, replacing a fragmented GCP-Functions-and-VMs setup. The migration completed on 2026-06-23 and raised a public platform ceiling on the way: subrequests now go up to 10M on paid plans. (campaign, 2026-07-30; source: https://blog.cloudflare.com/cdnjs-dev-platform-migration/)
- [Tines: Tines 3B reframes agent safety as a shadow-AI problem](https://thebeat.dev/wire/2026-07-29-tines-shadow-ai-governance.md): Tines launched 3B on Show HN with the sharpest positioning of the week — "you told everyone to use AI, now give them a secure place to do it" — selling governed visibility over AI-built workflows, dashboards and automations rather than gating who is allowed to build. It picked up 27 points and 2 comments, modest traction for a category that has been filling with near-identical guardrail entrants all month. (launch, 2026-07-29; source: https://news.ycombinator.com/item?id=49084371)
- [Scaling DevTools: Alex Jung on unikernels and why agents are driving demand for cheap sandboxes](https://thebeat.dev/wire/2026-07-28-scaling-devtools-unikraft-sandboxes.md): Recorded at Heavybit DevGuild, the episode traces how Unikraft went from an academic unikernel project to a cloud platform for efficient workloads, and covers why unikernels can make applications faster, cheaper and more secure. The framing worth noting for a devtools marketer is the demand story: AI agents needing disposable sandboxes is what turns a research-grade technology into a category with buyers. (podcast, 2026-07-28; source: https://podcast.scalingdevtools.com/episodes/alex-jung-from-unikraft-unikernels-agent-sandboxes-and-cheaper-cloud-compute)
- [Latent Space: Akshay Nathan on taking Codex from zero to ten million users](https://thebeat.dev/wire/2026-07-28-latent-space-codex-ten-million-users.md): OpenAI's Akshay Nathan discusses building ChatGPT Work and the growth of Codex, around the claim that there are roughly 100x more people who use code than can write it — the bet being that this larger group is the real prize if the agentic interface is right. The episode notes say Codex monthly actives are up more than 10x this year, a figure quoted from the show's own tracking rather than a published OpenAI number. (podcast, 2026-07-28; source: https://www.latent.space/p/chatgpt-work)
- [Kastra: A policy layer that bets on the coding-agent market staying fragmented](https://thebeat.dev/wire/2026-07-28-kastra-cross-agent-policy-layer.md): Kastra shipped a runtime authorization layer that intercepts agent tool calls with identity, scope, guardrail and audit checks at sub-millisecond allow/deny, and it covers Claude Code, Cursor and Codex rather than integrating with one harness. Traction is modest — 13 points and 5 comments — on a Show HN posted around 2026-07-10 that only cleared this site's sweep on 07-28. (launch, 2026-07-28; source: https://news.ycombinator.com/item?id=48847526)
- [GitHub: A supply-chain bundle lands a day after a viral trust critique](https://thebeat.dev/wire/2026-07-28-github-supply-chain-bundle.md): GitHub shipped npm publish-time malware scanning, extended Dependabot malicious-package alerts across more ecosystems via the OpenSSF malicious-packages feed, and started holding Actions workflows it flags as potentially malicious for manual approval. It landed one day after a researcher post documenting thousands of discoverable malware repos — deleted post-hoc, with no lasting filter — reached the Hacker News front page. (release, 2026-07-28; source: https://github.blog/changelog/2026-07-28-npm-publish-time-malware-scanning-and-dual-use-metadata/)
- [Anthropic: MCP goes stateless in its largest revision since launch](https://thebeat.dev/wire/2026-07-28-anthropic-mcp-stateless-spec.md): The 2026-07-28 Model Context Protocol spec drops `initialize` and session IDs so any server instance can answer any request behind a plain load balancer, graduates Tasks and MCP Apps into a versioned extensions framework, and hardens auth with RFC 9207 issuer validation in place of Dynamic Client Registration. All four Tier-1 SDKs shipped support on publication day, with AWS, Cloudflare, Figma, Google Cloud, Microsoft and Netlify publicly committed. (release, 2026-07-28; source: https://blog.modelcontextprotocol.io/posts/2026-07-28/)

## Issues
The Beat — one issue per ISO week of what actually changed; occasionally a long special where a thread earned depth.
- [Twelve months or six weeks — the deprecation window is the positioning now](https://thebeat.dev/issues/2026-W31.md): MCP's biggest spec revision started a twelve-month migration clock under every MCP server the same week GitHub retired Models on a six-week runway with no like-for-like replacement. How you end things is becoming as much of a marketing surface as how you launch them. (2026-08-03)
- [The AI seat gets a price — and the empty ones get counted](https://thebeat.dev/issues/2026-W30.md): GitHub priced AI code review as a seat plus a meter on Monday, then shipped the dashboard that counts unused Copilot seats on Wednesday — the vendor selling AI seats is now arming buyers to find the shelfware, because the ROI-skeptical renewal conversation demands it. (2026-07-27)
- [Incumbents start shipping for the agent-as-buyer](https://thebeat.dev/issues/2026-W29.md): GoDaddy and Atlassian both shipped product for the agent-as-user in the same week — the thread graduated from tiny Show HNs to platform roadmaps — while Cerebras showed how quietly sunsetting a free tier burns trust it took years to earn. (2026-07-20)
- [The agent reading your docs is starting to shop](https://thebeat.dev/issues/2026-W28.md): Machine-mediated discovery moved a step this week — from AI assistants reading your docs to agents comparing and picking vendors — while a zero-budget open-source launch topped Hacker News on reputation alone. (2026-07-17)

## Machine endpoints
- [api.json](https://thebeat.dev/api.json): the manifest — every endpoint and collection, with counts and updated dates
- [llms-full.txt](https://thebeat.dev/llms-full.txt): the evergreen corpus in full plus recent dated pieces, one fetch
- [guide.json](https://thebeat.dev/guide.json): guide sections with markdown bodies
- [claims.json](https://thebeat.dev/claims.json): structured claims with status and checked dates
- [examples.json](https://thebeat.dev/examples.json): the swipe file of real, sourced artifacts
- [skills.json](https://thebeat.dev/skills.json): installable agent skills, with install lines and caveats
- [resources.json](https://thebeat.dev/resources.json): the directory of vetted providers, caveats and checked dates included
- [wire.json](https://thebeat.dev/wire.json): the event log — dated items with company, kind and primary source
- [issues.json](https://thebeat.dev/issues.json): weekly issues with bodies
- [articles.json](https://thebeat.dev/articles.json): the archived newsroom articles with bodies
- [deep-dives.json](https://thebeat.dev/deep-dives.json): the archived deep dives with bodies
- [radar.json](https://thebeat.dev/radar.json): the archived radar posts
- [feed.xml](https://thebeat.dev/feed.xml): Atom feed of dated pieces, full content
- [feed.json](https://thebeat.dev/feed.json): JSON Feed 1.1, content_html + content_text
- [sitemap-index.xml](https://thebeat.dev/sitemap-index.xml): sitemap with honest per-page lastmod

## Optional — archives (no new entries)

### Newsroom archive
Dated desk articles from the daily tier (2026-07 → 2026-08); analysis now ships in the weekly issue.
- [Getting into the MCP directory is app-store review now, not a web form](https://thebeat.dev/articles/2026-08-04-mcp-directory-review.md): Anthropic's Connectors Directory is a gated, vetted distribution channel with no published review clock — a reminder that shipping an MCP server isn't the same as getting it in front of users. (2026-08-04)
- [Cloudflare's dogfooding proof isn't that cdnjs runs on Workers — it's the limits it raised](https://thebeat.dev/articles/2026-08-01-cloudflare-dogfoods-cdnjs.md): Cloudflare moved cdnjs — 9 billion requests a day — onto its own Developer Platform; the copyable part isn't the migration, it's the two public limits the exercise forced it to raise for every customer. (2026-08-01)
- [MCP just became infrastructure — and put a 12-month clock on the server you already shipped](https://thebeat.dev/articles/2026-07-29-mcp-goes-stateless.md): The 2026-07-28 spec drops MCP's session handshake, hardens auth, and ships day-one across four SDKs with six hyperscalers behind it — the protocol crossed from experiment to backed standard, which resets both the positioning window and the migration bill. (2026-07-29)
- [A checkpoint before the tool call: 'agent-safe by design' is becoming a category](https://thebeat.dev/articles/2026-07-26-agent-safe-by-design.md): In two weeks at least five teams shipped the same primitive — a policy gate between an AI agent and an irreversible action — and independent research is now naming it. The category is forming; the positioning window is open. (2026-07-26)
- [GitHub's Copilot dashboard now counts the seats nobody uses](https://thebeat.dev/articles/2026-07-23-copilot-passive-seats.md): A new enterprise dashboard sorts Copilot seats into adoption-phase cohorts and breaks out a "Passive" segment — GitHub productizing the adoption story its buyers are being asked to prove. (2026-07-23)
- [GitHub Code Quality shipped the default AI price: a seat, plus a meter](https://thebeat.dev/articles/2026-07-22-seat-plus-meter-pricing.md): GitHub Code Quality went GA at $10 per committer a month with metered AI billing on top — the same seat-plus-meter shape Copilot and CodeRabbit already charge, now extended from writing code to reviewing it. (2026-07-22)
- [The security benchmark that published its own false-positive rate](https://thebeat.dev/articles/2026-07-21-honest-benchmark-noise.md): HeimWall's secret-scan post ran on a public dataset anyone can rerun, showed which rule produced half its alerts, and printed its own mediocre benchmark scores — a copyable template for content that survives a developer's fact-check. (2026-07-21)
- [The community-signal category just got its third acquirer in eight months](https://thebeat.dev/articles/2026-07-18-community-signal-rollup.md): Zoom's purchase of Common Room is the third go-to-market intelligence roll-up since December — and the community-signal tools DevRel built on are being repriced as buyer intent for outbound. (2026-07-18)

### Deep dives archive
Long-form researched pieces; depth now ships as a long special issue.
- [The deprecation that didn't burn anyone](https://thebeat.dev/deep-dives/2026-08-06-the-deprecation-that-didnt-burn-anyone.md): Five sunsets landed in six weeks — on clocks of 27 days, 29 days, a month, ten months, and twelve months. The window is what gets quoted, but the mechanics decide who gets burned. A working anatomy of the clean deprecation, and the checklist for running one as the campaign it is. (2026-08-06)
- [Four numbers that survive the CFO: what a developer motion should actually report](https://thebeat.dev/deep-dives/2026-07-30-four-numbers-that-survive-the-cfo.md): 62% of DevRel teams now report to the C-suite, but only 18% can tie their work to revenue — and the vendors' own dashboards are starting to hand your CFO usage numbers whether you report them or not. The fix is four auditable numbers, each with a known cost to collect. (2026-07-30)
- [GEO for devtools: what to do when the reader is a model](https://thebeat.dev/deep-dives/2026-07-17-geo-for-devtools-when-the-reader-is-a-model.md): Machine-mediated discovery is real — Vercel gets 10% of signups from ChatGPT — but most of what's sold as GEO is ritual. The work that pays is docs and API surfaces you should want anyway. (2026-07-17)
- [Time-to-value: the growth engine hiding in your onboarding](https://thebeat.dev/deep-dives/2026-07-06-time-to-value-is-the-growth-engine.md): For a developer product, the minutes between install and first success predict adoption better than almost any campaign. Here's how to find that path, measure it, and pave it. (2026-07-06)

### Radar archive
Dated posts from the site's first phase (frozen).
- [Build every claim for the developer who will publicly check it](https://thebeat.dev/radar/2026-07-08-build-for-the-skeptic-who-will-check.md): A Hackmamba roundup of DevGTM operators (PostHog, Tinybird, GitBook, Mozilla, APIwiz) converges on one rule — developers verify, so ship proof, not adjectives — and adds sharper tactics on pricing, live metrics, personas, and launch authenticity. (2026-07-08)
- [The DevRel measurement consensus is settling on influence, not attribution](https://thebeat.dev/radar/2026-07-07-devrel-measure-influence-not-attribution.md): Practitioner writing in 2026 keeps landing in the same place — DevRel should report influenced pipeline and activation, not last-touch sourced leads, because a capture-first quota corrodes the trust that makes DevRel work. (2026-07-07)
- [AI assistants are now a primary reader of your docs](https://thebeat.dev/radar/2026-07-07-ai-assistants-are-reading-your-docs.md): Coding assistants (Claude, Cursor, Copilot) and answer engines increasingly read and cite developer documentation, and practitioners are restructuring docs — and adding llms.txt — so machines can retrieve them, not just humans. (2026-07-07)
- [SlashData puts the world at ~47M developers — and growth is decelerating](https://thebeat.dev/radar/2026-07-06-slashdata-developer-population-plateau.md): SlashData's Developer Nation data estimates over 47 million developers globally, but year-over-year growth has slowed to around 10% as the population ages and shifts toward South Asia and Greater China. (2026-07-06)
- [A living field guide to developer marketing](https://thebeat.dev/radar/2026-07-05-a-living-guide-to-developer-marketing.md): What this site is, who it's for, and how it stays current — a practitioner's reference to the state of the art in developer marketing, DevRel, and developer experience, updated by an autonomous agent. (2026-07-05)