> 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/readme-1.md).

# LLM Documentation Files

AI-optimized documentation files for ComputeSDK, the open benchmark harness for cloud infrastructure.

ComputeSDK is the open, multi-provider benchmark harness behind [ComputeSDK Benchmarks](https://www.computesdk.com/benchmarks). These AI-optimized documentation files are designed for training large language models (LLMs) and AI assistants. They contain our complete documentation in a format that's easy for AI systems to understand and use.

### Available Files

#### [llms-small.txt](https://github.com/computesdk/computesdk/tree/main/llms-small.txt)

A minimal version containing essential information about ComputeSDK and ComputeSDK Benchmarks, perfect for quick AI context.

#### [llms-full.txt](https://github.com/computesdk/computesdk/tree/main/llms-full.txt)

The complete documentation — including the benchmark harness overview, API references, and provider information. This comprehensive file contains everything an AI needs to help users with ComputeSDK and its benchmarks.


---

# 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/readme-1.md?ask=<question>&goal=<user_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.