> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/developer-tools/readme.md).

# Developer tools

Build on top of Cerby with a RESTful API and a powerful CLI. Automate workflows, integrate with your toolchain, and extend Cerby to fit your stack.

Cerby is built to be extended. Whether you're automating account operations, integrating Cerby into your internal tooling, or scripting workspace management tasks, the Cerby developer tools give you the access and control you need.

***

## What you can build with

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Cerby CLI</strong></td><td>A command-line interface for interacting with your Cerby workspace directly from your terminal. Ideal for scripting, automation, and power users.</td><td><a href="https://help.cerby.com/developer-tools/cerby-cli">https://help.cerby.com/developer-tools/cerby-cli</a></td></tr><tr><td><strong>Cerby API</strong></td><td>A RESTful API to programmatically manage accounts, users, and workspace resources. Integrate Cerby into your existing workflows and internal tools.</td><td><a href="https://github.com/cerbyinc/help-center/tree/main/extending_cerby/public-api/README.md">https://github.com/cerbyinc/help-center/tree/main/extending_cerby/public-api/README.md</a></td></tr></tbody></table>


---

# 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://help.cerby.com/developer-tools/readme.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.