Radius

• Name: Radius
• URL: https://www.radiustech.xyz/
• Category: stablecoin settlement layer / machine-to-machine micropayments infrastructure / EVM-compatible agent-payments network
• Tags: ethereum-ecosystem
• Summary: Radius is a payments-first settlement chain for tiny stablecoin transfers and agent traffic, not a general-purpose EVM center. The live docs matter less for the TPS theater than for the operator shape: fixed-fee transfers, Ethereum and Base bridge ingress, x402 facilitator paths, and slightly off-standard JSON-RPC behavior that tells you this thing is tuned for metered machine billing rather than broad app neutrality.
• What it does:
  • Provides a stablecoin-native settlement network intended for micropayments, machine-to-machine commerce, and usage-based internet billing
  • Exposes EVM-compatible RPC endpoints, chain configuration, contract-address references, and standard tooling guidance for Foundry, viem, wagmi, Hardhat, and ethers.js integrations
  • Supports bridge flows from Ethereum and Base into Radius for USDC and SBC, plus testnet faucet access for developer onboarding
  • Uses a fixed-fee model designed to make stablecoin transfers cheap and predictable, with Turnstile conversion when an account has convertible stablecoin but lacks fee balance
  • Publishes dedicated use-case docs for real-time API metering, pay-per-visit content, streaming payments, and x402-based machine-payment settlement
  • Maintains a public GitHub organization with open-source repos for Radius skills, agent-payment-related tooling, and EVM integration surfaces
• Key claims:
  • The homepage says Radius is a “high-performance stablecoin network” for the next generation of commerce and highlights microtransactions, real-time metering, and usage-based pricing as core target workloads
  • The homepage claims 2.5M+ demonstrated TPS, sub-1-second settlement, and stable transaction fees of $0.0001
  • The docs index describes Radius as a settlement layer where stablecoin micropayments reach finality, purpose-built for machine-to-machine payments at the scale of API calls on the open internet
  • The network-configuration docs publish mainnet and testnet RPC endpoints, chain IDs, explorers, faucet paths, API-key URL format, and dedicated x402 facilitator URLs for both networks
  • The fees docs say a standard stablecoin transfer costs about $0.00010 on average and explain that Radius uses RUSD for fees while the Turnstile can convert SBC inline at 1:1 face value when needed
  • The network-configuration docs explicitly note Ethereum-compatibility differences such as eth_blockNumber returning the current timestamp in milliseconds, eth_getBalance including native plus convertible USD balance, and eth_feeHistory being pseudo-supported
  • The real-time API metering guide positions Radius as a way to charge per API call with instant settlement, no chargebacks, and far lower minimum-transaction economics than traditional card billing
  • The docs index also highlights pay-per-visit content, streaming payments, and x402 integration as first-class surfaces, which is strong evidence that Radius is packaging an agent-payments stack rather than only a base execution network
• Whitepaper: No canonical standalone Radius whitepaper or litepaper surfaced in this pass. The clearest current sources of truth are the official site, docs corpus, and public GitHub organization; see ../whitepapers/radius-primary-sources-2026-05-02.md.
• Sources:
  • https://www.radiustech.xyz/
  • https://docs.radiustech.xyz/
  • https://docs.radiustech.xyz/llms.txt
  • https://docs.radiustech.xyz/get-started/
  • https://docs.radiustech.xyz/developer-resources/network-configuration
  • https://docs.radiustech.xyz/developer-resources/fees
  • https://docs.radiustech.xyz/use-cases/real-time-api-metering
  • https://github.com/radiustechsystems

Internal linkages

• Best stronger payments-chain read: plasma.
• Best paid-request overlay contrast: x402.

Control surface

• The leverage sits in bridge ingress from Ethereum and Base, fee-asset policy, RPC quirks, x402 facilitator defaults, and whatever operator choices decide which machine-payment flows feel first-class.

• Treat Radius as a narrow settlement environment for agent billing and metered services, not as a general EVM hub.

• Last reviewed: 2026-06-15 UTC