An index and topic collection covering machine-readable API and SaaS plan definitions. Plans capture the structured representation of pricing tiers, included entitlements, metered entries, add-ons, and rate plans that a provider exposes — whether as API Commons Plans YAML, OpenAPI x-plans extensions, in-band catalog APIs (Stripe Products/Prices, Lago Plans, OpenMeter Plans, Chargebee Plans, Recurly Plans, Metronome Plans, Orb Plans, Apigee Rate Plans, Zuplo Plans), or scraped pricing-page artifacts. This collection focuses on providers whose /plans/ directory is generated by the API Evangelist pipeline, treating the plan itself as a first-class machine-readable artifact distinct from the broader monetization or rate-limiting surface.
URL: https://apievangelist.com
Run: Capabilities Using Naftiko
- Pricing Plans, API Commons Plans, Subscription Tiers, Pricing Page, Plan Catalog, Rate Plans, Plan Entitlements
- Created: 2026-05-19
- Modified: 2026-05-19
- Portal
- GitHubOrganization
- JSONSchema - Pricing Plan Schema
- JSONSchema - Plan Entry Schema
- JSON-LD
- Vocabulary
| Name | Description |
|---|---|
| Machine-Readable Pricing Tiers | Plans expose subscription tiers (Free, Pro, Enterprise, Custom) as structured artifacts that downstream tooling can parse, compare, and reconcile against billing records. |
| API Commons Plans Specification | Providers can publish a normalized API Commons Plans YAML file describing plan IDs, entries, metrics, limits, time frames, and prices — the canonical machine-readable representation used across this network. |
| In-Band Plan Catalog APIs | Billing platforms such as Stripe, Chargebee, Recurly, Lago, Metronome, Orb, and Apigee expose plan and price catalogs through their own APIs, enabling programmatic synchronization of pricing into product, billing, and entitlement systems. |
| Pricing-Page Scrapers and Reconciliation | When providers do not publish in-band plan catalogs, scaffolded pricing-page scrapers extract tier and entry data from public pricing pages, then reconcile them against provider documentation to produce a verifiable plans artifact. |
| Plan Entitlements and Feature Flags | Plans declare entitlements — included features, request quotas, seat caps, retention windows, support SLAs — that platforms like Schematic and Stigg consume to drive in-product gating, packaging experiments, and trial flows. |
| Rate Plans and Metered Entries | Plans capture metered usage entries (transactions, requests, events, GB-ingested, seats) with per-unit pricing, tier breaks, and overage rules — the underlying contract for usage-based billing engines. |
| Name | Description |
|---|---|
| Pricing Page to Catalog Sync | Marketing-published pricing pages are scraped into API Commons Plans YAML, validated against the provider's catalog API, and used to keep public pricing and billed prices in lockstep. |
| Plan Comparison and Procurement | Procurement platforms like Vendr and cost tools like Infracost ingest normalized plan artifacts across vendors to compare tiers, identify overpayment, and surface negotiable line items. |
| Entitlement Enforcement in Product | Product teams use entitlement platforms like Schematic and Stigg to read plan definitions and gate features, meter usage, and present in-product upgrade prompts driven by the same artifact billing uses. |
| Usage-Based Billing Configuration | Engineering teams seed billing platforms (Lago, Metronome, Orb, Amberflo, Togai, M3ter) with plan artifacts that declare metrics, tier breaks, and commitments — replacing per-tenant pricing spreadsheets with a versioned source of truth. |
| API Marketplace Plan Tagging | API hubs and gateways (Postman, Apigee, Zuplo) tag listed APIs with the plan tiers under which they are accessible, letting consumers filter discovery by subscription level and authentication scope. |
| Pricing Governance and Audit | Finance and revenue operations use machine-readable plan artifacts to audit historical pricing changes, detect drift between the website and the billing system, and produce SOC-2-friendly pricing change logs. |
| Name | Description |
|---|---|
| Stripe | Products and Prices APIs expose subscription plans, tiered pricing, and metered components — the most widely integrated plan catalog in the SaaS billing ecosystem. |
| Lago | Open-source usage-based billing platform whose Plans API is a first-class resource for declaring subscription tiers, charges, and minimum commitments. |
| Metronome | Usage-based billing platform exposing customer plans, rate cards, and commit balances designed for high-throughput consumption pricing. |
| Orb | Billing platform whose Plans and Prices APIs model tiered, volume, package, and matrix pricing alongside metered events. |
| Schematic | Entitlements and packaging platform that consumes plan artifacts to drive in-product feature gating, paywall experiments, and pricing-page rendering. |
| Stigg | Pricing and packaging platform exposing plans, features, and entitlements as a managed catalog consumed by application code and billing systems. |
| Google Apigee | API management platform whose Rate Plans (Apigee Monetization) model entitled API products, included quotas, overage rates, and revenue share. |
| Postman | API hub that tags published APIs with subscription tiers and plan metadata for marketplace discovery and access control. |
Machine-readable plan specifications organized by format.
- Plans Vocabulary — Unified taxonomy mapping 5 resources, 7 actions, 4 workflows, and 4 personas across pricing reconciliation, entitlements, usage-based billing, and API marketplace plan tagging
This index references the following pricing-plan-publishing provider repositories:
- Stripe
- Chargebee
- Recurly
- Lago
- Metronome
- Orb
- Amberflo
- Togai
- M3ter
- Google Apigee
- Zuplo
- Schematic
- Stigg
- Twilio
- PayPal
- Braintree
- Shift4 Payments
- HubSpot
- Postman
- BigCommerce
- Vendr
- Infracost
FN: Kin Lane
Email: kin@apievangelist.com