Auth0

What Plutus imports

• Failed logins
• Brute-force blocks
• Breached-password attempts

Connecting

Method: Machine-to-Machine Application

1. Open your Auth0 dashboard → Applications → Applications → Create Application.
2. Choose Machine to Machine Applications, then authorize it for the Auth0 Management API.
3. Grant the read:logs scope (read:logs_users too, if you want user-identifying log fields).
4. Copy the Client ID and Client Secret from the application’s Settings tab, and your tenant domain (e.g. my-tenant.us.auth0.com) from the same page.
5. Paste all three into Plutus, click Save & connect, then Sync now to pull failed logins, brute-force blocks and breached-password attempts onto your cost charts.

Notes

A wave of failed logins, brute-force blocks or breached-password attempts is the one signal here that isn’t about code shipping — a credential-stuffing attack against a login-gated app can move an Auth0 bill (which prices by monthly active user) with nothing in your deploy history to explain it. Successful logins and ordinary Management API activity are not synced — only these three security-relevant log families.

This is an event-only source — Auth0 has no self-serve billing API, so there’s no matching cost source.