> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/help/developer-access.md).

# Developer access

Request portal access for API Cookbooks, API Reference, Platform Guides, and the Object Model.

Some developer resources are available only in the Qore documentation portal. They support secure, consistent integrations with the platform.

{% hint style="info" %}
**Access is available on request.** Request access to receive login details for the documentation portal.
{% endhint %}

### Available resources

| Resource            | What it covers                                                                | Why it matters                                               |
| ------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------ |
| **API Cookbooks**   | Task-based examples for common API integrations.                              | Start with proven implementation patterns.                   |
| **API Reference**   | API endpoints, request and response formats, and authentication requirements. | Build requests that match the platform contract.             |
| **Platform Guides** | Implementation guidance for platform services, workflows, and integrations.   | Connect platform capabilities to your applications reliably. |
| **Object Model**    | The platform's core objects, fields, and relationships.                       | Map your data correctly across integrations.                 |

### Request access

Request access to the documentation portal. We provide login details after your request is approved.

{% hint style="warning" %}
You must sign in before you can access these resources.
{% endhint %}

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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.uptiq.ai/ai-workbench-qore/help/developer-access.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.