> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# extraAgents | Hyperliquid info

> Reference for the extraAgents JSON-RPC method on the Hyperliquid info blockchain via Chainstack nodes. Parameters, response, and examples included.

<Info>
  This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see [Hyperliquid methods](/docs/hyperliquid-methods) for the full availability breakdown.
</Info>

The `info` endpoint with `type: "extraAgents"` retrieves information about additional agents or authorized accounts associated with a user's wallet on the Hyperliquid exchange. This endpoint provides details about delegated permissions, agent activities, and access control configurations for advanced account management.

## Parameters

### Request body

* `type` (string, required) — The request type. Must be `"extraAgents"` to retrieve extra agents associated with a user.
* `user` (string, required) — Address in 42-character hexadecimal format (e.g., `0x2ba553d9f990a3b66b03b2dc0d030dfc1c061036`).

## Response

The response is an array of agent objects:

### Agent identification

* `name` (string) — Human-readable label for the agent
* `address` (string) — Agent address in 42-character hexadecimal format
* `validUntil` (integer) — Timestamp in milliseconds until which the agent is valid

### Understanding agent management

**Agent types:**

* **Trading bots**: Automated trading systems with trade permissions
* **Management tools**: Applications with specific operational permissions
* **Backup accounts**: Secondary wallets with limited access rights
* **Service integrations**: Third-party services with delegated permissions

**Permission levels:**

* **Read-only**: Access to account information without modification rights
* **Trade-only**: Ability to execute trades but not withdraw funds
* **Full access**: Complete account management capabilities
* **Custom permissions**: Specific combinations of authorized actions

**Security considerations:**

* Agents provide controlled access without sharing private keys
* Permissions can be revoked or modified as needed
* Activity tracking enables audit trails for agent actions

## Example request

<CodeGroup>
  ```shell Shell theme={"system"}
  curl -X POST \
    -H "Content-Type: application/json" \
    -d '{"type": "extraAgents", "user": "0x2ba553d9f990a3b66b03b2dc0d030dfc1c061036"}' \
    https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info
  ```

  ```python Python (hyperliquid-python-sdk) theme={"system"}
  from hyperliquid.info import Info

  info = Info("YOUR_CHAINSTACK_ENDPOINT", skip_ws=True)

  agents = info.extra_agents(user="0x2ba553d9f990a3b66b03b2dc0d030dfc1c061036")
  print(agents)
  ```

  ```typescript TypeScript (@nktkas/hyperliquid) theme={"system"}
  import { HttpTransport, InfoClient } from "@nktkas/hyperliquid";

  const transport = new HttpTransport({ apiUrl: "YOUR_CHAINSTACK_ENDPOINT" });
  const client = new InfoClient({ transport });

  const agents = await client.extraAgents({
    user: "0x2ba553d9f990a3b66b03b2dc0d030dfc1c061036",
  });
  console.log(agents);
  ```
</CodeGroup>

<Note>
  **Use your own endpoint in your code.** The code examples use a placeholder Chainstack endpoint (YOUR\_CHAINSTACK\_ENDPOINT) — replace it with your own Hyperliquid node endpoint from the [Chainstack console](https://console.chainstack.com/). The curl above uses a shared public endpoint for quick checks only; do not use it in production.
</Note>

## Example response

```json theme={"system"}
[
  {
    "name": "Mobile QR",
    "address": "0x1715462edd45a87eea74e402428392ffc744eb20",
    "validUntil": 1756349176478
  },
  {
    "name": "p1",
    "address": "0xd56a73c11336d712403d346c7502f5af29027cda",
    "validUntil": 1766846919956
  }
]
```

## Use case

The `info` endpoint with `type: "extraAgents"` is essential for applications that need to:

* **Security auditing**: Review all authorized agents and their permissions
* **Access management**: Monitor and control delegated account access
* **Account administration**: Manage multiple agents for different purposes
* **Permission tracking**: Understand what actions each agent can perform
* **Activity monitoring**: Track agent usage and last activity timestamps
* **Security dashboards**: Display comprehensive account access information
* **Compliance monitoring**: Ensure appropriate access controls are in place
* **Agent lifecycle management**: Track creation and activity of authorized agents
* **Risk management**: Assess potential security exposure from delegated permissions
* **Multi-account coordination**: Manage complex trading setups with multiple agents
* **Automated trading oversight**: Monitor trading bot permissions and activity
* **Third-party integrations**: Track service permissions and access levels
* **Account recovery planning**: Understand backup access mechanisms
* **Institutional management**: Handle enterprise-level account delegation

This endpoint is particularly valuable for users who employ sophisticated trading setups with multiple automated systems, institutional users with complex permission structures, or anyone who needs comprehensive visibility into account access controls and delegated permissions on the Hyperliquid exchange.


## OpenAPI

````yaml openapi/hyperliquid_node_api/hypercore_info/info_extraagents.json post /4f8d8f4040bdacd1577bff8058438274/info
openapi: 3.0.0
info:
  title: Hyperliquid Node API
  version: 1.0.0
  description: This is an API for interacting with Chainstack Hyperliquid node.
servers:
  - url: https://hyperliquid-mainnet.core.chainstack.com
security: []
paths:
  /4f8d8f4040bdacd1577bff8058438274/info:
    post:
      tags:
        - hyperliquid operations
      summary: info (extraAgents)
      operationId: infoExtraAgents
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                type:
                  type: string
                  default: extraAgents
                  enum:
                    - extraAgents
                  description: Request type to retrieve extra agents associated with a user
                user:
                  type: string
                  default: '0x2ba553d9f990a3b66b03b2dc0d030dfc1c061036'
                  description: Address in 42-character hexadecimal format
              required:
                - type
                - user
      responses:
        '200':
          description: List of extra agents associated with the user
          content:
            application/json:
              schema:
                type: array
                description: List of extra agents associated with the user
                items:
                  type: object
                  properties:
                    name:
                      type: string
                      description: Label for the agent
                    address:
                      type: string
                      description: Agent address in 42-character hexadecimal format
                    validUntil:
                      type: integer
                      format: int64
                      description: Timestamp in milliseconds until which the agent is valid
                  required:
                    - name
                    - address
                    - validUntil
                example:
                  - name: Mobile QR
                    address: '0x1715462edd45a87eea74e402428392ffc744eb20'
                    validUntil: 1756349176478
                  - name: p1
                    address: '0xd56a73c11336d712403d346c7502f5af29027cda'
                    validUntil: 1766846919956

````