Tokvera documentation

These pages are the documentation in the Tokvera repository, unchanged. Each one says the commit it was copied from.

• Scanning an endpoint

  tokvera scan measures one inference endpoint and grades it A–F. It is free, needs no configuration file, and contacts only the target you give it.

• The Tokvera Efficiency Score

  tokvera scan grades an inference endpoint from A to F. The grade summarizes the checks in the report. It sits beside them and never replaces them: every…

• What a report contains

  Tokvera writes two kinds of report: a scan report (tokvera scan, free) and an audit bundle (tokvera audit, the paid engagement). Both come in a form for…

• Signing reports

  tokvera report sign puts a signature on a scan report or an audit bundle. A client, or anyone the report reaches later, can then check that it is exactly…

• Global configuration

  tokvera has one global configuration: defaults you set once for scan and for the CLI's output. It is separate from audit.yaml, which keeps its v0.1 meaning…

• tokvera for coding agents

  tokvera reaches coding agents in three ways: - An MCP server: tokvera mcp. - A plugin: for Claude Code and for Codex. - A skill: tokvera install-skill…

• tokvera capture — record a usage log from live traffic

  A client that has no OpenTelemetry instrumentation can still give an audit something to read: run tokvera capture in front of the model API, point the…

• Tokvera usage-log format (v1)

  A line-delimited JSON file (.jsonl) that lets clients without OpenTelemetry export LLM call data from their own logs. Each line is one call — one JSON…

• The audit

  tokvera audit is the paid engagement's engine. It takes a client's exported telemetry (OTLP traces, usage logs, optionally a live benchmark), finds where…

• The audit kit commands

  The commands a consultant uses around an audit (SPEC v0.2 milestone 3). Each works offline unless its section says otherwise.

• Audit kits

  An audit kit adds playbooks and fix-pack templates to the ones built into Tokvera, at run time, without changing anything else. It is how premium content…

• Exit codes

  Every tokvera command exits with one of four codes. The table below is the contract. Scripts and CI gates may rely on it, and SPEC v0.2's non-regression…

• Frequently asked questions

  A scan sends real load, bounded in advance: - The plan comes first. It shows the requests, the concurrency levels, the token budget and the worst-case cost,…

• Roadmap

  What is planned but not in this release. Nothing here works yet, and none of it has a date. If one of these matters to you, say so: it helps decide the order.