A1 ratingsUnifyUnify

Unify

Unify · platform · Any industry
C
CGrade
51Score
±1195% range
#383Rank of 1134
0%From fleets
FR-CAT-00454Catalog no.

The six pillars

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

Can you see what it costs?

Only your card statement · prices published
43±27
Desk research 40 · 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
14±27
Desk research 0 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

By user
50±27
Desk research 50 · 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?

Remote MCP connector · Unify MCP (remote) consumes the same credits as Unify Chat; Open API and webhooks Business-only.
86±27
Desk research 100 · 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 · SSO: SSO only
80±27
Desk research 93 · 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
14±27
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 keysNot known
Audit logNot known
RevokeNot known
SSOSSO only
PricesPublished

The pricing page says credits are a hard cap and actions pause when the seat and pool credits run out. SAML SSO is a paid extra with no SCIM, and I found no documentation on API key scoping or revocation.

History

11-12 C 5111-13 C 5111-14 C 5111-15 C 5111-16 C 5111-17 C 5111-18 C 5111-19 C 51
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 Declared
medium confidence
2026-10-28
1 earlier
[1] Correct
Prices published
Cost
Yes Verified 2026-11-09
2 earlier
[1][2][3][4] Correct
Usage API
Usage
None found Declared
medium confidence
2026-10-28
1 earlier
[1] Correct
Cost per agent
Per agent
By user Declared
medium confidence
2026-10-28
1 earlier
[1] Correct
How an agent reports out
Reports out
Remote MCP connector Declared
medium confidence
2026-10-28
1 earlier
[1] Correct
Spend cap
Controls
Hard cap Declared
medium confidence
2026-10-28
1 earlier
[1][2] Correct
SSO
Controls
SSO only Declared
medium confidence
2026-10-28
1 earlier
[1][2] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-28
1 earlier
[1] Correct

Prices · Free (3 seats); Base $20/seat/mo (800 credits); Pro $60/seat/mo (2,400 credits); Business custom

Notes · Credit-consuming actions pause when credits run out; top-ups carry over 12 months; Open API/webhooks Business-only; SSO listed as add-on.

Scored with the rubric for Platforms and APIs (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

Run agents on Unify?

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.