Accounts are one billing model. Protocol-native payment is another.
Traditional API billing usually starts with account creation and credentials. x402 can expose the payment requirement directly at the resource boundary, letting software discover terms and authorize within its own policy.
Current SML examples use Base/USDC and fresh x402-v2 challenges. Retired GitHub and multi-rail material is not current authority.