- Protocol
- x402
- Type
- SDK
- Stars
- 70
- License
- LGPL-3.0
- Last push
- Jul 6, 2026
About Faremeter
Faremeter is an open-source x402 SDK by faremeter, written mainly in TypeScript. Framework for machine payments with pluggable x402 schemes. It has 70 GitHub stars and uses the LGPL-3.0 license, and its code was last pushed on Jul 6, 2026.
New to x402? Our x402 Protocol guide explains how it works and lists other projects built on it.
At a glance
- Protocol
- x402
- Type
- SDK
- Language
- TypeScript
- License
- LGPL-3.0
- GitHub stars
- 70
- Last push
- Jul 6, 2026
Listed from public GitHub data, checked 2026-11-08. Not scanned by AgenticMart.
Questions about Faremeter
What is Faremeter?
Framework for machine payments with pluggable x402 schemes It is listed as a x402 SDK, maintained in the faremeter/faremeter repository on GitHub.
How do I install Faremeter?
The README in faremeter/faremeter has the setup steps. Clone the repository with git clone https://github.com/faremeter/faremeter.git and follow its instructions.
Is Faremeter an official x402 project?
No. It is a community project built on x402, not published by the organisation that runs the protocol.
What license does Faremeter use?
It is published under the LGPL-3.0 license. Check the license file in the repository before using it commercially.
Is Faremeter still maintained?
Its code was last pushed on Jul 6, 2026, and it had 70 GitHub stars when we checked on 2026-11-08. Look at recent issues and releases in the repository for a fuller picture.
README
Faremeter: Frictionless Agentic Payments
Faremeter is a collection of libraries, tools, and applications designed to allow agents and other utilities to transparently make web3 payments using web2 infrastructure. By leveraging existing and emerging standards, you can use Faremeter to attach new and legacy client SDKs and API services to blockchain payments, without extensive rewrites.
Under the hood, Faremeter is built around:
- Using HTTP and the existing
402 Payment Requiredconcepts. - A plugin system that's standard, wallet, and blockchain agnostic.
- Wrappers, middleware, and proxies that let you easily integrate into your existing codebase.
For more information on our approach, take a look at our architecture document.
The implication of this is:
- New payment strategies (e.g. x402 Schemes) can be developed outside of the core Faremeter project.
- Blockchains with specific behaviors and needs can be supported without forcing a one-size-fits-all approach.
- Wallets and other infrastructure can be connected to Faremeter without "official" support.
To get started with the tooling, take a look at the quickstart guide. To start developing, take a look at the developer notes.
Standards
Faremeter supports the following industry standards today:
- Coinbase's x402 — both v1 and v2 of the protocol, negotiated automatically.
- MPP (Machine Payments Protocol) — the spec is still evolving; we currently ship the
chargeintent on Solana.
We're tracking these for future support:
See the compatibility document for the detailed status of each standard.
What's in the box
Faremeter ships with payment support for both the Solana and EVM ecosystems:
- A pluggable client library.
- A middleware with both remote and in-process payment handlers, plus an OpenAPI-driven pricing middleware for spec-driven endpoints.
- Solana payment schemes (
flex,exact, and the MPPchargeintent) in @faremeter/payment-solana. - EVM
exactover EIP-3009 gasless USDC in @faremeter/payment-evm, with network coverage including Base, Polygon, Monad, and Skale (mainnet and testnets). - A payment facilitator and legacy service proxy, plus an nginx gateway.
- Wallet integrations for Solana, EVM, Ledger, Squads multisig, Crossmint, and OWS.
Sponsorship
Faremeter is sponsored and built by the engineers at ABK Labs along with other open-source contributors.
More x402 projects
All 20 →x402
Reference specification and SDKs for the x402 payments protocol
vapi-network
TypeScript client for paying x402 APIs in USDC on Base
Daydreams
Agent commerce toolkit with x402 pay-per-use model access