M2M tokens are now generally available, marking a significant step for backend service authentication. After extensive beta testing, the APIs are stable, allowing developers to implement secure communication between various backend systems, including microservices and distributed architectures. The transition from beta to general availability means users can build production-grade applications without the worry of future breaking changes. Key features include stable APIs and usage tracking. The Clerk Dashboard now displays usage charts for monitoring token creation and verification, helping users manage their authentication effectively. Pricing follows a usage-based model: $0.001 for creating a token and $0.00001 for verifying opaque tokens. Billing isn’t active yet, but users will receive a 30-day notice before it begins, allowing them to adjust their usage accordingly. Future developments include the introduction of M2M tokens as JSON Web Tokens (JWTs), which will allow local verification without network calls. Resources for getting started, such as a detailed guide, example repository, and a machines dashboard, are readily available for users looking to implement this feature. Feedback from the beta phase has been instrumental in shaping M2M tokens, and the team is eager to see how users leverage this new capability.