TECH Signal 475 2 feeds carried it
Introducing the Billable Usage API: programmatic cost visibility for Cloudflare
↗
Cloudflare launched a Billable Usage API that provides a single endpoint for programmatic access to cost and usage data across self-serve products, aligned with the FOCUS specification.
Engineers who automate infrastructure provisioning or run FinOps toolchains can now integrate Cloudflare cost data directly into their pipelines and dashboards, replacing manual dashboard checks. The API's FOCUS alignment means spend can be compared alongside other cloud providers in existing cost management tools, but the daily update cadence and partial FOCUS conformance limit real-time cost control and full interoperability.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The API returns usage and cost per product per charge period for all usage-based Cloudflare self-serve products in a single call.
Data is updated daily, not in real time, so cost feedback lags behind infrastructure changes.
The API uses column names from the FOCUS specification, but does not yet fully conform to that standard.
THE READ
What elseif makes of it.
Cloudflare's new Billable Usage API shifts cost visibility from a human-facing dashboard to a machine-readable endpoint. This matters because the company's Agents Week theme highlights automated agents that deploy Workers and provision infrastructure on behalf of users. If a program spends money, another program must be able to track that spend without human intervention. The API returns a JSON array with rows per product per charge period, including consumed quantity, unit, and contracted cost.
Adopting the API requires a read-only API token with Billing Read access. The data is refreshed daily, which means cost information is at least one day old. For teams that need near-real-time cost feedback, for example, to halt runaway spending by an agent, this delay is a limitation. The API also covers only usage-based products listed in the announcement, such as Workers, R2, D1, Workers AI, Vectorize, Images, and Stream. Other Cloudflare services may not appear in the response.
The API deliberately mirrors the FinOps Open Cost and Usage Specification (FOCUS) column names, such as ServiceName, ConsumedQuantity, and ContractedCost. This makes it easier to ingest Cloudflare data into existing cost management platforms that already speak FOCUS, like those used for AWS, Azure, and Google Cloud. However, Cloudflare explicitly states it is not yet fully conformant; some required FOCUS columns are missing, and full conformance is on the roadmap. Users who need strict FOCUS compliance must wait or work around the gaps.
Cloudflare also announced a partnership with Vantage, a cost management platform, to pull Billable Usage data daily and break it down by product, zone, and account. This integration supports cross-provider allocation and virtual tagging. For engineers already using Vantage, this reduces setup effort. For those using other FinOps tools, the FOCUS-aligned shape should simplify ingestion, but the daily refresh and partial conformance remain constraints.
The Hacker News feed shows the announcement is being shared, but with only one comment and five points, community reaction is minimal so far. The event is primarily a product launch, not a controversy. Engineers evaluating the API should test it against their specific usage patterns and decide whether the daily update frequency and product coverage meet their automation needs.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER