Quote the bill, not the rate

1. Publish what a task costs beside the token rate

Anthropic shipped Claude Opus 5.5 (opens in a new tab) on Tuesday at $4 and $20 per million tokens, down from $5 and $25. A 20% cut. The sentence Anthropic wrote is a different number: “at default settings it will cost 40% less than Opus 5 on typical workloads”.

OpenAI did the same thing the same day. GPT-6 Sol and Luna (opens in a new tab) list at half the GPT-5.6 prices, and the rates are permanent (opens in a new tab). The pitch was $0.27 per task on one benchmark and “roughly 80% lower cost per task” on another.

Why did the claim move? Because the rate stopped holding still. Last week’s issue had the token price down 23% in a month. This week two vendors cut list by 20% and 50%. A rate that moves that fast cannot carry a positioning claim. A bill for a defined job can.

Am I affected? If your pricing page states a rate per token, per gigabyte or per request, yes. What replaces it? A worked task. Vercel shows it in the product: every deployment now lists its billable duration and CPU minutes (opens in a new tab) in the dashboard, in vc inspect and in the API. DigitalOcean’s Managed Agents bill per second of active CPU and say it in one line: the waits cost $0 (opens in a new tab).

The trade-off is that a bill is the number the vendor defines. “Typical workloads” is not on Anthropic’s page. A per-task figure with no task is a rate with better copy. Publish the workload with the number.

Your move:

• Put one worked example on the pricing page: what your quickstart’s first hour costs at list, with the workload written out.
• Show the bill per unit of work inside the product, per build, per run or per job, the way Vercel now does.
• When you cut a rate, say what it does to a typical bill, and define typical.

Takeaway: a rate is the vendor’s number. A bill is the buyer’s. Quote the one they will remember.

2. Say what the agent can reach, in a number

Docker rewrote its front door on Thursday. The homepage now reads “Trust Docker for the Agents You Don’t”, and the keynote (opens in a new tab) behind it shipped Cloud Sandboxes on pay-as-you-go pricing, announced Sandbox Kits, an agent, its tools and its access rules as one OCI image, and promised the spec to the CNCF.

Postman published the number that makes the fear concrete. It ran its own Passport monitor (opens in a new tab) against a coding agent on one laptop from 12 August to 9 September and counted 22 distinct secrets leaving the machine, to 18 hosts. The project’s .env held 4. One machine, Postman’s own product.

Resend made the opposite bet the same week. Its Headless Dashboard Initiative (opens in a new tab) says everything the dashboard can do should be available from the API, the CLI or MCP, and “humans and agents alike should have equal access”.

Am I affected? If a developer’s agent holds your API key, yes. Docker sells the ceiling. Resend sells the floor. Both are positioning claims written as scope, and neither is on your site today.

Your move:

• Write the reach page: what an agent with a default key can do, and what needs a scoped one, as a table with endpoint names in it.
• Make the scoped or short-lived key the default in every agent quickstart.
• Run Postman’s test on your own SDK for a week and publish the count.

Takeaway: for a human the trust claim was uptime. For an agent it is reach. Say the number before a customer measures it for you.

Quick hits

• llms.txt is opened after the pick, not before. (opens in a new tab)
  Gauge’s agent sessions opened it in 36.3% of build tasks and 0.5% of vendor-selection tasks (Gauge’s own runs, sample size unstated), so write it as a routing index for an agent already committed and keep the pitch out.
• Cloudflare made the prompt the install button. (opens in a new tab)
  Turnstile Spin’s prompt has been copied 30,000 times and produced 65,000 widgets since July (Cloudflare’s own count), so a prompt at a fixed URL is now a call to action you can count.
• Railway hands out a VM before an account. (opens in a new tab)
  ssh railway.new gives 60 minutes to build and 24 hours to claim, so the claim-later tier is still two vendors deep.
• DigitalOcean bills the agent’s waits at $0. (opens in a new tab)
  It is the third cloud in five weeks with compute built for agents, after Railway and Fly.io, and the only one with no cap.

Open questions

1. Does Docker file the Kits spec with CNCF by October 31?
   Search the CNCF sandbox applications (opens in a new tab) for “Sandbox Kit”: a filed proposal makes the neutral-governance promise checkable, and no filing leaves it Docker’s spec.
2. Does Armature publish its selection study by Oct 31?
   Its blog (opens in a new tab) lists the series as planned, and a second instrumented dataset on whether llms.txt figures in the pick either confirms Gauge’s 0.5% or kills it.