When you want Kimi AI itself, begin at the official Kimi website or official help center links. When you want Kimi K3 guides, K3Nova pages can help you understand workflows, model choices, local running, hardware, and pricing boundaries.
Keep login and payment actions on official domains you can verify. Use guide pages for learning and setup decisions, not for entering official account credentials.
AI handoff prompt and permissions
Copy this prompt into Kimi Code, K3Nova, or another AI agent. Keep approval manual for file writes, shell commands, account actions, and secrets.
Copyable AI prompt
Use this to give the agent the task and safety boundary in one message.
You are my AI agent for this task: verify official Kimi AI links and tell me which pages are safe for reading, login, API keys, or payment.
Start by restating the goal and the permissions you need.
Use official docs or the files I provide before making claims.
Give me a direct answer first, then a short table or checklist.
If commands are needed, show exact copyable commands without a shell prompt.
Ask before writing files, running shell commands, deleting or moving data, logging in, spending money, changing account settings, or handling API keys.
Stop and ask me when a step requires secrets, payment, account access, destructive cleanup, or a permission broader than the task.
Recommended AI permissions
Permission
Give AI
Why
Navigation
Allow opening public official docs and help pages.
The agent can verify domains and product boundaries.
Login
Deny entering credentials, solving account challenges, or continuing OAuth.
The user should control account access.
API keys
Deny copying, pasting, or displaying keys.
Guide pages should not handle secrets.
Bookmarks or notes
Ask before changing browser bookmarks, local files, or account settings.
Small changes still need consent.
Link groups and safety notes
Kimi Code safety
Kimi Code docs explain where data, credentials, plugins, and sessions live, which helps you clean up safely.
Kimi API safety
The API docs explain model choices and current unsupported capabilities, which helps avoid wiring a product to the wrong endpoint.
Kimi Claw safety
Kimi Claw docs explain cloud deploy and OpenClaw linkage, including plan and model-configuration details.
Safe-link checklist
Before you act
Why it matters
Better habit
Check domain and HTTPS
Lookalike pages can capture credentials
Navigate from a trusted bookmark
Read current docs
Model IDs and plan rules change
Use official model selection pages
Keep tokens out of chat
API keys and OAuth files are sensitive
Use documented config paths
Separate K3Nova from official Kimi
The surfaces have different responsibilities
Use each for the right job
Before login, payment, or API keys
Check the product you need
Kimi web, Kimi Work, Kimi Code, Kimi API, and Kimi Claw are different surfaces with different setup paths.
Use docs before entering keys
Read model and credential documentation before putting provider keys into any tool.
Treat unknown domains as read-only
If you are not sure a page is official, do not enter credentials, cards, tokens, or private project data.
Use K3Nova for practical planning
Open K3Nova when you want independent walkthroughs for context, local workspace behavior, benchmarks, and hardware planning.
FAQ
Where are official Kimi AI links?
Start from kimi.com and the official Kimi help center.
Can I use K3Nova as an official Kimi account page?
No. Use it as an independent Kimi-style workspace and guide surface.
What should I do before entering an API key?
Confirm the tool, docs, model ID, and credential storage path.
K3Nova