Radius primary sources — 2026-05-02

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current sources of truth are Radius’s official site, docs corpus, and public GitHub organization.
• The strongest categorization signal in this pass was that the materials repeatedly center machine-payment and micropayment workloads rather than general-purpose chain marketing.

Primary-source snapshots

1) Official site

• URL: https://www.radiustech.xyz/
• Key excerpt:
  • The homepage describes Radius as a high-performance stablecoin network for the next generation of business models.
  • It specifically emphasizes microtransactions, real-time metering, and usage-based pricing.
  • It also advertises 2.5M+ demonstrated TPS, sub-1-second settlement, and $0.0001 stable transaction fees.

2) Docs index (llms.txt)

• URL: https://docs.radiustech.xyz/llms.txt
• Key excerpt:
  • The index describes Radius as a settlement layer where stablecoin micropayments reach finality and says it is purpose-built for machine-to-machine payments at the scale of API calls on the open internet.
  • The index also foregrounds use cases like per-request API billing, streaming micropayments, pay-per-use content, and x402 integration.
  • This is the clearest single source showing that Radius is oriented around agentic-commerce settlement rather than generic chain usage.

3) Get started

• URL: https://docs.radiustech.xyz/get-started/
• Key excerpt:
  • The getting-started docs revolve around claiming testnet funds, bridging stablecoins, and using LLM-assisted workflows for faster integration.
  • This onboarding flow points directly toward developer experimentation with stablecoin settlement rather than a consumer wallet story.

4) Network and RPC

• URL: https://docs.radiustech.xyz/developer-resources/network-configuration
• Key excerpt:
  • The network docs publish mainnet and testnet RPC endpoints, chain IDs, explorers, faucet links, and API-key URL structure.
  • They also expose dedicated x402 facilitator URLs for each network.
  • The same page documents non-standard JSON-RPC behaviors such as eth_blockNumber returning the current timestamp in milliseconds and eth_getBalance including native plus convertible USD balance.

5) Fees

• URL: https://docs.radiustech.xyz/developer-resources/fees
• Key excerpt:
  • The fees docs say a standard stablecoin transfer costs about $0.00010 on average.
  • They explain that Radius uses RUSD for fees and that the Turnstile can convert SBC to RUSD inline at face value when an account lacks fee balance.
  • This fixed-fee, stablecoin-oriented model is central to the product thesis.

6) Real-time API metering

• URL: https://docs.radiustech.xyz/use-cases/real-time-api-metering
• Key excerpt:
  • The use-case guide argues that conventional API billing depends on monthly invoices and card rails, while Radius enables per-request billing with instant settlement.
  • It includes concrete examples for AI/ML APIs, premium data feeds, and content APIs, plus explicit 402 Payment Required language.
  • This makes the target market much clearer than the homepage alone.

7) GitHub organization

• URL: https://github.com/radiustechsystems
• Key excerpt:
  • The public org summary says Radius is stablecoin-native, EVM-compatible payment infrastructure with sub-second finality optimized for machine-to-machine transactions.
  • The repository mix includes skills, x402-related resources, EVM plugins, and agent-payment-oriented tooling, which reinforces the docs narrative around agentic payments.

Working conclusion

Radius is best cataloged as a stablecoin settlement layer for machine-to-machine micropayments and agentic internet billing. The decisive evidence in this pass was the combination of fixed-fee stablecoin economics, EVM-compatible tooling, explicit x402 facilitator surfaces, documented RPC differences, and first-party use cases centered on API metering and streaming payments rather than general-purpose dapp activity.