Skip to main content
Tokscale Route AI. Pay per request. Prove your work. Tokscale is a verified AI gateway on GIWA: every model request a developer routes through it becomes a signed receipt, and those receipts accumulate into work history nobody can forge. The thesis behind that is proof of actual work.

​
Find your path

Gateway

How a paid request becomes a signed receipt and an anchored root.

Builder Passport

The Dojang-bound record of how you build with AI, and the evidence ladder behind it.

Usage Tracker

The open-source CLI that already reads usage from 41 coding agents.

Vision

The thesis behind proof of actual work, and the constraints we hold ourselves to.

Live evidence

What is proven on public GIWA Sepolia today, what is local, and what is Phase 2.

Glossary

Every coined term defined once, from the evidence ladder to the V1 wire identifiers.

​
AI-native work has no proof

Employers screen for AI-native skill, and the two existing signals are both broken: usage trackers are self-reported and forgeable, and résumés cannot be verified.
  • 56% AI-skill wage premium in 2025, up from 25% (PwC AI Jobs Barometer)
  • 1/3 of entry-level jobs now require AI skills, nearly triple fall 2025 (NACE)
  • 29% of developers trust AI output (Stack Overflow 2025)
And GIWA has no crypto-paid AI gateway, the infrastructure primitive OpenRouter proved at a ~$1.3B valuation.

​
One loop: usage to proof to identity to income

The gateway meters paid requests, verified usage folds into an anchored Usage Root, the Passport accrues that proof, and Earn pays it back out as more proof. Four layers, and each one consumes what the layer before it produced. For how each stage works, see The Proof Loop.

​
Why this works, and why on GIWA

Every layer maps to something that already worked at scale: OpenRouter for the multi-model gateway, x402 for per-request crypto payments, Coinbase Verifications for exchange-KYC attestation on an L2, Talent Protocol for builder identity, and Superteam Earn for bounties paid to verified builders. The adaptation is the work, not the invention. Comparables with named traction and sourcing: Five Proven Patterns. It lands on GIWA because an AI gateway needs three things on one chain, and this is the only place all three exist: Flashblocks for sub-second payment preconfirmation, Dojang for KYC-grade human identity that keeps personal data off-chain, and permissionless EAS predeploys for anchoring. In return, Tokscale ships the x402 gateway and facilitator GIWA lacks. The full argument: Why GIWA. What none of those comparables has is an un-forgeable, KYC-bound record of how developers actually work with AI.

​
What is live today

GIWA does not officially support x402, so Tokscale ported the stack and then settled a real payment on it: one ERC-3009 exact settlement of 1.0 tUSD on public GIWA Sepolia (chain ID 91342), replay-rejected by the facilitator on retry (tx 0xad1a2f7b…). The payment contracts are deployed and byte-verified. No Usage Root is anchored on the public chain yet, and the application itself has no public host.
Live Evidence is the authoritative record of what is proven on the public chain, what is proven only on a local localnet, and what is named Phase 2. If any page disagrees with it, that page is wrong.

​
Built on a live open-source base

Tokscale already ships as an open-source CLI with 4.4K GitHub stars, 268K npm downloads, and 41 client integrations, so the gateway starts with neither zero users nor zero data. That usage is self-reported and labeled that way; routing the same activity through the gateway is what makes it verifiable. See The Open-Source Base.

​
Try it

The shipped client surface is the open-source CLI. Quickstart: Track Your Usage reads the agents already on your machine and publishes a profile you control. The verified gateway is pre-release and has no public origin yet. Its end-to-end proof is a maintainer-run harness whose marker GIWA_LOCAL_E2E_OK is recorded in Verification Log, and Gateway Overview describes what that pass covers.

​
Built for GASOK

Tokscale is a submission to GASOK, the GIWA Accelerator: Track 4 AI/Web3 as the primary track, cross-applied to Track 3 GIWA-Native and Track 5 Mass Adoption.

​
Next steps

  • New here? Why GIWA covers the three primitives that make this GIWA-native rather than ported.
  • Want the mechanics? The Proof Loop walks each stage from paid request to anchored root.
  • Want to check the claims? Live Evidence separates public-chain proof from local-only proof.
  • Unfamiliar vocabulary? Every coined term is defined once in the Glossary.