Skip to main content
Faremeter supports multiple blockchain networks and assets. The @faremeter/info package provides lookup utilities for network configuration and asset details.

​
Supported networks

​
Solana

NetworkIdentifierStatus
DevnetdevnetSupported
TestnettestnetSupported
Mainnet Betamainnet-betaSupported

​
EVM

NetworkIdentifierStatus
Base Sepoliabase-sepoliaSupported
BasebaseSupported
Skale Europa Testnetskale-europa-testnetSupported
Polygoneip155:137Supported (CAIP-2)
Monadeip155:10143Supported (CAIP-2)
EVM networks support CAIP-2 format identifiers. Networks like Base Sepolia and Base have short aliases (base-sepolia, base). Others use the full CAIP-2 format (eip155:<chainId>).

​
Supported assets

AssetSolanaEVM
USDCDevnet, MainnetBase Sepolia, Base, Polygon, Skale
SOLDevnet, Testnet, Mainnet—

​
Using @faremeter/info

The info package provides helpers to construct payment requirements with correct network and asset details.

​
Solana

import { xSolanaSettlement } from "@faremeter/info/solana"

const requirements = xSolanaSettlement({
  network: "devnet",
  payTo: "7xKXwxRPMo2sUAT5...",
  asset: "USDC",
  amount: "10000",
})

​
EVM

import { x402Exact } from "@faremeter/info/evm"

const requirements = x402Exact({
  network: "base-sepolia",
  asset: "USDC",
  amount: "10000",
  payTo: "0x1234...",
})

​
Network aliases

The info package resolves network aliases to canonical identifiers. For example, "devnet" resolves to the correct Solana devnet RPC endpoint, and "base-sepolia" resolves to the correct EVM chain ID and RPC.

​
Configuring custom networks

When using the lower-level packages (@faremeter/fetch, @faremeter/payment-*), you can pass custom network configuration directly to wallet and handler factory functions. See the API Reference for the full configuration options.

​
Further reading