Account

Balance, plans and Cloud projects load from api.ide.kuunda-cloud.com. Payment credentials are never stored in this page.

Session

Internal session token only. Email, Google, GitHub and Apple login are not enabled until the Worker auth routes are live.

Credits

Balance and plan come from the API after a session exists.

—

Plans

Catalogue from GET /v1/billing/plans. Checkout opens a hosted page on the API — never a card form here.

Payment failures show as insufficient funds, timeout, or declined — never a provider dump.

Kuunda Cloud projects

Linked projects appear once provisioning and a session are enabled.

Device pairing

Enter the short-lived code shown by Kuunda IDE. Verify the device name and platform before approving.

Review a device code

Models & agents

Agent profiles and preferences sync to your Kuunda account. API keys never leave a device: this page never asks for one.

Sync: — · event 0 · Catalogue —

Agent profiles

A profile edited here reaches the desktop IDE without a restart. Models come from the published catalogue.

Profiles revision —

BYOK keeps the key in the OS vault on each machine. Managed sends the run through the Kuunda gateway and debits credits on real tokens.

Default profile

Preferences revision —

Developer instructions

Account-scoped block, synced across machines. Project rules (KUUNDA.md, .kuunda/rules) stay in the project and never reach this server.

Test the managed gateway

Send a request through the Kuunda gateway using a managed profile. The reply streams token by token; its content stays private to this request.



          

Devices

Agent runs

Live state pushed over WebSocket. Only relative file labels and tool names travel — never file contents or terminal output.