A1 ratings11xAlice (AI SDR)

Alice (AI SDR)

11x · agent · Any industry
D
DGrade
37Score
±1495% range
≈#743Rank of 1136
0%From fleets
FR-CAT-00436Catalog no.

The six pillars

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

Can you see what it costs?

Only emailed invoices · prices published
41±38
Desk research 32 · 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?

Nothing a buyer can read
14±27
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?

HTTP step in a workflow · API access, webhooks and Slack only at Enterprise tier; no MCP found
57±27
Desk research 60 · 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?

SSO: SSO only
60±38
Desk research 70 · 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 capNot known
Per-agent keysNot known
Audit logNot known
RevokeNot known
SSOSSO only
PricesPublished

Price changes: Pricing FAQ: price increases at renewal are capped (percentage not stated); multi-year commitments lock the current rate for the term

SSO appears only at the Enterprise tier, and SCIM, audit logs and spending limits are not mentioned. Julian API keys are scoped to the organization with access to all its agents (no per-agent scoping, though agents can require per-agent request signing), and the docs don't describe revoking 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
First rated 2026-10-02 at 36 (D). Now 37. 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 emailed invoices Declared
medium confidence
2026-11-15
2 earlier
[1] Correct
Prices published
Cost
Yes Inferred 2026-11-15
3 earlier
[1][2] Correct
Usage API
Usage
None found Declared
medium confidence
2026-11-15
2 earlier
[1] Correct
Cost per agent
Per agent
None found Declared
medium confidence
2026-11-15
2 earlier
[1] Correct
How an agent reports out
Reports out
HTTP step in a workflow Declared
medium confidence
2026-11-15
2 earlier
[1] Correct
SSO
Controls
SSO only Inferred 2026-11-15
4 earlier
[1][2] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-11-15
3 earlier
[1] Correct

Prices · Growth from $36,000/yr billed annually (up to 5 users, 2,000 prospects/mo); Pro and Enterprise custom

Notes · Flat per-user/prospect bundle billed annually; no cost or usage API published, and API access is Enterprise-only. The pricing page is now consistent: the plan card, FAQ and meta description all say Growth from $36,000/yr (the earlier $3,750/mo card price is gone). Onboarding is included with no setup fee, renewal increases are capped (no percentage given) and multi-year terms lock the rate.

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

Corrections

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

RefFactChangeDecision
-How an agent reports outhttp_step → admin_apirejected 2026-11-02

Run agents on Alice (AI SDR)?

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.