Qorx has three public-facing metric surfaces. They use the same B2C accounting language, but they do not share one counter store.
Ayie is the supported local product runtime: daemon, tray, provider routing, MCP/CLI activation, ORCL, account-backed service features, and the local resolver experience.
Primary metric source:
GET http://127.0.0.1:47187/stats
Main Ayie counters:
requestsraw_prompt_tokenscompressed_prompt_tokenssaved_prompt_tokenscontext_pack_requestscontext_indexed_tokenscontext_sent_tokenscontext_omitted_tokenscache_lookupscache_hitscache_missesprovider_cached_prompt_tokensprovider_cache_write_tokenscontext_usd_savedproxy_usd_savedprovider_cache_usd_savedtotal_estimated_usd_savedBoundary: Ayie metrics are local runtime evidence. Starter includes 5,000 Ayie/Cloud service requests, but local Community Edition commands stay unmetered.
Qorx API is the hosted account and usage surface for tenant keys, optimizer calls, resolver handles, trial keys, pricing, checkout, and usage metering.
Primary metric source:
GET /api/v1/usage
Main API counters:
eventsbillableUnitsresolverCallstokenBlocksproofPagesauditMonthsBoundary: API metrics are hosted tenant usage and plan enforcement metrics.
They do not replace the local Ayie /stats ledger.
Qorx CLI Community Edition is this AGPL source line. It is the local language/runtime/proof surface.
Main CLI metrics:
statsPrimary public proof files:
docs/benchmarks/live.json
docs/benchmarks/live.md
Boundary: CLI CE metrics are local, reproducible proof numbers. They are not provider invoice savings and they are not capped by Qorx Ayie Starter.
Use these labels when documenting or building UI:
Local savedCloud usageEstimated per-call savingsLocal proof metrics