What problem does it solve? Backend services like workers, cron jobs, and microservices need to call Overlens APIs on their own behalf, but wiring up OAuth 2.0 client_credentials correctly — token caching, scope-based authorization, secret handling — is error-prone and often confused with the user login flow. ## Core Features & Use Cases - Copy-paste M2M client templates: Ready-made TypeScript/NestJS, Python, and Go clients that fetch tokens via POST /auth/token and cache them in memory until exp − 30s, avoiding 429 rate-limit errors. - Client registration guidance: Exact POST /admin/clients payload for a confidential M2M client (isPublic:false, allowedGrantTypes:['client_credentials'], redirectUris:[], exhaustive allowedScopes) plus required environment variables. - Resource Server authorization patterns: Scope guards and user-vs-M2M discrimination (client_id present, email absent) for the API consuming the token. - Use Case: A developer needs a nightly billing worker to call api.overlens.com.br. They register an M2M client, drop in the TypeScript template, set four env vars, and the worker obtains and reuses 5-minute Bearer tokens automatically. ## Quick Start Ask the assistant to integrate Overlens machine-to-machine authentication into your backend service using the client_credentials flow.