A1 ratingsPalo Alto NetworksCortex AgentiX

Cortex AgentiX

Palo Alto Networks · platform · Any industry
D
DGrade
36Score
±1195% range
#788Rank of 1134
0%From fleets
FR-CAT-00688Catalog no.

The six pillars

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

Can you see what it costs?

Only emailed invoices
25±27
Desk research 15 · 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?

Admin API · Successor to XSOAR with a platform REST API; CU consumption only in console dashboard, no API.
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?

Spend cap: Hard cap · Per-agent keys: Scoped · Audit log: By API · Revoke: Console only · SSO: SSO only
80±27
Desk research 93 · 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
7±13
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 research73%Neutral starting point27%

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
RevokeConsole only
SSOSSO only
PricesNot known

Compute units have a configurable daily limit (default annual quota divided evenly) and queries fail without quota; consumption shown in a console dashboard. XSIAM-style API keys tied to roles with optional scope-based access and expiry; public API exposes audit logs (Premium/Enterprise). SAML 2.0 SSO with JIT; no SCIM, no key-delete endpoint documented.

History

11-12 D 3711-13 D 3711-14 D 3711-15 D 3711-16 D 3611-17 D 3611-18 D 3611-19 D 36
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
Only emailed invoices Declared
medium confidence
2026-10-20
1 earlier
[1][2] Correct
Usage API
Usage
None found Declared
medium confidence
2026-10-20
1 earlier
[1][2] Correct
Cost per agent
Per agent
None found Declared
medium confidence
2026-10-20
1 earlier
[1][2] Correct
How an agent reports out
Reports out
Admin API Declared
medium confidence
2026-10-20
1 earlier
[1][2] Correct
Per-agent keys
Controls
Scoped Declared
medium confidence
2026-10-20
1 earlier
[1][2][3][4] Correct
Audit log
Controls
By API Declared
medium confidence
2026-10-20
1 earlier
[1][2][3][4] Correct
Revoke access
Controls
Console only Declared
medium confidence
2026-10-20
1 earlier
[1][2][3][4] Correct
Spend cap
Controls
Hard cap Declared
medium confidence
2026-10-20 [1][2][3][4] Correct
SSO
Controls
SSO only Declared
medium confidence
2026-10-20
1 earlier
[1][2][3][4] Correct
Small plans get the data
Small plans
No Verified 2026-11-15
2 earlier
[1][2][3] Correct

Prices · Base: 2 users + 400 compute units/yr; Enterprise: 4 users + 800 compute units/yr; extra users/units add-on; prices quote-based

Notes · Licensed per user plus annual compute-unit allowance. CU burn (XQL queries via API; agent/LLM activity shown but not billed) is visible in a console Compute Unit Consumption dashboard with usage table and configurable daily limit; no CU usage API or export documented.

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

Corrections

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

RefFactChangeDecision
-Cost per agentnone → by_userrejected 2026-11-02

Run agents on Cortex AgentiX?

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.