See where every session, token, and dollar goes.
TknScope gives you one place to inspect Claude Code activity, imported workflow history, cost spikes, and team-level session trends without hunting through raw transcripts.
Tracked sessions
12,480
Spend reviewed
$18.4k
Alerts acknowledged
98.2%
Workspace overview
March cost health
Spend today
$312
12% below last Tuesday
Tracked runs
186
Across 7 active workflows
Alerts
3
2 cost, 1 quality review
Recent sessions
Surface expensive runs before they disappear into logs.
claude-code-prod
Healthy
tax-analysis-batch
Needs review
support-queue
Healthy
A cleaner operating surface for AI usage and incident review.
The product is structured like a normal SaaS workspace: dashboards, session detail, alerts, imports, API keys, and role-based access.
Session replay
Open any run and inspect messages, token-level evidence, source metadata, and imported context from one view.
Built for transcript-first debugging.
Cost analytics
Break spend down by workflow, provider, or time window so expensive sessions are obvious instead of anecdotal.
Track trends before they hit the bill.
Alerts and rules
Set thresholds for spikes in usage, unexpected quality scores, and sessions that need operator review.
Make anomalies actionable.
Team controls
Invite teammates, assign roles, and keep a shared record of who reviewed what and when.
Useful when incidents become collaborative.
Historical import
Bring in existing JSON session archives to backfill reporting instead of starting from a blank dashboard.
Useful for migration and postmortems.
API key ingestion
Push telemetry into TknScope from your own agents through a simple ingest endpoint without changing your stack.
Works well for batch jobs and internal tools.
Capture real work, not synthetic metrics.
Start by installing the Claude Code hook or post directly to the ingest API. TknScope then turns that raw session flow into dashboards, filters, and review queues.
Recent activity
Claude Code hook installed
claude-code
Session ingest accepted
api/ingest
Cost delta crossed threshold
alert rule
Analyst acknowledged session
workspace activity
Expected result
Go from raw session data to something your team can operate.
Create a workspace
Invite the people who need to review usage, then generate API keys or log in with Google.
Connect a source
Use the Claude Code hook or post existing session archives and telemetry through the ingest API.
Review and respond
Filter expensive sessions, compare workflows, acknowledge alerts, and import history when needed.
Operator checklist
- 1
Confirm routing
Make sure the hook or ingest caller is posting into the right org and workflow.
- 2
Validate review paths
Use filters, compare views, and imports to confirm analysts can actually investigate what matters.
- 3
Watch costs over time
Establish a baseline before you trust alerts or pricing conversations.
Start with the hook. Expand with the API.
TknScope is already structured around the two integration paths you need first: native Claude Code capture and a straight REST ingest endpoint for everything else.
Claude Code
Best for hands-off capture
Install once, let Stop events send sessions automatically, then review transcripts and workflow groupings in the dashboard.
REST ingest
Best for custom agents and imports
Post your own message history, tokens, and metadata with an API key when you need scheduled jobs or backfills.
settings.json
POST /api/ingest
Stop guessing where the spend came from and start recording it on purpose.
TknScope is already deployed, but it needs to be used as the actual session ledger. Start with a workspace, install the hook, then let the product accumulate the history you wish you had today.