Projects & keys
Projects are optional workspaces for organizing Mizan keys and the spend they generate — useful once you have more than one app or environment calling through Mizan.
Projects
Every account has a default workspace — keys created without picking a project land there. Beyond that, you can create named projects (unique per account) from Settings → Projects, and archive ones you no longer need. Archiving removes a project from the project lists (including the Analytics filter); it doesn't touch the keys or spend history that were in it. Once you have more than one project, Analytics can be filtered to a single project — or left on "All projects" to see everything combined.
Keys
There's one key type — created from Mizan Keys, optionally assigned to a project. A key is never pinned to a single provider: which credentials serve a given call (your wallet or a BYOK connection) is resolved per request, based on the model you ask for.
Usage limits
Both keys and projects can carry their own spend ceilings — a lifetime cap, a rolling period cap, or both — enforced live and independent of your wallet balance. Once one is hit, the affected key (or every key in the affected project) returns a 403 until it's raised, cleared, or its period rolls over. Manage and monitor them all from the Limits page — see the full Limits docs for how the two levels interact and what happens once one fires.
Revoking & deleting
Revoking a key disables it immediately — any further request with it is rejected. Deleting (only available once revoked) just hides it from the Mizan Keys list; its request history keeps counting toward your spend totals, it's never actually removed.