> For the complete documentation index, see [llms.txt](https://documentation.pulseap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pulseap.com/core-concepts/co-chains.md). # Co-Chains **Co-Chains** are how **Pulse AP** brings modularity and flexibility to real-world systems. They give developers their own mini blockchain environments that operate on top of **Pulse AP’s** secure base network, removing the need to build everything from the ground up. Simply deploy your co-chain, define its logic, choose your pricing model, and either use the native token **($PULSE)** or launch your own. Every co-chain is fully programmable and built to match your exact use case. Whether you are developing robotics control systems, deploying AI into machines, or creating something entirely new, co-chains let you move quickly while maintaining full control. There is no reliance on centralized backends, and no need to reinvent the wheel. Each co-chain functions as part of a broader modular ecosystem. You can connect your application to compute chains, AI agents, storage layers, and other decentralized services within **Pulse AP**. Everything is interoperable, permissionless, and composable. The architecture is flexible, integrations are seamless, and ownership always remains with the builder. Although robotics is the primary focus, the infrastructure is adaptable to any developer or organization ready to build and deploy at the edge.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.pulseap.com/core-concepts/co-chains.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.