A1 ratingsGoogle CloudTriage and Investigation Agent (TIN)

Triage and Investigation Agent (TIN)

Google Cloud · agent · Any industry Early access
-
-Grade
-Score
±1695% range
-Rank of 1136
0%From fleets
FR-CAT-00583Catalog no.
In beta or announced. A1 shows the facts but grades only released products, so early numbers never follow a product into release.

The six pillars

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

Can you see what it costs?

Only emailed invoices · prices on request only
31±38
Desk research 12 · 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?

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?

Spend cap: Hard cap · Per-agent keys: Scoped · Audit log: By API · Revoke: By API · SSO: SSO + SCIM
75±38
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 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 capHard cap
Per-agent keysScoped
Audit logBy API
RevokeBy API
SSOSSO + SCIM
PricesOn request

Price changes: GCP fees may change at any time unless fixed in an Order Form; Looker (original) 30 days

Security Tokens: paid consumption must be activated per tenant, every GA agent has built-in consumption limits, and admins can set daily consumption ceilings for paid tokens in the SecOps UI or Chronicle API; without a ceiling, exhausting purchased tokens triggers overage. Token prices are not published. IAM service accounts, Cloud Audit Logs and SAML with directory sync carried forward from Google Cloud (not re-read today).

History

11-12 - 11-13 - 11-14 - 11-15 - 11-16 - 11-17 - 11-18 - 11-19 -
Not saved yet. 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-31
1 earlier
[1][2] Correct
Prices published
Cost
No Inferred 2026-10-31
3 earlier
[1][2][3] Correct
Usage API
Usage
None found Declared
medium confidence
2026-10-31
1 earlier
[1][2] Correct
Cost per agent
Per agent
None found Declared
medium confidence
2026-10-31
1 earlier
[1][2] Correct
Per-agent keys
Controls
Scoped Inferred 2026-10-31
3 earlier
[1][2][3] Correct
Audit log
Controls
By API Inferred 2026-10-31
3 earlier
[1][2][3] Correct
Revoke access
Controls
By API Inferred 2026-10-31
3 earlier
[1][2][3] Correct
Spend cap
Controls
Hard cap Inferred 2026-10-31
3 earlier
[1][2][3] Correct
SSO
Controls
SSO + SCIM Verified 2026-11-16
4 earlier
[1][2][3][4] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-31
1 earlier
[1][2] Correct

Prices · No public price (Security Tokens add-on SKU, contract-priced; daily included tokens on Enterprise Plus/GUS)

Notes · Now called the Triage and Investigation Agent (TIN). Google SecOps Security Tokens meter GA agents only; TIN is the listed token-consuming feature. Model is Commit and Overage: a daily included allotment for Enterprise Plus/GUS (10M/20M/60M tokens by package ACV), paid annual token add-on SKU (Enterprise, Enterprise Plus, GUS; not standalone), then automatic overage. Paid consumption began Aug 31, 2026 for pre-July contracts. Usage visible in SecOps dashboards / Settings > Security Tokens; no per-token price published.

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

Run agents on Triage and Investigation Agent (TIN)?

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.