Start with your AI assistant.
Copy a prompt, connect the Not Organic MCP, and build against the actual platform contracts.
Use the prompts below with your project open. They direct your assistant to inspect the app, preserve security boundaries, and verify the result.
Integrate my app
Give this prompt to your coding assistant inside your project.
Integrate this application with Not Organic. First inspect the repository and identify the framework, app origin, callback route and existing authentication. Read https://docs.notorganic.info/integrate and https://docs.notorganic.info/ai/integration.md, or use the Not Organic MCP guides. Use the supplied browser sign-in module where appropriate. Implement a user-triggered sign-in with PKCE and state, a single-use callback attempt, clear loading/error states and recovery. Keep provider secrets out of browser code. Request only necessary scopes. Do not assume production access: applications require review and exact-origin configuration. Do not submit an application, change deployment settings, spend money or create an account without user authorization. Verify callback mismatch, stale state and unsuccessful exchange. Report local checks separately from a real user-approved sign-in.Design a learning plan
Give this prompt to your coding assistant inside your project.
Design a Not Organic learning integration for this product. Read https://docs.notorganic.info/learning and https://docs.notorganic.info/ai/learning.md. Compare context-only, individual LoRA, organization LoRA, and organization adaptation plus private individual context. Ask only for missing business decisions. Define account/workspace ownership, permitted training data, consent, isolation, evaluation, budget, serving compatibility, revision promotion and rollback. A personal adapter is optional. Existing evolution APIs manage artifacts, evidence, jobs and revisions; do not invent a hosted LoRA training API or organization membership endpoint. Identify what is implemented, what needs provider configuration and what needs engineering. Do not launch training, publish data or spend money without authorization.Diagnose a failed sign-in or response
Give this prompt to your coding assistant inside your project.
Diagnose this Not Organic integration using https://docs.notorganic.info/authentication and https://docs.notorganic.info/operations. Trace the path from the user's sign-in action through callback, token exchange, scoped request, wallet and model response. Use sanitized errors and request references. Never request or print passwords, tokens, private keys, cookies or authorization codes. Keep approval failures, CORS, expired sessions, insufficient wallet balance and upstream provider failures distinct. Preserve the user's message and offer the appropriate recovery. A healthy endpoint or passing unit test is not proof of end-to-end sign-in or inference. Report exactly which stage is verified.Connect the developer MCP
Use this URL with an MCP client that supports Streamable HTTP:
https://id.notorganic.info/mcpThe server provides public guides, reusable prompts, and app-origin/callback validation. No account, API key, or admin access is required. Do not send secrets. It cannot inspect private applications, approve reviews, deploy, train models, or spend money.
Machine-readable references
llms.txt · Combined reference · Integration Markdown · Learning Markdown
Read the implementation guides
Integration and sign-in · Learning and workspaces · Authentication · API reference · Application administration
Applications require review before launch. The platform’s existing account and evolution contracts do not imply every training and serving path is configured.