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

# Access Keys

An Access Key is used to authenticate and make secure programmatic API calls to the Zata.ai S3 service. It allows applications and S3-compatible tools to interact with object storage for operations such as uploading, downloading, listing, and managing files.

Each access key consists of two parts:

* **Access Key ID** – Acts as a public identifier (similar to a username).
* **Secret Access Key** – Acts as a private credential (similar to a password).

Both are required to authenticate requests to the Zata.ai API.

Access keys are used to make secure REST or Query protocol requests to the Zata.ai service. When configuring any S3-compatible client such as S3 Browser or Cyberduck, you must enter the Access Key ID and Secret Access Key in the respective fields.

The Zata.ai S3 endpoint is:

```
idr01.zata.ai
```

For security reasons, the Secret Access Key should never be shared with anyone. It is recommended to store access keys securely and rotate them periodically as a best practice.

Access keys provide a standardized and secure way to connect applications and tools with Zata.ai Object Storage.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zata.ai/manage/access-keys.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.