A1 ratingsKore.aiKore.ai AI for Service

Kore.ai AI for Service

Kore.ai · platform · Any industry Provisional
B
BGrade
62Score
±1695% range
≈#213Rank of 1136
0%From fleets
FR-CAT-00362Catalog 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?

Admin or analytics API · prices published
69±27
Desk research 76 · 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?

API scope 'Billing Sessions' plus LLM and Generative AI Usage Logs API
86±27
Desk research 100 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

partial
50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · 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?

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?

Per-agent keys: Scoped · Audit log: By API · Revoke: Console only · SSO: SSO only
78±27
Desk research 89 · 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 research50%Neutral starting point50%

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 capNot known
Per-agent keysScoped
Audit logBy API
RevokeConsole only
SSOSSO only
PricesPublished

Multiple JWT apps each mapped to API scopes, deleted in the Admin Console. Audit-log API exists; SAML/WS-Fed/OIDC SSO, no SCIM found. Vendor pricing page shows Essential-tier list prices; Enterprise custom.

History

11-13 B 6211-14 B 6211-15 B 6211-16 B 6211-17 B 6211-18 B 6211-19 B 6211-20 B 62
Rated since 2026-10-09. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-08.

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
Admin or analytics API Verified 2026-10-26
1 earlier
[1][2][3] Correct
Prices published
Cost
Yes Declared
medium confidence
2026-10-08
2 earlier
[1][2][3] Correct
Usage API
Usage
API scope 'Billing Sessions' plus LLM and Generative AI Usage Logs API Declared
medium confidence
2026-10-08 [1][2] Correct
Cost per agent
Per agent
partial Declared
medium confidence
2026-10-08 [1][2] Correct
Per-agent keys
Controls
Scoped Declared
medium confidence
2026-10-08
1 earlier
[1][2][3][4] Correct
Audit log
Controls
By API Declared
medium confidence
2026-10-08
1 earlier
[1][2][3][4] Correct
Revoke access
Controls
Console only Declared
medium confidence
2026-10-08
1 earlier
[1][2][3][4] Correct
SSO
Controls
SSO only Declared
medium confidence
2026-10-08
1 earlier
[1][2][3][4] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-08 [1][2] Correct

Prices · Automation AI Essential $60/mo + per-session fee (1K sessions/mo), Enterprise custom; Contact Center AI Essential $29/mo (up to 30 agents), Enterprise $79/mo; Agent AI Essential $29/mo + $0.10/session, Enterprise $79/mo

Notes · Kore.ai pricing page bills Automation AI per session (up to 15 min each) and Contact Center AI per agent seat; the Automation AI per-session figure renders ambiguously on the page. The page does not use the 'AI for Service' label; mapping these lines to AI for Service is inferred.

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 Kore.ai AI for Service?

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.