A1 ratingsDatabricksDatabricks

Databricks

Databricks · platform · Any industry
A
AGrade
71Score
±1195% range
#55Rank of 1134
0%From fleets
FR-CAT-01139Catalog no.

The six pillars

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

Can you see what it costs?

Cloud billing export (system.billing.usage (+ system.billing.list_prices)) · 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?

system.billing.usage
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 workspace
64±27
Desk research 70 · 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 · Databricks hosts managed MCP servers (Genie, AI Search, DBSQL, UC functions); agent can also query system.billing.usage via SQL/SDK.
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 · Per-agent keys: Scoped · Audit log: By API · Revoke: By API · SSO: SSO + SCIM
86±27
Desk research 100 · 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 keysScoped
Audit logBy API
RevokeBy API
SSOSSO + SCIM
PricesPublished

Account budgets can block only Unity Gateway (LLM/agent) requests, enforced approximately (near-real-time cost estimate); compute budgets stay alert-only; Genie has its own budgets with per-user block thresholds. Service principals, token permissions and Token Management API give scoped revocable identities; audit via system tables; SCIM on Premium+.

History

11-11 A 7111-12 A 7111-13 A 7111-14 A 7111-15 A 7111-16 A 7111-17 A 7111-18 A 71
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
Cloud billing export Declared
medium confidence
2026-10-21
1 earlier
[1] Correct
Prices published
Cost
Yes Declared
medium confidence
2026-10-21
1 earlier
[1][2][3][4] Correct
Usage API
Usage
system.billing.usage Declared
medium confidence
2026-10-21
1 earlier
[1] Correct
Cost per agent
Per agent
By workspace Declared
medium confidence
2026-10-21
1 earlier
[1] Correct
How an agent reports out
Reports out
Remote MCP connector Declared
medium confidence
2026-10-21
1 earlier
[1] Correct
Per-agent keys
Controls
Scoped Declared
medium confidence
2026-10-21
1 earlier
[1][2][3][4] Correct
Audit log
Controls
By API Declared
medium confidence
2026-10-21
1 earlier
[1][2][3][4] Correct
Revoke access
Controls
By API Declared
medium confidence
2026-10-21
1 earlier
[1][2][3][4] Correct
Spend cap
Controls
Hard cap Declared
medium confidence
2026-10-21
1 earlier
[1][2][3][4] Correct
SSO
Controls
SSO + SCIM Declared
medium confidence
2026-10-21
1 earlier
[1][2][3][4] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-21
1 earlier
[1] Correct

Prices · DBU-based, rate varies by SKU (not read)

Notes · Billing system table system.billing.usage is first-class; attribution via identity_metadata.run_as / owned_by (SQL warehouses) / created_by (Apps, Knowledge Assistant, Supervisor Agent) and usage_metadata IDs (job, cluster, warehouse, endpoint, app, usage_policy, Agent Bricks workload). Corrections arrive as RETRACTION/RESTATEMENT rows; data typically within 12h.

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 Databricks?

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.