85% of x402 payments aren’t what they look like. Why ERC-8004 reputation is easy to game, and how 402Pilot helps agents decide what — and who — to pay.
// focus areas
Blockchain
EVM systems, protocol integrations, on-chain monitoring, performance, and reliability
Go development
APIs, microservices, middleware, messaging systems, and internal tooling
Machine payments
Tools, SDKs, and payment flows for machine-to-machine commerce over HTTP
Web3 engineering
Permissionless interfaces, protocol UX, and practical on-chain integrations
// projects
Self-hosted HTTP 402 paywall for any API.
A machine payments gateway that charges AI agents and humans per API call — no keys, no accounts, no subscriptions. xgateway is the Go reverse proxy that answers HTTP 402, verifies x402 and MPP (Tempo) payment proofs, settles them on-chain and forwards the request upstream; xpaywall is the full self-hosted stack around it, adding a control API for projects, routes and per-route pricing, a React admin panel, request logs, and a one-command Docker deployment.
Go SDK for the Machine Payment Protocol (MPP).
A Go SDK for MPP with core protocol types, automatic 402 payment handling, client/server flow support, Gin and Fiber middleware, and Tempo / Stripe integrations.
Permissionless Interfaces.
An open-source permissionless interfaces for DeFi protocols.
// latest posts
Where's the Money in x402: An Analysis of Coinbase's Bazaar Catalog
A full snapshot of Coinbase's x402 Bazaar — 25,443 paid resources. The real size of the agent payment market, how much popularity is faked, and what agents buy.
x402 Payment Schemes: exact, upto, and batch-settlement
How the three x402 payment schemes work: exact for fixed prices, upto for usage-based billing, and batch-settlement for high-frequency micropayments.
Get in touch
[Contact →] Questions about x402, MPP, or Go backend infrastructure — or something you are building in that space? Say hello.