Developer Console Setup

Sign in with the active flow

The developer surface uses the active Supabase OAuth flow. Start from /developers/login, finish Google or Apple sign-in, then return here to prepare your developer identity and runtime credentials.

• One developer app is created per signed-in Kai account.
• One active developer token is kept at a time. Rotate it whenever you need a fresh credential.
• Consent prompts show your app identity, not a raw token or opaque runtime id.

Complete your developer profile

Your app identity is what users see during consent review inside Kai. Fill in your company details first so the approval request does not look anonymous or unfinished.

Generate your API key

Generate the developer key after profile setup. Keep it secure and use it for the REST contract plus the browser-safe tooling on this site.

Generate a session token

Use the API key to mint a session token. This is the cleanest way to move from console setup into the request-consent and status-polling flow.

Validate the runtime

Before you request real user consent, validate the session token once so you know the developer contract is wired correctly.

Before requesting consent

• Keep your display name, support contact, and environment URLs current.
• Use Agent Kai API Reference as the canonical contract source.
• Use /agents only for browser-safe testing of the restored runtime.
• Request one narrow scope at a time before you expand into broader PKM branches.