Skip to main content
Trophy There are two Tokscales, and knowing which one you are looking at explains most of this documentation. The first is a command-line tool that reads token usage off your own machine. It is open source, it has been shipping for months, and it is live today at tokscale.ai. The second is the verified AI gateway on GIWA that this documentation is about. It is not hosted anywhere yet. They are not competing products. The CLI is where the data starts, and the gateway is where the same data stops being forgeable.

​
What the CLI already does

Run it against your machine and it finds the coding agents you already use:
It reads usage from 41 client integrations, prices every model against LiteLLM’s pricing data, and renders the result as a native terminal UI. For the full list of clients and where each keeps its data, see Supported Clients. If you want a public profile, you submit:
That puts your usage on a leaderboard, gives you a profile page, and generates an embeddable card for your GitHub README. tokscale autosubmit enable --interval 24h keeps it current without another terminal run. This is a real distribution channel with real users, and it is the reason Tokscale on GIWA does not start from zero.

​
Why that data is forgeable by construction

The CLI measures your machine by reading files your machine wrote. Nothing about that can be trusted by a third party, and we do not ask anyone to trust it. Submitted data passes what the open-source project calls Level 1 validation: totals must add up, no negatives, no future dates, required fields present, duplicates rejected. That catches accidents and lazy tampering. It cannot catch a determined forger, because every input still originates on the machine being measured. So the CLI’s data is labeled self-reported, and validated submissions are labeled consistency-checked. Those are the bottom two rungs of the evidence ladder, and they are labeled that way in the product, not just here.

​
What the gateway changes

The gateway does not read your machine. It serves the request. When your client routes through it, the gateway observes the model, the token counts, and the price as it proxies the call, then writes that observation into an append-only ledger and signs it. Nothing in that path depends on what your machine reports about itself. The same activity that was self-reported becomes gateway-verified, and once its epoch anchors on GIWA, attested. That is the whole thesis in one sentence: the CLI proves the demand exists, and the gateway makes the resulting record worth something.

​
Two names, one product family

A few things carry different names on each side, which is worth knowing before you read further:
tokscale.ai being live is not a claim that Tokscale on GIWA is live. They are separate deployments. For what exists on the public chain today, see Live Evidence.

​
Next steps