> For the complete documentation index, see [llms.txt](https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/api-reference/readme.md). # API Reference HPEC is not an API-first platform. It is an infrastructure-first, governance-driven network. ### Overview In HPEC, interfaces define **where autonomy ends and responsibility begins**.\ Some interfaces are traditional APIs. Others are **bootstrap processes, declarative roles, and governance hooks**. > **In HPEC, the first interface is a node joining the network — not a request hitting an endpoint.** This section documents all current and evolving interfaces used to interact with the HPEC ecosystem. *** ### Primary Interface: CMHPEC Bootstrap The [#primary-interface-cmhpec-bootstrap](#primary-interface-cmhpec-bootstrap "mention") is the **canonical entry point** into the HPEC network. For most operators, this is the **only interface required**. #### What the Bootstrap Does The bootstrap process: * Registers a node into the CMHPEC network * Establishes cryptographic trust and authority * Applies node roles and operational labels * Connects the node to the secure mesh * Enforces governance and compliance rules There are: * ❌ No API keys * ❌ No dashboards * ❌ No manual service configuration Everything is **declarative, automated, and governed**. 📎 See: [#primary-interface-cmhpec-bootstrap](#primary-interface-cmhpec-bootstrap "mention") *** ### Declarative Infrastructure Interfaces Beyond the bootstrap, HPEC exposes **non-API interfaces** that define how infrastructure behaves. These include: #### Node Roles & Labels Nodes declare their operational intent using governance-recognized labels (e.g. operator, worker, service provider). #### Authority & Governance Recognition Nodes and operators are recognized through: * Node Operator Authority (NOA) * Governance participation * Compliance validation #### Node Factories & Services Factories and services expose **capabilities**, not endpoints: * Compute availability * Autonomous service execution * SLA participation * Reward eligibility These interfaces are enforced at the **network and governance layer**, not via HTTP requests. *** ### Programmatic Interfaces (Limited) HPEC currently exposes **restricted programmatic interfaces** used internally by the network. These may include: * Monitoring and telemetry endpoints * Agent task coordination * Internal service orchestration * Factory and node health reporting ⚠️ These interfaces are: * Not public * Not guaranteed stable * Governed by DAO policy * Subject to change without notice They are **not required** for standard node operators. *** ### Interface Stability & Governance All HPEC interfaces — including APIs — are governed by: * DAO decisions * Network upgrades * Security requirements Interface availability, stability, and permissions may evolve as governance matures. *** ### Future Interfaces & APIs Planned future interfaces may include: * Service provisioning APIs * Autonomous agent orchestration * Economic and reward reporting * Governance participation hooks These will be introduced **only when aligned with network security and decentralization principles**. *** ### Summary * HPEC interfaces are **infrastructure-native** * Bootstrap is the primary entry point * APIs are secondary and scoped * Governance defines access and behavior HPEC prioritizes **resilience, autonomy, and trust** over convenience abstractions. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/api-reference/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.