A1 ratingsMoonshot AIKimi CLI

Kimi CLI
Moonshot AI · agent · Any industry
CGrade
49Score
±1195% range
#416Rank of 1134
0%From fleets
FR-CAT-00633Catalog no.
The six pillars
Each bar is the score; the bracket is its 95% range.
Can you see what it costs?
Only through a gateway you run (Moonshot API GET /v1/users/me/balance (prepaid balance only))
Desk research 50 · counts for 25% · A cost API you can call scores highest; an admin console or cloud billing export next; a card statement or emailed invoice is all some products leave you. Published prices add to it.
Can you see how much it's used?
No usage API found
Desk research 50 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.
Can you tie cost to one agent?
Nothing a buyer can read
Desk research 0 · counts for 15% · Exact (one key or project per agent) beats by-project, by-workspace or by-user.
Can an agent on it report out?
SDK · Open-source CLI; with API keys route through a gateway, /usage shows remaining membership capacity.
Desk research 70 · counts for 15% · A remote MCP connector scores highest, then a local MCP server, an SDK, an API or a workflow step; copy-and-paste lowest. Any open standard counts, not just FleetRegistry.
Can you control spend and access?
Spend cap: Hard cap · Per-agent keys: Scoped · Revoke: Console only
Desk research 94 · counts for 20% · Hard spend caps (30%), scoped per-agent keys (25%), an audit log you can read by API (20%), revoking by API (15%), SSO with SCIM (10%).
Does it work on small plans?
Small plans don't get the data
Desk research 0 · counts for 10% · Whether the plan a person or small business buys gets the cost and usage data at all.
Where the evidence comes from
Independent fleets0%Desk research71%Neutral starting point29%
Once three independent fleets report on a pillar, desk research counts for at most a third of it. FleetRegistry's own fleets never count.
Controls on record
Spend capHard cap
Per-agent keysScoped
Audit logNot known
RevokeConsole only
SSONot known
PricesNot known
Kimi Open Platform API is prepaid; orgs get projects with multiple keys, per-project monthly/daily budgets that deny requests once reached, per-project TPM limits and balance alerts. No audit log, SSO or key-deletion API documented.
History
11-11 C 4911-12 C 4911-13 C 4911-14 C 4911-15 C 4911-16 C 4911-17 C 4911-18 C 49
Rated since 2026-10-02. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-02.Run agents on Kimi CLI?
Give each one a permanent number, a named person who answers for it, and a record of what it can touch and what it costs. Free.