# Introduction

The Onehub API enables developers to access data from the Onehub Service on behalf of a client. The API is organized around [REST](http://en.wikipedia.org/wiki/Representational_state_transfer). Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. Where appropriate, the API provides the four basic functions of persistent storage — **create**, **read**, **update**, and **delete**. In general, most API resources will accept an `index` request and return a [paginated](https://developer.onehub.com/api/pagination) set of all available items.


---

# Agent Instructions: 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:

```
GET https://developer.onehub.com/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.