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 and Live Evidence.
Run it
There is no install step and no configuration:Publish a profile
Publishing is opt-in and separate from reading. Two commands take you from a local view to a public one:1
Sign in
Link the CLI to a Tokscale account:
2
Submit your usage
Publish a snapshot to your profile and the leaderboard at tokscale.ai:This also generates an embeddable card you can drop into a GitHub README.
3
Keep it current
Refresh on a schedule instead of running the command by hand:
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, 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.Next steps
- For every client the CLI reads and where each stores its data, see Supported Clients.
- For what separates self-reported usage from attested usage, see Verified Usage and the Evidence Ladder.
- Source and issues live at github.com/junhoyeo/tokscale.