Jump To Inventory Page

API Keys Meaning Layer

API key inventory should surface trust gaps, shared credential lanes, and company consequence before it behaves like a masked credential list.

Credentials are one of the clearest blast-radius surfaces in the inventory. The first read should make that consequence obvious.

Operator Brief

1 key changes the story

One unknown key is enough to reframe several sessions, files, and outbound paths above the raw inventory table.

Question This View Answers

Which credential lane matters most right now?

Keys seen

Only one is story-defining

Unknown keys

This is the main inventory trust break

Shared usage

2 lanes

One expected, one weakly explained

Immediate review value

high

Closing the key story clarifies much else

c6 List Reference

c6 shape: risk banner, count strip, map, then key-by-key ledger.

1 unknown API key

sk-ant-...C001 is not in the org allowlist and has an active session.

Keys observed

Unknown keys

Immediate review

Primary org

qpoint-dev

Live unknown spend

$0.61

Why Borrow This Shape

The meaning page should still feel like the same inventory class from c6: quick signal, recognizable topology context, then a raw ledger you can trust.

Raw API Key Inventory

Prefix, organization, sessions, spend, status, and last seen.

Key prefix	Organization	Sessions	Total cost	Status
sk-ant-...A3F2	qpoint-dev	33	$47.20	known
sk-ant-...7B91	qpoint-ci	11	$0.82	known
sk-ant-...C001	unknown	1	$0.61	unknown

Why API Keys Matter

Interpretation before the full raw catalog.

Credentials are trust surfaces first

The inventory page should say quickly whether a key is known, expected, shared, or weakly explained.

That is more useful than a masked prefix list.

A single unknown key can reframe many rows

Because credentials sit above sessions and external traffic, one trust break can explain much of the dashboard story.

This is why keys deserve meaning-first treatment.

Key detail should expose containment value

Operators should know immediately what gets clearer if the key is suspended, matched, or rotated.

That is the operational abstraction the page should add.

Priority Queue

The fastest drill paths for this entity type.

sk-ant-...C001

Unknown key with active usage and a direct alert relationship.

Open key story

Why It Matters

Fastest path to clarifying the current trust story.

Shared org key

Known but broad lane.

Open raw key list

Why It Matters

Useful baseline and blast-radius comparison.

Service key lane

Automation-only path with lower consequence.

Open service-key rows

Why It Matters

Useful to separate routine from the current unknown.

API Keys Relationship Map

Representative item showing adjacency, consequence, and next drill path.

Credential trust map

The unknown key should be shown as a trust break that widens several adjacent stories.

Use the map to connect the key to sessions, hosts, files, and outbound traffic in one operator view.

Identity, adjacency, activity, and posture around one representative item.

Trust anchors

What is missing?

allowlist matchmissing

org hintspartial context

Attached work

Where is it used?

1 active sessionflagged now

5 recent sessionsadjacent context

credential

sk-ant-...C001

Unknown owner with active usage and shared scope.

trust break

Company context

Why does it matter?

auth repo pathsensitive work

.env + configcredential-adjacent files

Boundary paths

What does it unlock?

api.anthropic.comprovider traffic

secondary hostsupporting path

trust level

low

linked sessions

containment value

high

next drill

session + file story

Representative Entity

The detail page should feel like the natural next click.

sk-ant-...C001

Use one representative api keys item to explain what a high-signal detail page should surface first.

Bridge from category significance into an evidence-backed item story.

Open detail story

Raw Evidence Paths

Keep the ledger close, but secondary.

Raw API Keys Listing

Full rows, totals, timestamps, and supporting inventory attributes.

Open raw list

Representative Raw Detail

Inspect the canonical entity page after the meaning layer narrows focus.

Open raw detail