One secure home for partner API keys

Before a partner can touch an API key, they have to get through the door properly. The portal opens on a clean auth screen — create an account or log in — with authentication handled by Auth0 rather than anything hand-rolled, and the usual terms-of-service and privacy consent captured up front.

Everything past this point is gated behind login. That's deliberate: API keys are credentials that can open and close real positions and move funds through the protocol, so the console that mints them is treated as a secure surface from the very first screen.

Inside, the dashboard is a straightforward key-management console. A partner can create a new API key, see every active key they hold with its unique identifier and creation timestamp, and revoke any key the moment it's no longer needed or might be compromised. Each key becomes the API key that authenticates the partner's calls to the Lavarage REST API.

That API is broad — core trading, portfolio operations, utilities, lending and staking, partner integration with webhooks and MEV protection, and market data — all rate-limited per key to keep any one integrator from overwhelming the protocol. The portal's job is to make the credential behind all of that easy to issue, easy to see, and easy to cut off.