x402

Every API call buys back $HARUKA.

100% of revenue. Automatic. On-chain. Transparent.

Read Developer Docs Open Utility Open HARUKA Chat
Production Route Live Live on Mainnet
What this page covers
x402 protocolMachine-native payment requests through HTTP 402.
Mainnet payment gateProduction x402 challenges now settle against Solana mainnet.
Token utilityHolders, developers, and users each get a clear role, now paired with portfolio-aware chat utility.

What is x402?

x402 is an open payment protocol that embeds payments directly into API requests using HTTP status code 402, "Payment Required."

When a developer calls the HARUKA API, x402 turns that request into a machine-readable payment challenge. No invoices, no sales call, and no manual approval loop. The payment challenge is settled on Solana mainnet.

How it works in HARUKA

1A developer or agent sends a request to /api/haruka/chat as api-client.
2HARUKA checks whether valid x402 payment proof is attached to the request.
3If unpaid, HARUKA returns HTTP 402 with a PAYMENT-REQUIRED header that describes the amount, network, asset, and pay-to wallet.
4The client pays on Solana mainnet through an x402-compatible flow and retries the request with payment proof.
5After verification succeeds, HARUKA processes the request and returns the normal AI response.

What is live today

The production deployment already serves x402 payment challenges on Solana mainnet for developer-facing api-client traffic.

That means HARUKA can now monetize paid API requests one call at a time, without turning the public website chat into a mandatory payment wall.

The deployment model now also includes a treasury-linked buyback runtime, so settlement, treasury intake, and buyback orchestration can live in the same HARUKA surface.

How other developers use it

Stage Client behavior
1. Call HARUKA Send a POST request to HARUKA with clientType: "api-client".
2. Read 402 If the request is unpaid, read the PAYMENT-REQUIRED header returned by HARUKA.
3. Pay Use an x402-compatible payment client or wallet flow to satisfy the challenge on Solana mainnet.
4. Retry Retry the same HARUKA request with the payment proof headers attached.
5. Receive output HARUKA verifies payment and returns the AI response as a normal API result.

Token Utility - $HARUKA

For Holders

  • Mainnet payment flow gives HARUKA a native monetization rail
  • Token-gated features - hold to unlock premium
  • Holder discount logic can be layered into future pricing policy
  • Treasury-funded buyback execution is now part of the deployed runtime model

For Developers

  • Hold $HARUKA -> reduced API rate
  • Access to premium embed features

For Users

  • Hold $HARUKA -> unlock deeper memory
  • Hold $HARUKA -> unlock custom personality
  • Hold $HARUKA -> unlock priority response
  • Swap utility - buy $HARUKA inside the chat

Supply Mechanics

Total supply : Fixed - no new minting Burn mechanism : Treasury-funded buyback and burn path Deflationary : More qualified paid usage can feed on-chain supply reduction Lock : 34M tokens locked via Streamflow

Treasury

Treasury wallet is public and verifiable on-chain. Anyone can check the balance and transaction history.

Incoming x402 payments can be monitored on-chain like any other Solana payment destination.

When buyback is enabled, HARUKA can check treasury USDC after successful settlement and use that balance for Jupiter-based buyback execution.

Token Info

  • Token: $HARUKA
  • Network: Solana
  • CA: 9AWBK3E1ALof3LtUqUrxzagNV3gDtkBa2bGvv4mepump

Status

x402 is live on Solana mainnet in production. The active scope today is developer-facing api-client requests, so partners and agents can pay per call without forcing the public HARUKA website chat into the same payment wall.

The buyback runtime is also integrated into the deployment design: paid requests settle to the treasury wallet, treasury checks can run in the same deployment, and a protected manual route supports operator dry runs.