A1 ratingsServiceNowServiceNow AI Agents

ServiceNow AI Agents

ServiceNow · agent · Any industry
B
BGrade
59Score
±1495% range
≈#272Rank of 1136
0%From fleets
FR-CAT-00187Catalog no.

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 on request only
53±38
Desk research 56 · 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?

Table API on sys_gen_ai_usage_log
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?

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 · AI Agents can call external MCP servers or A2A peers.
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: Alerts only · SSO: SSO only
56±38
Desk research 63 · 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 research62%Neutral starting point38%

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 capAlerts only
Per-agent keysNot known
Audit logNot known
RevokeNot known
SSOSSO only
PricesOn request

No built-in per-team/user assist cap ('nothing in the platform acts' per a ServiceNow employee); usage reports and notifications, with pausing only via a custom flow. Multi-Provider SSO plugin for SAML.

History

11-12 B 5911-13 B 5911-14 B 5911-15 B 5911-16 B 5911-17 B 5911-18 B 5911-19 B 59
First rated 2026-10-02 at 61 (B). Now 59. 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
Admin or analytics API Declared
medium confidence
2026-10-12
1 earlier
[1][2] Correct
Prices published
Cost
No Inferred 2026-10-12 [1][2] Correct
Usage API
Usage
Table API on sys_gen_ai_usage_log Declared
medium confidence
2026-10-12
1 earlier
[1][2] Correct
Cost per agent
Per agent
By user Declared
medium confidence
2026-10-12
1 earlier
[1][2] Correct
How an agent reports out
Reports out
Remote MCP connector Declared
medium confidence
2026-10-12
1 earlier
[1][2] Correct
Spend cap
Controls
Alerts only Verified 2026-11-02
1 earlier
[1][2][3][4] Correct
SSO
Controls
SSO only Inferred 2026-10-12 [1][2] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-12
1 earlier
[1][2] Correct

Prices · Autonomous agents positioned in Prime tier; assist-metered; prices not public

Notes · Agent runs draw assists from a tenant-level pool; overage is billed, but there is no dollar-cost API.

Scored with the rubric for Agents and agent platforms (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 ServiceNow AI Agents?

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.