A1 ratingsProgress SoftwareDomo Agent Catalyst

Domo Agent Catalyst

Progress Software · platform · Any industry Provisional
C
CGrade
52Score
±1695% range
≈#375Rank of 1134
0%From fleets
FR-CAT-01370Catalog 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 (Credit Usage DomoStats dataset (Date, skuId, entityType, entityId, usageQuantity, creditsUsed, instanceId), readable via dataset API/export) · 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?

Credit Usage DomoStats dataset; Activity Log API GET /v1/audit
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?

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?

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 + SCIM
72±38
Desk research 94 · 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 research51%Neutral starting point49%

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 + SCIM
PricesOn request

API clients with least-privilege scopes, revoked by admins in the UI; Activity Log via Audit API GET /v1/audit (lookups by specified users); SCIM provisioning alongside SSO (from earlier check). Consumption terms and Credit Monitoring doc describe no credit spend cap or alert; credit rates public but price per credit is not.

History

11-12 C 5211-13 C 5211-14 C 5211-15 C 5211-16 C 5211-17 C 5211-18 C 5211-19 C 52
First rated 2026-10-06 at 54 (C). Now 52. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-05.

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-11-04
2 earlier
[1][2][3][4] Correct
Prices published
Cost
No Inferred 2026-11-04
2 earlier
[1][2][3] Correct
Usage API
Usage
Credit Usage DomoStats dataset; Activity Log API GET /v1/audit Declared
medium confidence
2026-11-04
2 earlier
[1][2][3][4] Correct
Cost per agent
Per agent
None found Declared
medium confidence
2026-11-04
1 earlier
[1][2][3][4] Correct
Per-agent keys
Controls
Scoped Inferred 2026-11-04
2 earlier
[1][2][3] Correct
Audit log
Controls
By API Inferred 2026-11-04
2 earlier
[1][2][3] Correct
Revoke access
Controls
Console only Inferred 2026-11-04
2 earlier
[1][2][3] Correct
SSO
Controls
SSO + SCIM Inferred 2026-11-04
2 earlier
[1][2][3] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-11-04
2 earlier
[1][2][3][4] Correct

Prices · Committed credits (price per credit via sales); Domo AI Pro 0.01 credits/operation (AI agent chat included from Nov 1 2026, was 0.2 credits/request); AI Pro model processing = unit price ÷ contract rate per 1M tokens; customer-provided models 0 credits

Notes · Progress Software completed its purchase of substantially all assets of Domo's AI and data platform business on Sept 22, 2026 (Domo press release); no billing change announced. Consumption terms: through Oct 31, 2026 AI agent chat cost 0.2 credits/request; from Nov 1, 2026 chat is consumed as Domo AI Pro operations at 0.01 credits/operation. Credit Usage DomoStats rows carry entityType/entityId (only 'dataset' given as example), so per-agent breakdown is not confirmed.

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 Domo Agent Catalyst?

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.