Developer Workspace

Sign in with the shared identity

The developer workspace uses the same Firebase identity project as Kai. Start from /developers/login or sign in inline below with Google or Apple, then keep all access and profile changes tied to that single account.

• 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.

Enable developer access

Use the local Kai workspace below to enable access, reveal a token once, rotate that token when needed, and keep your app identity aligned with what users see during consent review inside Kai.

Keep your app identity current

Your display name, site URL, support URL, policy URL, and brand image are part of the trust surface. Users see this identity when they approve or review consent, so do not leave it blank or stale.

• Use a human-readable app name that matches your product.
• Keep support and policy links live before you request real user consent.
• Rotate the token whenever team ownership or local secrets change.

Use the token safely

The raw developer token is only revealed after enable or rotate. Save it immediately, put it in your environment as an opaque secret, and use the runtime URLs below as the canonical setup shortcuts.

HUSHH_DEVELOPER_TOKEN=<developer-token>
https://api.kai.hushh.ai/mcp?token=<developer-token>

• Use Agent Kai API Reference as the canonical contract source.
• Keep the raw token in a secure secret store, not in client code or shared screenshots.
• Use ?token=<developer-token> only where the Kai reference explicitly documents it.
• Request one narrow scope at a time before expanding into broader PKM branches.