Docs · API
The verified-revenue API
A read-only REST API over the same verified-revenue index you see on the board. List the verified products, pull a single signal, read the leaderboard, or take the whole thing as aggregate stats. Every response is shaped like the data on screen, because it is the data on screen.
Base URL
All endpoints are served under a single host and return JSON. The read endpoints are public; auth (below) only gates rate limits and write access, which don't exist yet.
https://launchscaler.com/api/revenueReference
Endpoints
List verified products
Every listing carrying a verified-revenue signal, joined to its listing summary. Un-verified listings are omitted. They have no figure to return.
/api/revenueQuery params
sortmrr (default) · growth · newestcategoryfilter to one category slugcountryfilter to one countrylimit1-100, default 50200 response
{
"data": [
{
"listing": {
"slug": "helioscope",
"name": "HelioScope",
"category": "analytics",
"url": "https://helioscope.app"
},
"rev": {
"slug": "helioscope",
"mrr": 24680,
"arr": 296160,
"growthPct": 5.2,
"subscribers": 1042,
"source": "dodo",
"verifiedHoursAgo": 3,
"country": "United States"
}
}
],
"count": 1,
"sort": "mrr"
}Get one revenue signal
The full verified-revenue signal for a single listing, including the 12-month MRR series and the revenue-intelligence extras. Returns 404 when the slug is un-verified or unknown.
/api/revenue/{slug}200 response
{
"slug": "helioscope",
"mrr": 24680,
"arr": 296160,
"mrrSeries": [
9120, 10430, 11890, 13020, 14700, 16050,
17720, 19340, 20910, 22140, 23510, 24680
],
"growthPct": 5.2,
"subscribers": 1042,
"source": "dodo",
"verifiedHoursAgo": 3,
"connectedAt": "2026-05-14",
"country": "United States",
"techStack": ["Next.js", "Supabase", "TypeScript"],
"channels": ["SEO", "Product Hunt"],
"domainRating": 41,
"revPerLoc": 0.82
}Read the leaderboard
The board itself: verified products ranked by MRR. The same ordering the /revenue page renders, delivered as data.
/api/revenue/leaderboardQuery params
limit1-100, default 50200 response
{
"data": [
{ "rank": 1, "slug": "helioscope", "name": "HelioScope", "mrr": 24680, "growthPct": 5.2 },
{ "rank": 2, "slug": "quartzmail", "name": "QuartzMail", "mrr": 18240, "growthPct": 11.4 },
{ "rank": 3, "slug": "deploybird", "name": "DeployBird", "mrr": 15910, "growthPct": -2.1 }
],
"count": 3
}Aggregate stats
The whole index rolled up: verified count, total and median MRR, and the breakdowns by category and country that power the /stats page.
/api/revenue/stats200 response
{
"verifiedCount": 128,
"totalMrr": 1840520,
"totalArr": 22086240,
"medianMrr": 6420,
"medianGrowthPct": 4.8,
"byCategory": [
{ "category": "analytics", "name": "Analytics", "count": 14, "totalMrr": 312400 }
],
"byCountry": [
{ "country": "United States", "count": 61, "totalMrr": 980300 }
]
}API keys
The read endpoints are open, so you can pull the board without a key. Keys will exist to lift rate limits and, later, to reach your own connected data. When they do, you'll pass one as a bearer token:
curl https://launchscaler.com/api/revenue/leaderboard \
-H "Authorization: Bearer ls_live_…"Key issuing wires in with the hosted product, alongside real payment-processor verification. Until then, the responses above are demo data.
For agents
Machine access
LaunchScaler exposes the verified-revenue index to agents, not just browsers. There are two front doors, and they point at the same data as the REST API above.
MCP server
A Model Context Protocol server surfaces the index as tools (list_revenue, get_revenue, revenue_stats) so an agent can read verified MRR the way it reads any other connected source.
llms.txt
A plain-text map of the site for language models: what LaunchScaler is, the directory, the verified-revenue index, and where the data lives. It ships today.
Read /llms.txtEvery figure a machine reads here carries the same guarantee as the badge on the board: a read-only pull from the processor charging real customers (Dodo Payments, Stripe, RevenueCat, Lemon Squeezy, Polar), refreshed regularly, shown in public. The verification bar applies to the API byte-for-byte.
Want your product in the index?
Connect a read-only processor link and your verified figure joins the board and the API.