> For the complete documentation index, see [llms.txt](https://docs.computesdk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.computesdk.com/platform.md). # Platform - [Overview](https://docs.computesdk.com/platform/platform.md): The ComputeSDK Platform is the hosted control plane for ComputeSDK: managed Benchmarks, Actions CI on real compute providers, organizations, and a REST API + CLI for driving all of it. - [CLI reference](https://docs.computesdk.com/platform/cli.md): Install and use the \`compute\` CLI (@computesdk/cli) to drive the ComputeSDK Platform — Actions dispatch, run logs, artifacts, provider credentials, secrets and variables, connected repos, sandboxes, a - [Actions](https://docs.computesdk.com/platform/actions.md): ComputeSDK Actions is a CI/workflow engine that runs GitHub-style workflow YAML on real compute-provider sandboxes — connect repos, register provider credentials, dispatch runs, and stream logs from t - [Benchmarks](https://docs.computesdk.com/platform/benchmarks.md): Managed benchmarks on the ComputeSDK Platform — org-private and subscribed benchmark runs over the REST API and \`compute bench\` CLI. - [API reference](https://docs.computesdk.com/platform/api-reference.md): The ComputeSDK Platform REST API surface — every /api/v1 endpoint for Actions, the vault, benchmarks, organizations, and the org feed. --- # 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://docs.computesdk.com/platform.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.