A1 ratingsAirOpsAirOps

AirOps

AirOps · platform · Any industry
B
BGrade
64Score
±1195% range
#179Rank of 1136
0%From fleets
FR-CAT-00490Catalog 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
64±27
Desk research 70 · 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?

REST API manages workflow executions (not clearly usage totals)
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 · Official OAuth MCP server plus Bearer-token REST API; plan gating unpublished
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: One shared key · Revoke: Console only
56±27
Desk research 58 · 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 keysOne shared key
Audit logNot known
RevokeConsole only
SSONot known
PricesNot known

Billing offers a soft (email) limit and a hard task limit that blocks Workflows and Playbooks. The API uses one unscoped workspace key that can be regenerated in settings (old key stops working immediately); no public SCIM or audit-log docs, and the pricing page's SSO row is not mapped to plans.

History

11-12 B 6411-13 B 6411-14 B 6411-15 B 6411-16 B 6411-17 B 6411-18 B 6411-19 B 64
First rated 2026-10-02 at 59 (B). Now 64. 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-11-15
2 earlier
[1][2][3] Correct
Usage API
Usage
REST API manages workflow executions (not clearly usage totals) Declared
medium confidence
2026-11-15
2 earlier
[1][2][3] Correct
Cost per agent
Per agent
By workspace Declared
medium confidence
2026-11-15
2 earlier
[1][2][3] Correct
How an agent reports out
Reports out
Remote MCP connector Declared
medium confidence
2026-11-15
2 earlier
[1][2][3] Correct
Per-agent keys
Controls
One shared key Declared
medium confidence
2026-11-15
3 earlier
[1][2][3] Correct
Revoke access
Controls
Console only Declared
medium confidence
2026-11-15
1 earlier
[1][2][3] Correct
Spend cap
Controls
Hard cap Declared
medium confidence
2026-11-15
4 earlier
[1][2][3] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-11-15
2 earlier
[1][2][3] Correct

Prices · Solo / Pro / Enterprise by task volume (35k / 100k / custom tasks); prices not public

Notes · Tasks are consumed per workflow step; the Usage tab shows month-to-date consumption, pacing and resource-level usage, but the API (workspace Bearer key) documents no usage, task or billing endpoints. Solo overage is $0.025 per task; no plan dollar prices published.

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

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.