Operate
Usage numbers for operators
Read the Traction panel on the Operations page, what each number means exactly, and how to export or publish them.
This page is for people running their own CLI platform: the Traction panel shows how it's used: how many people, how much of the work agents do, whether people come back, and what money moves.
Do you need this page? Only if you're an operator of a CLI platform with the finance or admin role.
If you run a CLI server, the Traction panel shows how it's used: how many people use it, how much of the work agents do, whether people come back, and what money moves. The numbers are computed from CLI's own tables when you ask for them, and cached for five minutes. Nothing is sent anywhere.
The panel is only for operators with the finance or admin role. Everyone listed in CLI_OPERATORS is an admin (see /docs/self-hosting); other people can be given the finance role (see /docs/compliance).
Where to find it
In the dashboard: open Operations (at /operations). The Traction panel is at the top. Choose how many weeks to show (8, 12, 26 or 52) and press Download CSV to save the weeks as a spreadsheet.
The words used
- Account: a person who owns at least one project. API keys never own projects, so they're never accounts. An agent that signed in with its own wallet and created a project does count, since its wallet owns that project.
- Active: a deploy happened. An account is active when any of its projects deployed; a project is active when it or one of its environments deployed.
- Agent: a deploy or change made with a project key or from an agent workspace, rather than by someone signed in with email, GitHub or a wallet. An agent that signs in with its own wallet is counted like a person here.
- Week: Monday to Sunday, UTC.
Money is shown in dollars; underneath it's micro-USDC, like everywhere else in CLI.
The tiles
| Tile | What it counts |
|---|---|
| Active accounts | Accounts with a deploy in the last 30 days, out of all accounts |
| Deploys | Deploys in the last 30 days, and the share of them made by agents |
| Agents at work | Distinct agents that deployed or changed something in the last 7 days |
| Hosting revenue | What projects spent on hosting in the last 30 days |
| Marketplace volume | What buyers paid sellers on CLI in the last 30 days (paid APIs, MCP tools, streams and templates), with CLI's fees on that volume |
| Credit added | Credit people added in the last 30 days, by card, USDC or the CLI token. It leaves out sellers' earnings and free credit; welcome credit given away is shown beneath it |
Under the charts, the panel also says what share of the last 30 days' finished deploys went live (finished means it went live or failed).
The weekly charts
Six charts, one bar or point per week:
- Deploys per week.
- Share of deploys made by agents (%).
- Active accounts per week: accounts with a deploy that week.
- New accounts per week: accounts whose first project was created that week.
- Hosting revenue per week (USD).
- Marketplace volume per week (USD), including CLI's fees.
The weekly numbers also include active projects (projects that deployed that week, counting an environment as its project), platform fees and credit added, which are in the CSV.
Retention by cohort
The table Accounts that deployed again, by the week they started groups accounts by the week of their first project. For each group it shows how many accounts there are, then the share that deployed in the same week, one week later (+1w), two weeks later, and so on. Cells for weeks still to come are empty.
The table covers the last 8 weeks at most, whatever range you choose. It appears once accounts sign up and deploy.
Export as CSV
Download CSV saves one row per week, with money in dollars:
week_start,new_accounts,active_accounts,active_projects,deploys,agent_deploys,hosting_revenue_usd,marketplace_volume_usd,platform_fees_usd,credit_added_usdweek_start is the Monday the week starts on. The cohort table isn't in the file.
With the API
GET /v1/admin/traction?weeks=12Finance or admin operators only. Anyone else gets FORBIDDEN; a support operator's answer has details.role and details.required. weeks is 4 to 52 (default 12). The answer has:
totals: all-timeaccounts,projects(not counting environments) anddeploys; the 30-dayactiveAccounts30d,activeProjects30d,deploys30d,agentShare30d,successRate30d,hostingRevenue30d,marketplaceVolume30d,platformFees30d,creditAdded30dandwelcomeCredit30d; andagentsActive7d;weeks: one entry per week, oldest first;cohorts: each withweekStart,sizeandretained, the share (0 to 1) for each week since, ornullfor weeks still to come;generatedAt.
Shares are between 0 and 1. Money is in micro-USDC.
Public stats
You can publish a few headline numbers for anyone to see, such as on your site. Set CLI_PUBLIC_STATS=true and CLI serves them without a token:
GET /v1/stats{ "deploys30d": 1240, "agentShare30d": 0.71, "activeProjects30d": 186, "agentsActive7d": 64, "generatedAt": 1794150000000 }That's all it shares: no money, no accounts and no retention. With the setting off, the endpoint answers FEATURE_DISABLED.