A1 ratingsZhipu AIZ.ai Chat

Z.ai Chat

Zhipu AI · assistant · Any industry Provisional
D
DGrade
37Score
±2095% range
≈#743Rank of 1136
0%From fleets
FR-CAT-00135Catalog no.
Provisional: the range is wide because some facts are thin or not yet known. It narrows as research and fleets fill in.

The six pillars

Each bar is the score; the bracket is its 95% range.

Can you see what it costs?

Only your card statement
38±38
Desk research 25 · 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
25±38
Desk research 0 · 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
25±38
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?

Chat product has no API; the separate Z.ai model API and Coding Plan include Web Search/Reader MCP tools but no billing endpoint.
50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · 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?

50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · 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
25±38
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 research33%Neutral starting point68%

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

Being researched now. Spend caps, per-agent keys, audit logs, revoking and SSO land here as the research writes them.

History

11-12 D 3711-13 D 3711-14 D 3711-15 D 3711-16 D 3711-17 D 3711-18 D 3711-19 D 37
Rated since 2026-10-02. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-02.

Every fact, with its rung and source

Each fact stands on its own source and its own rung of the evidence ladder (Rule N2.1). Verified Observed Declared Inferred. The weakest fact in a pillar sets its weight.

FactValueRungCheckedSources
How a buyer sees cost
Cost
Only your card statement Inferred 2026-11-01
2 earlier
[1][2][3] Correct
Usage API
Usage
None found Inferred 2026-11-01
2 earlier
[1][2][3] Correct
Cost per agent
Per agent
None found Inferred 2026-11-01
2 earlier
[1][2][3] Correct
Small plans get the data
Small plans
No Inferred 2026-11-01
2 earlier
[1][2][3] Correct

Prices · Z.ai GLM Coding Plan Lite $18/mo (Pro/Max higher); API GLM-5.3 $1.40 in / $4.40 out per 1M tokens

Notes · Z.ai docs still do not say whether chat.z.ai is free or paid. GLM-5.3 lists $1.40/1M input, $4.40/1M output (Flash models free). Coding Plan 'starts at 18 USD per month' (Lite/Pro/Max by 5-hour and weekly credits, off-peak 50%); usage visible on the Charge Type billing page, no billing or quota API documented.

Scored with the rubric for Assistants (chat apps people buy seats for) (Rule N7.1). Each pillar blends a neutral 50, desk facts weighted by rung, and independent fleets. A1 is 85+ with fleet proof, A 70, B 55, C 40, D 25, E below. Part N of the Rules

Corrections

1 awaiting review. Accepted corrections are published in the corrections register with an FR-C number.

Run agents on Z.ai Chat?

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.