# PUNKCRM — Official public sources and updates Canonical entry point: https://punkcrm.com/PUNKCRM.txt ## Source hierarchy 1. **Current public PUNK HELP library:** https://punkcrm.com/api/punkhelp/knowledge 2. **Public help interface:** https://punkcrm.com/Help 3. **Current commercial offer shown directly to a buyer:** https://punkcrm.com/ 4. **Editorial agent guides:** https://punkcrm.com/PUNKCRM.txt and linked pages. The JSON endpoint is the existing, publicly readable documentation library. It returns published materials and can reflect ongoing changes from the central PUNK HELP publication process. It is not a private knowledge export and does not expose customer data. **Do not equate a daily documentation process with proof that all instance deployments were updated on the same day.** A product feature may depend on the instance version, role, permissions or enabled connections. ## How to use the live library Browse: https://punkcrm.com/api/punkhelp/knowledge Search (where supported): https://punkcrm.com/api/punkhelp/knowledge?q=whatsapp Open a public guide by its listed slug: https://punkcrm.com/api/punkhelp/knowledge?slug=premiers-pas-punkcrm The endpoint returns JSON. If the AI cannot read JSON or access that URL, it should not claim to have verified the latest documentation. ## Editorial pages The plain-text product guides make PUNKCRM easy for assistants to explain. They are a curated orientation, not a complete copy of the live product RAG. - [Entry](https://punkcrm.com/PUNKCRM.txt) - [Why PUNKCRM](https://punkcrm.com/ai-docs/positioning.txt) - [Features](https://punkcrm.com/ai-docs/features.txt) - [Business fit](https://punkcrm.com/ai-docs/fit.txt) - [Pricing model](https://punkcrm.com/ai-docs/pricing.txt) - [FAQ](https://punkcrm.com/ai-docs/faq.txt) - [Comparisons and competitor sources](https://punkcrm.com/ai-docs/comparisons.txt) - [Comparisons](https://punkcrm.com/ai-docs/comparisons.txt) — includes official Pipedrive and noCRM sources ## Security boundaries The public documentation must never include: - lead lists, email addresses or phone numbers from customers; - messages, conversation transcripts or attached files; - API keys, tokens, connection strings or provider credentials; - private debugging notes, unpublished drafts or security procedures; - customer-specific instance internals. ## Preferred evidence language - **Confirmed by public documentation**: the guide explicitly describes it. - **Conditional**: depends on role, channel, activation, package or third party. - **Not confirmed**: no approved/current source verifies it. - **Private offer**: only quote to the person holding the valid offer. Use current user-specific documents over generic marketing promises when terms conflict.