Tokscale
Start Now
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.

Start BuildingView Leaderboard
Proudly built onGIWA

The proof loop

AI usage becomes proof.
Proof becomes opportunity.

Four layers — pay, prove, carry, earn. Each one turns the last one's output into something worth more.

  1. 01

    Tokscale Gateway

    Drop into the coding agents and AI apps your team already uses — OpenAI, Anthropic, Vercel AI SDK, and more. Every request is paid on-chain via x402 and written to an immutable ledger, so usage stops being self-reported.

  2. 02

    Verified Usage

    Every completed 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.

  3. 03

    Builder Passport

    Verified usage accrues into a portable work history: tokens, active days, and per-model skill signals, backed by signed receipts. A published wallet can separately show its current Dojang status.

  4. 04

    EarnPhase 2

    GIWA ecosystem projects can post bounties by integrating with the Tokscale API, and verified builders can apply using their Builder Passport.

The stack

Gateway, payments, passport.

The gateway produces the evidence. The passport makes it portable. Earn turns it into opportunity.

Glass gateway structure on black

Tokscale Gateway

One endpoint for your AI traffic. Metered, paid, and recorded at the terminal boundary.

Frosted glass payment coin embossed with the GIWA mark

Pay per request with x402

HTTP 402 ported to GIWA with a self-hosted facilitator and canonical Permit2 proxies — deployed and source-verified on GIWA Sepolia.

Tokscale Builder Passport with holographic emblem

Builder Passport

Verified usage accrues into a work history you can carry, backed by signed receipts rather than a transferable token.

The missing trust layer

How one record earns its trust

Every record carries where it came from, how it was read, how far it has been verified, and the evidence to prove it — without exposing your work.

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

Turn work into access

Publish verified AI work on GIWA and let Builder Passport unlock opportunities across the onchain economy.

Builder Passport · the record

Work history you can verify.

Builder Passport is a portable record of work backed by signed gateway receipts, not a self-reported profile or transferable token. A published wallet can separately display its current Dojang observation.

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.

  1. Self-reported

    Activity published as-is, with nothing checked against it yet.

  2. Consistency-checked

    The facts hold up against the checks their own source promises.

  3. Source-verifiedPhase 2

    The provider's own records independently confirm the activity.

  4. Gateway-verified

    The gateway signed a receipt for the request as it happened, and that receipt can never be edited.

  5. Attested

    Published on-chain, where anyone can check it against the original evidence.

Glass terminal trophy on a pedestal

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.

5.6K

GitHub stars

544.4K

npm downloads

59

client integrations

Claude Code and Codex client marks Reads Claude Code, Codex, and 57 more clients.

github.com/junhoyeo/tokscale ↗

Built on GIWA

Attest the proof.
Not the claim.

Tokscale gives AI work an economic identity: x402 payments settle usage, signed receipts prove it happened, and GIWA attestations turn that proof into reputation builders can carry across launchpads, grants, and funding.

Pay for intelligencex402 on GIWAProve the workPrivate usage receiptsBuild reputationOnchain attestationsUnlock opportunityBuilder Passport
Glass cube assembled from interlocking pieces with the GIWA mark
Glass Upbit-branded bottle suspended above the section

Upbit Web3 Names

Your up.id, backed by real work.

Connect your Upbit Web3 Name to a verifiable record of AI usage.

Read More

Tokscale Verified

Make every token count.

Turn the AI usage you choose to share into verifiable developer reputation — never your prompts, your source, or your private work.

Start building View leaderboard