API Monetization for SaaS

In the agentic era, the most valuable SaaS companies won't be products. They'll be platforms. Agents don't care about your UX. They call APIs and MCP endpoints. And if you don't offer them, they scrape your data at scale through their computer use skills. In the SaaS era, the UX layer was the moat. Customers lived in your interface. Switching costs were muscle memory and training. That moat is evaporating. When your primary user is an agent, the value shifts to what's underneath — your data, your workflows, and your integrations. The most important strategic move for SaaS companies right now is to go headless. Expose your data and workflows through APIs and endpoints. Make programmatic access a first-class experience. Trying to block agents from accessing your data is like Prohibition. It doesn't work. The activity doesn't stop. It just moves underground where you get zero signal and zero revenue. Legalize it. Offer APIs, set the terms, charge for access. Now every interaction is visible, priced, and generating data that makes your platform smarter. Going headless doesn't mean opening the vault. Serve intelligence, not raw data. Rate limit bulk extraction. Automated terms prevent data aggregation. The API gives answers to queries — it doesn't export your database. Price for adoption, not margin. If your API access is cheap enough, no startup will invest the R&D to recreate your data asset from scratch. They'll just use yours. You become the default infrastructure — not because you locked anyone in, but because competing with you isn't worth the investment. Going headless turns your competitors into your customers. Everyone building agents in your domain that calls your API pays you, feeds your data moat, and generates signal about where the market is heading. You don't need to win the UX fight. You need to be the platform under every UX that does. Competition becomes distribution. Your accumulated data — transactions, workflows, domain expertise, customer patterns — is principal that took years to build. Going headless means every API call adds signal and increases learning velocity. Staying closed means those interactions happen anyway through scraping. You leak data and value and get zero signal and zero revenue. The SaaS companies that make this shift to platforms first will accumulate more signal at a higher rate. The ones that cling to their UX as the primary value layer will get steamrolled. This is a sprint. Can you turn your product into a platform faster than agentic startups and LLM providers can replicate your data moat? The window is open now but it won't stay open for long. Every day you stay closed, agents are scraping your data without paying for it and the models they feed are getting closer to not needing you at all. Your data is your moat. Your API is how you widen it.

Having founded two SaaS companies (Statista and ECDB), I've watched pricing models evolve from simple seat-based subscriptions to something far more nuanced. Today, I want to share my findings on what pricing model works for many SaaS companies, and what we’ve learned. Seat-based pricing means you buy x seats, use 70-80% actively, and everyone gets tool access. Simple. But the world has changed. Today, data flows through multiple channels, which means a seat does not reflect actual usage anymore. Data can now be accessed in various ways: 📈 Direct API integrations with BI tools 🤖 AI assistants answering ad-hoc questions 🖥️ Automated workflows pulling market data daily 🧑💻 MCPs (APIs for LLMs) enabling new use cases A single developer might automate queries for an entire organization. Ten analysts may share one dashboard but rarely log in. Why should they all pay the same? It doesn’t make sense. According to an OMR/hy study, usage-based pricing adoption in SaaS jumped from 31% to 67% in just two years. The reason? AI and automation are making per-seat models obsolete. When one employee can automate what previously required five, charging per seat doesn't reflect value delivered. The software’s true value comes from enhancing efficiency, output, or outcomes, not the headcount. That is why we at ECDB are moving to a hybrid model: platform access + consumption credits. 👇 Here's our approach: 1. Platform tiers remain - You still choose a plan based on team size and features needed. 2. Credits introduced - Each plan includes base credits for downloads and light API usage. Heavy automation requires add-on credit bundles with volume discounts. 3. Fair pricing across channels - Whether you access a data point via xls, API call, or AI query - same credit cost. No more arbitrary pricing based on how you access the data. We found that this model works best for us right now. I welcome feedback from our customers, other SaaS founders, and industry experts. Are you seeing similar shifts in your products?

𝗕𝗲𝘆𝗼𝗻𝗱 𝗦𝘂𝗯𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻𝘀: 𝗣𝗿𝗶𝗰𝗶𝗻𝗴 𝘁𝗵𝗲 𝗔𝗜 𝗔𝗴𝗲𝗻𝘁 𝗘𝗰𝗼𝗻𝗼𝗺𝘆 🚀 At #GoogleCloudNext25, we unveiled tools like ADK and A2A Protocol to fuel AI innovation: 🔹 𝗔𝗴𝗲𝗻𝘁 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗞𝗶𝘁 (𝗔𝗗𝗞): Simplifies building advanced AI agents.  🔹 𝗔𝗴𝗲𝗻𝘁𝟮𝗔𝗴𝗲𝗻𝘁 (𝗔𝟮𝗔) 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹: Enables cross-platform compatibility.  🔹 𝗔𝗴𝗲𝗻𝘁 𝗘𝗻𝗴𝗶𝗻𝗲 & 𝗔𝗜 𝗔𝗴𝗲𝗻𝘁 𝗠𝗮𝗿𝗸𝗲𝘁𝗽𝗹𝗮𝗰𝗲: Ensures reliable deployment and broad reach. These innovations make enterprise-ready AI agents more accessible than ever. But the question dominating my conversations with Google cloud partners over the last 48 hours? 𝙃𝙤𝙬 𝙙𝙤 𝙬𝙚 𝙢𝙤𝙣𝙚𝙩𝙞𝙯𝙚 𝙩𝙝𝙚𝙢? 💡 Traditional SaaS subscriptions are a start, but they often miss the full value AI agents deliver. The future lies in pricing tied to actions and results. Here are three models gaining traction: 𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻-𝗕𝗮𝘀𝗲𝗱 𝗣𝗿𝗶𝗰𝗶𝗻𝗴 ⚙️  • Charge per task for a transparent value exchange.  • Example: A travel AI charges $5 per itinerary booked, verified by customer confirmation.  • Challenge: Requires robust tracking to ensure trust. 𝗢𝘂𝘁𝗰𝗼𝗺𝗲-𝗕𝗮𝘀𝗲𝗱 𝗣𝗿𝗶𝗰𝗶𝗻𝗴 🎯  • Earn payment only when measurable goals are met, aligning incentives.  • Example: A logistics AI for a retailer earns $0.50 per mile saved on delivery routes, tracked via GPS data.  • Challenge: Customers need clear proof the agent drove the result. 𝗛𝘆𝗯𝗿𝗶𝗱 𝗣𝗿𝗶𝗰𝗶𝗻𝗴 🔄  • Blend subscriptions with variable fees for flexibility.  • Example: A weather platform charges $500/month for data access, plus $50 per hyper-local forecast delivered by an AI.  • Challenge: Balancing fixed and variable fees can complicate pricing. 𝗪𝗵𝗮𝘁’𝘀 𝗡𝗲𝘅𝘁? The best path depends on your agent’s role, audience, and measurable impact. As we refine tools for building and deploying agents, monetization will evolve too. I’m excited to see how we innovate in this space. Which option would you test first—execution-based, outcome-based, or hybrid? Share your thoughts below or DM me to swap ROI ideas! 💬 #AI #Monetization #AIAgents #Innovation #DigitalTransformation #enterprise #GoogleCloudNext25

Every SaaS company adding AI features is hitting the same wall: how do you actually charge for something when the product changes every few weeks and the cost structure is nothing like traditional software? Last week, we hosted Manny Medina (CEO of Paid) for an Office Hours session on AI credit pricing and customer success strategy. Manny works with companies on this problem every day (five to six conversations a day) and the insights were incredibly sharp. Here are 5 things from the session I'd want to know if I was figuring this out right now: 1️⃣ Transition customers to credits with a "gift," not a price increase. Don't ask existing customers to pay more on day one. Bundle free credits with their current seat, let them see the value, and then have the commercial conversation. Manny calls it the Cialdini reciprocity play — once you give them something, the door to a new pricing conversation opens naturally. 2️⃣ Separate your internal rate card from what your customer sees. Your cost-based rate card is for you. What the customer sees should be framed entirely around their value — outcomes, tasks completed, time saved. Manny pointed to Twilio and Vercel as cautionary examples of rate cards that are nightmares for customers. The best AI companies (OpenAI, Anthropic, Cursor) don't even publish theirs. 3️⃣ Price around workflows, not individual API calls or tokens. The winning approach right now is bundling agent activities into workflows that map to work a human would have done. "If I didn't do this, you'd hire someone to do it" is the clearest way to make credits feel tangible and worth paying for. 4️⃣ Credits are a bridge — outcome-based pricing is where this is heading. Manny sees this playing out in chapters: first the transition to credits, then standardization, then tying credits to outcomes. He thinks companies have a one to two year window to get ahead of this before the rest of the market catches up. If you start talking about outcomes now, you pull ahead. 5️⃣ Use credits as a growth lever, not just a billing mechanism. This was the part that surprised me most. The smartest companies are using credits to drive adoption — incentivizing off-peak usage, giving power users free credits to try new features, creating viral loops within organizations. Cursor and Lovable are doing this really well right now. Figma and Canva moved to credits seamlessly and seem to be winning. If you missed this one and want the recording, drop a comment or DM me and I'll send it over. ✌️

Most people think monetizing an API means charging directly for every API call. However, Salesforce attributes $6.6B in annual revenue without pricing its APIs separately from its main product. Meanwhile, Stripe is estimated to pull in $16B in ARR from its API. So, if you’re an API PM, you might be wondering how to best monetize your product. Here’s a breakdown of four main approaches and when to use each: 1. INDIRECT What: API calls are free (but not unrestricted). Why: It drives traffic, enhances stickiness, and boosts your brand. When to use: When your API is used for automation, integration, or by third parties building user experiences, ecosystems, and partnerships. Example: Salesforce REST API 2. SUBSCRIPTION What: Different paid plans include a set number of API calls (a quota). Why: It drives adoption with understandable, predictable pricing. When to use: Suitable for any API-as-a-Product. Example: Sendgrid Email API 3. TRANSACTIONAL What: Charging a fee and/or a percentage of revenue. Why: It’s outcome-based—the better your users do, the more you earn. When to use: When users delegate a valuable action to your API. Example: Stripe API 4. PAY-AS-YOU-GO What: Charging per successful API call, often with volume-based pricing tiers. Why: It ensures you recoup costs when usage can vary widely. When to use: When you offer valuable data or resources that users rely on. Example: Google Maps API How do you monetize your API today? Let me know in the comments ⬇️

CTOs spend years building valuable APIs. Customer data APIs. Payment processing APIs. Inventory management APIs. Then they give it away for free while competitors monetize the same capabilities. This is why technical leaders struggle to get CFO approval for infrastructure budgets. APIs sound like cost centers, not revenue drivers. But partners and developers will pay to access your APIs—if you package them as products. Most organizations can't monetize APIs because they lack the Infrastructure: - No discovery catalog. - No usage-based metering. - No self-service access. So APIs stay cost centers instead of becoming revenue drivers. Kong turns APIs into monetizable products: → Unified catalog for discovery. → Usage-based metering for billing. → Self-service developer portals. Turn what you've already built into recurring revenue. #APIMonetization #TechLeadership #ProductStrategy

With GenAI, I was flying blind on pricing. I had no real framework, no playbook, no idea how to tie value to usage - until Michael Mansard dropped his GenAI monetisation series last year. It reframed and unlocked everything for me. If GenAI disrupted SaaS pricing, Agentic AI obliterates it. You’re no longer selling access to tools; you’re selling “digital workers” - Agents that act, collaborate, and deliver outcomes. How do you price that? I’ve been waiting for Michael’s new series on monetising Agentic AI - and it's here: The COMPASS Framework, Part 1. I’ll set out a taster below, but want you to go and read the full article (link in the comments) Michael introduces a 3x3 matrix to guide pricing metric typology, based on two critical axes: 𝐒𝐜𝐨𝐩𝐞 𝐨𝐟 𝐭𝐡𝐞 𝐀𝐠𝐞𝐧𝐭’𝐬 𝐰𝐨𝐫𝐤: Is it automating tasks, orchestrating processes, or achieving strategic goals? 𝐋𝐞𝐯𝐞𝐥 𝐨𝐟 𝐯𝐚𝐥𝐮𝐞 𝐚𝐭𝐭𝐫𝐢𝐛𝐮𝐭𝐢𝐨𝐧: Can its output be clearly linked to measurable results, or is it more diffuse? From this, four pricing models emerge - building directly on archetypes introduced in Michael’s earlier 2024 GenAI monetisation research - each tailored to a different kind of Agentic behaviour: 𝐏𝐞𝐫 𝐀𝐠𝐞𝐧𝐭: Think retainers - predictable cost for always-on utility, even if value is hard to isolate. 𝐏𝐞𝐫 𝐀𝐜𝐭𝐢𝐯𝐢𝐭𝐲: Like time & materials - charging for discrete actions, API calls, or compute blocks. 𝐏𝐞𝐫 𝐎𝐮𝐭𝐩𝐮𝐭: Tangible deliverables - resolved tickets, code commits, saved checkpoints. 𝐏𝐞𝐫 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: Performance-based - pricing tied to a business KPI the agent helps deliver. Like any good framework, it’s not just descriptive - it’s prescriptive. It helps you make decisions, not just describe them. Michael doesn’t just map where we are - he forecasts where we’re going: “We're heading toward a value attribution battleground, where a single customer outcome might be achieved not by one Agent, but by a team of Agents from different vendors.” Think about it: When multiple autonomous Agents from different companies collaborate to deliver a single result - who gets credit? Who gets paid? Who owns the outcome? Each Agent may contribute differently: one gathers data, another analyses it, a third executes the action. But from the customer’s point of view, it’s one seamless result. It challenges basic assumptions of value attribution in pricing models: How do you split revenue when the outcome is co-produced? Who logs the “win”? Who invoices? Who maintains the customer relationship? It breaks traditional pricing logic - per seat, per API call, even per outcome - and demands interoperable telemetry and trust between vendors. It opens up new models: shared revenue, micro-commissions, Agent marketplaces, even arbitration layers. We’re entering a new era of multi-Agent, multi-vendor ecosystems - where telemetry becomes strategy. Michael has done it again - and provided the map we needed to navigate this. Go read it.

When customers can't translate 1,000 API calls' into cost per delivery, their finance teams start sweating. Here's how predictable pricing can become a competitive advantage: There’s a big disconnect between API calls and business metrics. API companies often use volume pricing: 0-1,000 API calls is $X per API; 1,001 - 2,500 is $X, and so on. But with this type of pricing, many companies can’t understand the real cost of APIs as a business unit they care about. Take a food delivery app. They want to know how many API calls are going to be made per order for an ETA. If they’re selling orders that average $50 for a 20% commission, they’re making $10 so maps API calls per order needs to cost them $0.50. Companies like Google Maps (and others) that offer standard API call pricing make it easy for companies to run up a massive bill without really knowing what they’ve paid for. That’s why we try to offer multiple pricing models. We do offer standard pricing, but what works better is offering slightly more conventional SaaS pricing. Here are 2 ways we do that: 1. Credit-based system with fixed pricing Customers buy credits with a certain validity so there’s no confusion. $10,000 worth of credits gives you API calls at a rate of $0.01/API call, which works out to 1M calls that the customer can decide how to use. This pricing is far easier to translate into a budget line and know exactly what you’re getting out of it. 2. Business unit pricing Using API call averages, customers can gauge the real cost of doing business with us. We try to understand the customer’s use case, leverage our experience, and give them a rough per order figure (ie. ¢5 per order or per truck) so they don’t have to worry about calculating API call usage. When your margins are low, API price predictability and avoiding surprise costs matters. NextBillion.ai takes away the guesswork. With our tool, you know what you’re going to pay upfront, the same way you would fuel costs, vehicle maintenance costs, etc.

You're a usage-based SaaS and not tracking usage in real-time? Stripe Meters API & why you should care... At Sessions this year, Stripe announced the launch of the usage-based billing with the Meters API - I could not tell you how many SaaS businesses I've spoken to that have asked if Stripe could track and automatically update usage events in real-time so that they can offer: 1. Accurate Usage-Based Billing 2. Enhanced Visibility and Transparency -- both customers and merchants increased visibility into consumption patterns and billing 3. Strategising with Flexible Pricing Models 🚀 How it works: Sarah's GPUs (its a fake company for now!) is a company that provides GPU computing resources for tasks like machine learning, rendering, and scientific simulations. They offer different tiers of GPU power, and they want to bill customers based on their actual usage rather than a fixed subscription plan. Define Meter Events: Sarah's GPUs would send meter events to Stripe whenever a customer uses their GPU resources. These events might represent the number of GPU hours used, the amount of GPU memory consumed, or any other relevant usage metric. Configure Meters: Sarah's GPUs would create meters in Stripe to define how the meter events should be aggregated over the billing period. For example, they might have a meter that sums up the total GPU hours used by each customer per month. Set up Prices: Sarah's GPUs would define prices in Stripe for their different GPU tiers. For instance, they might have a price of $0.50 per GPU hour for their entry-level tier, and $1.00 per GPU hour for their high-performance tier. Create Subscriptions: When a new customer signs up, Sarah's GPUs would create a subscription in Stripe and associate it with the appropriate price for the GPU tier the customer selected. Send Meter Events: As customers use Sarah's GPUs' resources, the company would send meter events to Stripe, representing the actual usage for each customer. Billing: At the end of each billing period (e.g., monthly), Stripe would aggregate the meter events for each customer based on the configured meters. It would then calculate the charges for each customer's subscription based on their aggregated usage and the associated prices. For example, if a customer used 100 GPU hours on the entry-level tier in a given month, their bill would be calculated as: 100 GPU hours x $0.50 per GPU hour = $50 Thanks for coming to my TED Talk! Just a passionate Stripe about automating payments instead of spending time crunching numbers. Sarah Useful links: https://lnkd.in/dSBpDdFD https://lnkd.in/dg5RmWZm https://lnkd.in/deS_Kn72 #Stripe #StripeSessions #Sessions2024 #Stripepayments #usagebasedbilling

If you’re still pricing #GenAI like SaaS, you’re not “innovating” — you’re gambling with your margins. AI-enabled business models are just emerging, but a recent article from Bessemer Venture Partners, "AI Pricing & Monetization Playbook" (in the first comment) nails the core shift: AI doesn’t monetize access; it monetizes outcomes — in a world where every token (and human-in-the-loop) has a real COGS line item. Practically speaking, start with the business model you’re really building: Copilot vs. Agent vs. AI-enabled Service → different economics, different charge metrics. Then pick a charge metric as a strategic choice (consumption → workflow → outcome): tighter value alignment means you’re taking on more cost risk. Next, use hybrid pricing (base + usage/outcome tiers) to balance predictability with upside. Finally, test value-first, then “find the price through friction” (if it’s an instant yes, it’s probably too low). Most importantly, treat pricing as your operating model: it shapes sales motions, CS incentives, what you measure, and how you scale from 10 to 1,000 customers. This resonates strongly with what I’ve been seeing in my research and in the classroom at The Wharton School: in AI-enabled business models, pricing isn’t a “packaging” decision—it’s where strategy, unit economics, and organizational design meet. #AI #GenAI #Pricing #Monetization #BusinessModels #UnitEconomics #GoToMarket #SaaS #Wharton