Tokscale Gateway
One endpoint for your AI traffic. Metered, paid, and recorded at the terminal boundary.
Menu
Proof of Actual Work
Every token becomes a receipt.
Every receipt becomes reputation.
Pay per model request with x402, get a signed receipt for every call,
and turn verified usage into a Builder Passport on GIWA.
Proudly built on
The proof loop
AI usage becomes proof.
Proof becomes opportunity.
Four layers. Each one consumes the previous layer's output.
- 01
Tokscale Gateway
An OpenAI and Anthropic compatible gateway. Every request is paid on-chain via x402 and written to an immutable ledger, so usage stops being self-reported.
- 02
Verified Usage
Every terminal request gets an EIP-712 signed receipt. Once per epoch, receipts fold into a single merkle root. 1M or 100M requests. Same on-chain cost.
- 03
Builder Passport
Verified usage accrues into a portable work history: tokens, active days, and per-model skill signals, bound to a Dojang Verified Address as attestations.
- 04
EarnPhase 2
GIWA ecosystem projects post bounties for verified builders. Payouts accrue back as more proof.
The stack
Gateway, payments, passport.
The gateway is the data engine. Identity is the moat. Earn is the payoff.
Pay per request with x402
HTTP 402 ported to GIWA with a self-hosted facilitator and canonical Permit2 proxies. Credit top-up today, per-request settlement staged.
Builder Passport
Verified usage accrues into a work history you can carry. Attestations about an address, never transferable tokens.
The missing trust layer
From local logs to trusted reputation
Every record keeps its source, parser, verification level, and privacy-preserving evidence.
01Local AI usage
Collect the evidence
Capture activity from supported AI coding tools without exposing private work.
02Canonical receipt
Normalize the record
Bind tokens, cost, model, parser version, session root, and device context.
03Verification target
Prepare source checks
Preserve the evidence needed for future provider matching and challenge review.
04Network publication
Keep provenance visible
Publish local evidence on Local Anvil today without presenting it as GIWA Sepolia trust.
Dojang · the seal
Builder Passport: identity you can't buy.
Identity lives as attestations about an address, never as tokens owned by one. Non-transferable by construction, with zero PII on-chain.
Verification tiers
Not all usage
should rank the same.
Self-reported usage is forgeable. Verified usage is an asset. Tokscale separates the two so confidence, not just volume, shapes leaderboards and rewards.
Self-reported
Published activity without an independent evidence check.
Consistency-checked
Published identity and activity facts pass the checks named by their source.
Source-verified
Provider or billing records independently match the published activity.
Gateway-verified
A write-once gateway receipt records terminal observed usage.
Attested
A named network publication commits to the evidence root.
Open-source base
Not a cold start.
Tokscale already ships as an open-source CLI. That usage is self-reported and labeled that way; routing the same activity through the gateway is what makes it verifiable.
4.7K
GitHub stars
301.7K
npm downloads
42
client integrations
Reads Claude Code, Codex, and 40 more clients.
Built on GIWA
Attest the proof.
Not the claim.
A hash alone does not make usage true. Publication is Local Anvil-only today; GIWA Sepolia hosting, source verification, challenge history, and identity authority remain separate prerequisites.
Usage receiptsLocal Anvil attestationsSource matching · plannedChallenges · planned
Tokscale Verified
Make every token count.
Turn selected AI usage into verifiable developer reputation, without exposing prompts, source code, or private project content.