Cloudflare's Billable Usage API makes cost data as programmable as the cloud. A single HTTP call returns per-product Cloudflare cost data in FOCUS format for FinOps pipelines and Vantage. Cloudflare API usage transforms into dashboard cost rows. By Andres SEO Expert. Key takeaways. * Cloudflare's Billable Usage API exposes per-product cost and usage data via a single curl, aligned with FOCUS. * Native Vantage integration unifies Cloudflare spend with AWS and Azure in Cost Reports, budgets, and anomaly alerts. * Programmatic billing enables real-time cost awareness for autonomous agents, shifting FinOps from monthly reviews to live control planes. Table of contents. Cloudflare delivers single-endpoint cost data for autonomous infrastructure. Cloudflare's engineering team today detailed a new Billable Usage API that gives self-serve accounts programmatic access to per-product cost and consumption data through a single HTTP call. The move arrives as infrastructure management shifts from dashboard-driven human oversight to code-executing agents that provision, scale, and spend on their own. Finance and engineering teams no longer need manual exports or screenshots to reconcile Cloudflare spend. As Cloudflare's announcement explains, a straightforward curl command now returns structured JSON rows for every usage-based product on an account, from Workers and R2 to D1, Vectorize, and Stream. The API output is deliberately designed to mirror the FinOps Open Cost and Usage Specification (FOCUS), making immediate ingestion into multi-cloud cost toolchains a realistic default. Cloudflare also revealed a native integration with Vantage, the infrastructure cost management platform that already aggregates data from over 30 providers, so Cloudflare costs appear alongside AWS, Azure, and everything else. Inside the API's Architecture and FOCUS Foundation. A single curl for the full spend picture. The endpoint returns one row per charge period per product, with fields that directly answer the questions every FinOps workflow asks: what was consumed, in which unit, for how much, and across what timeframe. BillingCurrency, ChargePeriodStart, ChargePeriodEnd, ServiceName, PricingQuantity, ConsumedQuantity, ConsumedUnit, and ContractedCost are all present and match FOCUS column semantics exactly. Cloudflare also layers in convenience fields like CumulatedContractedCost for running totals and ZoneId/ZoneName where usage ties to a specific zone. Response data is updated daily, with a stated roadmap push toward more real-time breakdowns for products where granularity makes operational sense. FOCUS conformance as strategic signal, not yet full-blown. The adoption of FOCUS naming is not coincidental. AWS, Azure, Google Cloud, Oracle, and an expanding roster of SaaS providers already publish FOCUS-formatted exports, and every serious cost-management platform speaks that language by now. Cloudflare acknowledges the API is not yet a complete FOCUS implementation - a few spec-mandated columns are absent from the current payload - but the shape is deliberate and full conformance is on the development roadmap. This pragmatic first step ensures that teams already running FOCUS ingestion pipelines can start pulling Cloudflare data without retooling their parsers, even if a few optional fields arrive later. Vantage integration turns billing data into cross-cloud action. The Vantage partnership operationalizes the raw data stream. Through a read-only API token with Billing Read access, Vantage pulls daily Billable Usage and breaks it down by product, zone, and account inside the same unified Cost Reports, Budgets, and anomaly alerts customers already trust for other providers. Cross-provider allocation workflows allow teams to group Cloudflare spend by product or team using Virtual Tags, putting it next to AWS and Azure line items in a single view. Anomaly detection surfaces cost deviations from baseline through Slack or email, so a sudden spike in Workers or R2 consumption triggers the same alerting cadence as any other infrastructure service. The Vantage FinOps agent - queryable in-console or through its hosted MCP server from tools like Claude - can answer natural-language questions about cost drivers across every connected provider, with Cloudflare spend included. Programmatic billing reshapes FinOps and agentic economies. The Billable Usage API is not just a convenience feature - it represents a fundamental shift in the relationship between infrastructure consumption and financial control. Organizations are increasingly delegating resource creation to autonomous agents, CI/CD pipelines, and AI orchestration layers that operate far faster than human review cycles. When an agent can deploy a Worker, provision an R2 bucket, or spin up a D1 database in code, the corresponding cost awareness must also live in code, with the same latency and machine-readability. Cloudflare's team puts it plainly: if a program is spending money, you need to know what it's spending, broken down by product, throughout the day, in a shape another program can consume. For finance teams, this means the end of invoice surprises and the beginning of near-real-time cost attribution to internal projects, teams, or even end customers, directly inside their own systems. The FOCUS alignment amplifies the strategic value because it makes Cloudflare spend natively composable with other cloud cost data, enabling holistic unit economics calculations that previously required painful manual stitching. As multi-cloud architectures become the norm, the providers that expose standardized, API-first billing surfaces will reduce friction for procurement, engineering, and finance equally - and the ones that don't will face escalating operational tax on their customers. Cloudflare's move also signals where the broader market is heading: billing data as a product that must be queryable, streamable, and automation-ready, not a monthly PDF artifact. The roadmap mentions forecasting capabilities at both account and product levels, which, if executed, would transform reactive cost management into predictive spend governance for platform engineering teams. FinOps by default: the shift toward embedded cost intelligence. Cloudflare's Billable Usage API removes the last manual step from cost visibility in its self-serve ecosystem, making spend data as accessible as the services that generate it. The deliberate FOCUS header mapping and the direct Vantage connector are pragmatic bets that a standardized, programmable billing surface is more valuable than a richer but proprietary one. Enterprise coverage remains on the upcoming roadmap, but the architectural direction is already clear: every Cloudflare account will eventually have a machine-readable cost stream, whether consumed through FinOps platforms, custom scripts, or agentic workflows. That trajectory turns billing from an after-the-fact accounting concern into a live control plane - one that can gate spending, trigger alerts, and reallocate resources instantly, based on actual usage curves rather than monthly cycles. For organizations building automated infrastructure management layers, the ability to embed this data into decision loops is the difference between flying blind and flying by instruments. Andres SEO Expert helps businesses architect those same principles of programmatic visibility and automation into their digital operations. From building agentic workflows that mirror the cost-awareness Cloudflare now provides, to engineering cloud hosting environments where every resource is tracked and optimizable, the approach is always engineering-first. Its programmatic SEO and AI automation services turn repetitive data pipelines into scalable growth engines, while its managed cloud hosting solutions ensure underlying infrastructure remains cost-transparent and performant. To explore how these capabilities can drive your next phase of efficiency, reach out to Andres and discover why Andres SEO Expert LLC is built for the API-first era. Frequently asked questions. What is the Cloudflare Billable Usage API? How does the Cloudflare Billable Usage API align with FOCUS? What can you do with the Cloudflare and Vantage integration? Why is programmatic billing important for FinOps and autonomous infrastructure? What data does the Cloudflare Billable Usage API return? How often is Cloudflare billable usage data updated? August 3, 2026

Vantage launches Cloudflare self-serve support. Track Cloudflare self-serve cost and usage data across Workers, R2, and more, alongside your other providers. Vantage Team AUG 3, 2026 Today, Vantage is announcing support for Cloudflare self-serve account cost and usage data, giving customers the ability to track CDN, Workers, Zero Trust, and more directly in Vantage. Once connected, Vantage automatically ingests Cloudflare billing usage, allowing customers to monitor consumption by product family and account, set budgets, configure cost alerts, and allocate edge and security costs alongside their broader cloud infrastructure. Cloudflare is a global cloud platform that sits in front of apps, websites, and APIs to improve performance and reliability while providing security services like DDoS protection, WAF, bot mitigation, and zero-trust access. With Cloudflare supporting roughly one in five websites globally, this integration represents one of the most significant and highly anticipated additions to the Vantage platform. Previously, Vantage customers using Cloudflare relied on PDF invoices, spreadsheet exports, or the focus.vantage.sh converter to get Cloudflare costs into a usable format and into Vantage using the Custom Provider. That often made it difficult to capture real-time cost spikes and track budget performance throughout the month. Now, with the launch of Cloudflare self-serve cost support in Vantage, customers grant Vantage read access through a Cloudflare API token, and Vantage automatically ingests costs to display alongside other infrastructure providers. This helps Finance and Engineering teams understand how Cloudflare costs fit into the broader cloud spend picture. Vantage retrieves cost and usage data from Cloudflare's Billable Usage API, including costs broken down by Workers, R2 Storage, Images, and more. Customers now have visibility into which products are driving costs and have the ability to allocate these to specific teams and budgets on a daily basis. Customers who previously uploaded Cloudflare invoices through Custom Providers can move to continuous, automated ingestion without changing how they analyze costs in Vantage. The Cloudflare integration is now available to all Vantage customers with Cloudflare self-serve accounts. To connect, go to the Integrations page in account settings and select Cloudflare. You can learn more via the Cloudflare section in Vantage's documentation. Frequently asked questions. 1. What is being launched today? Vantage is launching native support for Cloudflare self-serve account cost and usage data. Customers can now connect Cloudflare through an API token, enabling automatic ingestion and visibility of Cloudflare costs in Vantage. 2. Who has access to this integration? The Cloudflare integration is available to all Vantage customers utilizing Cloudflare's self-serve subscription type. 3. When will Cloudflare Enterprise plans be available to integrate? At the time of launch, Vantage supports integrating Cloudflare self-serve accounts. As Vantage continue to partner closely with the Cloudflare team, Vantage aim to support Enterprise Cloudflare costs in the near future. 4. How much does this integration cost? There is no additional fee for using the integration. However, Cloudflare costs will be included in quota tier enforcement. If your Cloudflare costs push you over your current tier limit, you may be prompted to upgrade. See the Pricing page for details. 5. How does the integration work? Vantage uses a Cloudflare API token with Billing Read permissions to access Cloudflare's Billable Usage API. Cloudflare provides a preconfigured API token template in the API Tokens section of its platform that includes the required permissions for this integration. After you provide your Account ID and API Token through the Vantage Integration Settings page, Vantage securely retrieves cost and usage data for your self-serve Cloudflare account and refreshes it daily. Costs are then available in Vantage with breakdowns by Cloudflare product and account, and you can apply Virtual Tags to them. 6. What permissions are required to create the token on the Cloudflare side? Super Administrator permissions on the account are required to create account-owned tokens. The API token itself only requires Billing Read permissions. Vantage never creates, modifies, or deletes Cloudflare subscriptions or account settings. 7. What permissions are needed within Vantage? You must have a Vantage Owner or Integration Owner role to add or remove the Cloudflare integration. 8. What permissions does Vantage have in my Cloudflare account? The API token requires the Billing Read permission, which gives Vantage read access into billing and usage data. 9. What dimensions can Cloudflare costs be filtered and grouped by? Cloudflare reports support filtering and grouping on the following dimensions: * Account (the Cloudflare account ID, displayed using the description you set when connecting the integration) * Service (e.g., Workers, R2, Cloudflare for SaaS) * Category (the specific Cloudflare service line item) * Charge Type (e.g., Usage) * Tag (Virtual Tags created in Vantage for this provider; Cloudflare billing data does not supply native tags) 10. Are there Active Resources for Cloudflare? At this time there is no support for Active Resources for Cloudflare in Vantage. 11. How does Vantage determine the cost? Vantage utilizes Cloudflare's ContractedCost field, which specifies the cost for this charge period in the billing currency. 12. Are discounts available to toggle on and off in Cost Settings? Cloudflare cost and usage data has one Charge Type available, Usage. Toggling discounts on or off will not change the cost report. 13. How often does Cloudflare data refresh in the Vantage console? Cloudflare data refreshes daily in the Vantage console. 14. What happens if I provide an API key for non-self-serve usage? At this time the integration supports self-serve subscription types. If a different type of subscription is connected Vantage will provide a message letting you know Vantage will not attempt to import any data. Vantage will maintain that integration setup until Enterprise Plan cost data is available. 15. What happens if I remove the Cloudflare integration? If you remove your Cloudflare integration from Vantage, all associated costs will be removed from the Vantage console. 16. How far back will the data go? Vantage imports up to six months of historical Cloudflare cost data upon initial connection. Ongoing retention follows your Vantage data retention settings. 17. Can I have multiple Cloudflare account integrations? You can connect multiple Cloudflare accounts by adding a separate API token for each; every account is tracked independently within Vantage. 18. Are Recommendations available for Cloudflare costs? Get started with tracking your cloud costs.

How Make.com built AI cost observability that engineers actually use. In the second session of FinOps Summer Camp, Vantage Inc. moved from theory to practice. Vantage Team Updated JUL 31, 2026 In the second session of FinOps Summer Camp, Lukáš Pokorný (Engineering Manager) and Martin Cangár (Senior Cloud Operations Engineer) from Make.com shared how they built AI cost observability across their engineering organization using Vantage. Joining them was Vantage CEO Ben Schaechter, who added perspective on the patterns emerging across the broader industry. For Make.com, the challenge arrived quickly. As the company's internal AI usage accelerated, AI spend grew 8.7x in the first half of the year. Spreadsheets and provider-specific dashboards were no longer enough. The team needed a consistent way to understand where AI costs were coming from, who was driving them, and how to respond before costs got out of hand. Here are four lessons from their implementation. 1. Start by consolidating every AI bill. The first step wasn't optimization. It was visibility. Make.com connected Anthropic, OpenAI, Cursor, GitHub Copilot, and AWS Bedrock into Vantage to create a single view of AI spending. Native integrations eliminated the need to build and maintain custom pipelines for each provider. AWS Bedrock proved especially important. Because Bedrock usage is embedded inside an AWS invoice, it's easy for AI costs to disappear alongside infrastructure spend. Breaking it into its own cost view and budget made one of the company's fastest-growing expenses visible. You can't manage AI costs until you can see them all in one place. 2. Standardize attribution across providers. Every AI provider exposes usage data differently. Rather than reporting against five different schemas, Make.com created a single virtual tag, AI User, that maps each provider's user field into one consistent dimension. That gives engineers a simple way to understand their own AI usage while allowing leadership to roll costs up by team, department, or organization. As Ben noted during the session, consistent attribution is what makes budgeting, governance, and chargeback possible as AI adoption grows. 3. Focus on behavior, not just spend. One of Make.com's most useful metrics isn't cost at all. Cursor exposes aborted and errored requests: instances where an engineer cancels a generation because the output isn't useful. The team tracks these as a signal of AI adoption quality. A low rate suggests engineers are using AI effectively, while a higher rate points to opportunities for training and better prompting. The team also emphasized the importance of timely data. Near real-time cost updates allowed Make.com to catch a Bedrock workload that increased four to five times overnight after a feature launch. Instead of discovering the spike weeks later during invoice review, they were able to investigate immediately. 4. Put cost data where engineers already work. Dashboards only help if people use them. Rather than asking developers to check another reporting tool, Make.com surfaces individual AI budgets directly inside Backstage, the internal developer portal engineers already use every day. The company complements that visibility with internal AI education and plans to manage budgets by individual AI tool instead of a single organization-wide budget, recognizing that different models serve different workloads. The goal isn't to slow AI adoption. It's to help engineers make informed decisions about how they use it. Three takeaways for engineering teams. If you're building AI cost observability today, Make.com's advice is straightforward: * Centralize AI cost data before trying to optimize it. * Standardize attribution early, even if providers expose different metadata. * Enable alerts immediately so unexpected spend is caught before month-end. AI cost observability isn't just about tracking spend. It's about giving engineers and leadership the information they need to make better decisions as AI usage scales. What's next. The next FinOps Summer Camp session shifts from observability to control. Join Rem Baumann, Director of Product at Vantage, and Ben Schaechter for Managing AI Budgets in the Age of Tokenmaxxing, where they'll explore practical strategies for setting AI budgets that encourage responsible usage without slowing development. Thursday, August 6 at 1pm ET. Register for the rest of the series here. Get started with tracking your cloud costs.