> ## Documentation Index
> Fetch the complete documentation index at: https://docs.giwa.tokscale.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart: Track Your Usage

> Read token usage from the coding agents already installed on your machine, then publish a profile you control.

The open-source Tokscale CLI is the shipped client surface. It finds the coding agents on your machine, prices what they consumed against public model pricing, and renders the result in your terminal.

<Info>
  The verified gateway described elsewhere in these docs is pre-release. It has no public origin yet, so there is nothing to point a client at today. What has been proven about it is recorded in [Verification Log](/gateway/verification-log) and [Live Evidence](/overview/live-evidence).
</Info>

## Run it

There is no install step and no configuration:

```sh theme={null}
bunx tokscale@latest
```

The same package runs under other launchers if you prefer one:

```sh theme={null}
npx tokscale@latest
deno run -A npm:tokscale@latest
```

It covers 41 client integrations and finds them by looking in the places each one already writes. For the full list and the read locations, see [Supported Clients](/usage-tracker/supported-clients).

## Publish a profile

Publishing is opt-in and separate from reading. Two commands take you from a local view to a public one:

<Steps>
  <Step title="Sign in">
    Link the CLI to a Tokscale account:

    ```sh theme={null}
    tokscale login
    ```
  </Step>

  <Step title="Submit your usage">
    Publish a snapshot to your profile and the leaderboard at [tokscale.ai](https://tokscale.ai):

    ```sh theme={null}
    tokscale submit
    ```

    This also generates an embeddable card you can drop into a GitHub README.
  </Step>

  <Step title="Keep it current">
    Refresh on a schedule instead of running the command by hand:

    ```sh theme={null}
    tokscale autosubmit enable --interval 24h
    ```
  </Step>
</Steps>

## What this data is, and is not

Usage the CLI reads is **self-reported**: it comes from files your own machine wrote, so a third party cannot verify it, and Tokscale labels it that way everywhere it appears. Submitted snapshots additionally pass consistency validation, which catches accidents rather than deliberate forgery.

That is the bottom of the [evidence ladder](/builder-passport/evidence-ladder), and it is deliberate. The gateway exists to move the same activity up to gateway-verified, because a gateway observes the request instead of reading your disk. For how the two relate, see [The Open-Source Base](/usage-tracker/open-source-base).

## Next steps

* For every client the CLI reads and where each stores its data, see [Supported Clients](/usage-tracker/supported-clients).
* For what separates self-reported usage from attested usage, see [Verified Usage and the Evidence Ladder](/builder-passport/evidence-ladder).
* Source and issues live at [github.com/junhoyeo/tokscale](https://github.com/junhoyeo/tokscale).