Glassbox402

GlassBox402 converts APIs into an x402.

1. One npm package. x402ify turns any existing API into an x402 API in minutes. No code, and your upstream key never leaves your machine.

2. Hedera, Base and Solana. One flag picks where it settles, so there is no separate payment integration to build per chain.

3. One dashboard. Revenue across every API you have wrapped, which endpoints are called, payment and usage trends, and pricing policies, including charging humans and AI agents differently.

Machines can pay for it directly. No signup, no key, no human.

At a high level: x402ify wraps any API in an x402 paywall, the paywall streams every payment event into a hub, and the hub feeds a live dashboard. The protocol layer is the official @x402 packages rather than a reimplementation, which is what makes the whole thing chain-agnostic.

x402ify, the npm package

• A Node CLI that builds a Hono app around x402ResourceServer and HTTPFacilitatorClient
• paymentMiddleware gates every route, then the paid request is proxied upstream with the operator's key injected server-side, so the buyer never sees it
• Handles the three auth patterns real APIs use: header keys, Bearer tokens and query-param keys, plus both REST and GraphQL shapes
• Each chain is a preset of facilitator, scheme, network id and price format, so adding a network is a config entry, not a rewrite
• Published on npm, so anyone can wrap their own API today

Hedera, where it settles

• Settlement runs through the blocky402 facilitator, the textbook Hedera x402 flow
• The resource server holds no private key. The facilitator and the buyer's wallet do the signing, so an operator monetizes an API without custodying anything
• Two Hedera services, not one. The transfer moves the value, and the Hedera Consensus Service records what it was for: every settled payment writes a receipt to a public HCS topic with the lane, buyer, price and settlement transaction
• That makes the dashboard auditable instead of trusted. Read the topic off the mirror node with none of our code in the loop and it has to match the payments table row for row
• Account lazy-create means a judge connects a fresh MetaMask 0x address and their Hedera account is created by their first payment, so onboarding an EVM user is a side effect, not a step

World ID, for human versus agent pricing

• The hub verifies a Selfie Check proof once against World's v4 endpoint, then mints a short-lived HMAC session token bound to the rp-scoped nullifier
• The gateway checks that signature locally on every request, so human pricing adds zero latency per call and cannot be faked with a header
• Binding to the nullifier instead of the wallet means one human is one session, no matter how many wallets their agent rotates through

The Graph

• A real Uniswap v3 subgraph is one of the monetized APIs, at 0.02 HBAR per GraphQL query
• The repo ships an MCP server with two tools, list_paid_apis and paid_fetch, so any Claude or GPT agent becomes a paying customer of it and the payment lands on the dashboard mid-answer

The dashboard

• Frontend fed by a WebSocket event stream from the hub
• The hub aggregates analytics and appends every event to a replayable tape
• Everything is scoped to the connected wallet: a lane belongs to whoever it pays out to