> For the complete documentation index, see [llms.txt](https://docs.ticko.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ticko.xyz/api-documentation/authentication/agent-key.md).

# Agent Key

Ticko API keys are Agent keys. An Agent key is a signing key authorized by a user wallet to submit API requests for an account within its approved permission scope.

## Authorization model

* The user wallet remains the account owner and authorizes the Agent key.
* The Agent key is used only for request signing.
* The Agent key can sign trading and trading-related account-setting requests for the authorized account scope.
* Authorizing a main account allows the Agent key to operate the main account and its sub-accounts.
* Authorizing a sub-account allows the Agent key to operate only that sub-account.
* The Agent key cannot withdraw funds, transfer funds, create sub-accounts, or manage API keys.

## Account data queries

Account data queries use account addresses, not Agent key addresses:

* To query data for a main account, pass the main account address required by the endpoint.
* To query data for a sub-account, pass the sub-account address required by the endpoint.
* Passing an Agent key address does not return data for the account that authorized it.

## Key types

* **User wallet private key:** full account authority. Required for API key management, sub-account creation, transfers, and withdrawals. It can also sign trading and account-setting requests, but using an Agent key is recommended for those actions.
* **API key / Agent key:** delegated trading key. Used by bots and API integrations for trading and account-setting endpoints.

## API key rules

* **Uniqueness:** an Agent address can be authorized only once globally.
* **TradeVM account mutex:** `agent_address` must not already have a TradeVM account. If an authorized Agent address later creates a TradeVM account, its Agent authorization is automatically invalidated.
* **Limit:** up to 4 Agent keys per authorized account.
* **Label:** required, unique within the account, 1-32 characters, matching `^[A-Za-z0-9](?:[A-Za-z0-9_-]{0,30}[A-Za-z0-9])?$`.
* **Scope:** authorizing a main account allows operating that account and its sub-accounts. Authorizing a sub-account allows operating only that sub-account.
* **Permissions:** trading and account settings only. No withdrawals, transfers, API key management, or sub-account creation.


---

# 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.ticko.xyz/api-documentation/authentication/agent-key.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.