SaaStr's agent answers a $240,000 API-access estimate with a $5 Postgres mirror

The charge comes from a shrinking seat count. SaaStr holds one API seat at Salesforce and says it does not need 20 or 80 ^[5]. It also says every seat-based vendor is seeing contraction because of agents ^[6]. A vendor paid per human loses revenue each time software replaces one ^[6]. So the vendor moves the bill to what the software does in volume, and for 10K that is calling the API ^[2].

At 35,000 to 40,000 calls a day, 10K makes 12.8 million to 14.6 million calls a year ^[2]. If every one were billed, $240,000 prices a call at roughly 1.6 to 1.9 cents ^[3]. That count covers every app 10K touches, so any traffic to vendors without a meter pushes the implied price on the metered calls higher. SaaStr concedes the volume grew because the calls were free: nobody charged, "so we used them like gas in a country where it costs 5 cents a gallon," it wrote ^[8]. By SaaStr's account, the same 40,000 calls a day cost almost nothing at a database such as Supabase ^[21].

10K went after that gap. Its longer-term proposal is to mirror the system of record into SaaStr's own Postgres database and call the vendors less, and it offered to set that up the same day ^[10]. SaaStr wrote that the cost is two copies of the data that must sync and will sometimes drift apart ^[11]. On the other side is a meter that, at the estimate's ceiling, comes to $20,000 a month ^[4]. "We're not a Fortune 10 company, and we're not going to pay that, or quadruple what we pay a vendor, for API access," the post said ^[7]. SaaStr does not yet know exactly what each vendor will charge ^[20].

One outcome is that buyers complain and pay. SaaStr notes that B2B price increases have mostly worked ^[13]. In its telling, Bending Spoons bought Evernote, raised the price two- or threefold and made more from the customers who stayed than it lost from those who left ^[13]. SaaStr also credits Atlassian's agent charge as one reason for Atlassian's growth ^[14].

Another is that agents cut calls to the minimum and send the rest to a mirror. That would be a slower version of SaaStr's exit from Marketo ^[12]. "I think metered pricing will get the same reaction from agents, just more slowly," SaaStr wrote ^[15].

The last is that incumbents keep their installed base and lose new purchases. "I doubt an agent would recommend any system of record that charges materially for API access," the post said ^[16]. Aurasell's CEO and CTO told SaaStr the last thing they would do is charge extra for agent access ^[17]. HubSpot's Dharmesh Shah talks often about HubSpot not charging for general agent access ^[18].

I'd expect the first and third to happen together. SaaStr says the Bending Spoons math may hold for a while with vendors it already has, and that buying new is a different decision ^[19]. If that holds, incumbents collect from existing customers and lose the next round of evaluations, where a buyer's agent drafts the shortlist. SaaStr runs on 3 humans and 21+ agents ^[1], which makes it an early and unusual buyer, and a larger company may find a same-day mirror harder to copy. For now SaaStr is not adding seats and says it will not pay the estimate. Its spend moves to a $5 database and the work of keeping it in sync ^[11]. This view is wrong if Salesforce's published price for this kind of workload comes in far below $240,000, or if SaaStr ends up paying the meter and dropping the mirror.