Discussing API pricing strategy: "we charge per 1,000 calls", "freemium API model", "our enterprise tier includes...", API business model vocabulary, and communicating API value to stakeholders.
Key phrases & vocabulary
"We charge per 1,000 API calls" — standard phrasing for a metered pricing model, often written as "per 1K requests" or "per 1M tokens" for AI APIs.
"Freemium API model" — a strategy offering a free tier with limited usage to drive adoption, with paid tiers for higher volume or premium features.
"Our enterprise tier includes…" — opening for describing the additional features bundled at the top pricing tier (SLA, dedicated support, custom rate limits).
"Time to first successful API call" — a developer experience metric measuring how quickly a new developer can make their first working request.
"API business model" — the overall strategy for how an API generates revenue: direct monetization, indirect (data/ecosystem), or internal cost centre.
0 / 5 completed
1 / 5
A colleague explains: "We charge $2 per 1,000 API calls." A stakeholder asks what this means. The best explanation is:
Pricing in units of 1,000 (or 1M for AI APIs) is standard because it gives manageable numbers. "$2 per 1,000 calls" means the unit price is $0.002 per call. This is a metered, pay-per-use model: no calls = no cost; high volume = proportionally higher cost. When communicating this to non-technical stakeholders, emphasise "cost scales with usage" — this is the core value proposition of usage-based billing.
2 / 5
Your API team is discussing adopting a freemium API model. Which description best captures this strategy?
A freemium API model uses a free tier as a growth engine: it lowers the barrier to trying the API (no credit card, instant access), allows developers to build and demonstrate value internally, and creates natural upgrade pressure when free limits are hit. The critical design decision is where to set the free tier limit — generous enough to attract real users, restrictive enough that production workloads require a paid plan.
3 / 5
In a meeting, a sales engineer says: "Our enterprise tier includes a 99.99% SLA, dedicated support, and custom rate limits." What does this communicate to the enterprise buyer?
The enterprise tier sells trust and reliability at scale. Key differentiators from self-serve tiers: a Service Level Agreement (SLA) with financial penalties for downtime; dedicated support (a named account manager, faster response SLAs); custom rate limits (negotiated to match the enterprise’s traffic patterns); and often single sign-on (SSO), audit logs, and a Data Processing Agreement (DPA) for GDPR compliance.
4 / 5
An API product manager reports that "time to first successful API call" dropped from 45 minutes to 8 minutes after a documentation rewrite. Why is this metric significant?
Time to first successful API call (sometimes "time to hello world") is a critical developer experience KPI. It measures the total time from a developer discovering the API to making a working API call — covering registration, API key generation, reading docs, and writing integration code. Reducing this from 45 to 8 minutes is a significant improvement: developers experience value faster, are more likely to continue integrating, and are more likely to upgrade to a paid plan.
5 / 5
A CTO asks: "What’s our API business model?" The best answer distinguishes between which two approaches?
The fundamental distinction in API business models is direct vs. indirect monetization. Direct: developers pay for API access (Stripe, Twilio, OpenAI). Indirect: the API is free or subsidised because it creates value elsewhere — for example, Google Maps API (free at scale, drives Maps product engagement and data), or Salesforce APIs (free because they lock enterprises into the platform). A third model is internal cost centre: the API is funded by the business it enables, not by charging API consumers.