> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1/install-the-pandium-cli.md).

# Install the Pandium CLI

Install the Pandium CLI and log in to your sandbox so you can run your integration locally with the secrets, configs, and context of a real tenant.

When your integration runs on Pandium, the platform hands it the tenant's secrets, connection settings, and context as [environment variables](/getting-started/anatomy-of-an-integration/environment-variables.md). The [Pandium CLI](/getting-started/pandium-integration-development-kit-idk/pandium-cli.md) lets you run the integration on your own machine with those same values pulled from the tenant you just made, so you never have to copy secrets into a local file.

{% hint style="info" %}
The Pandium CLI is currently only available for Mac OS.
{% endhint %}

1. In your sandbox Integration Hub click **Settings** from the side bar > **Developer Resources**.
2. Copy the install command for your system (e.g. MacOS aarch64 for Apple Silicon), paste it into your terminal, and hit Enter.
3. Run `pandium login`. Sandbox is the default environment, so there is no need to specify one.
4. Run `pandium get integrations`. Your Pokémon of the Day integration should be listed along with its integration ID.
5. Run `pandium get tenants -i <integration-id>`, replacing `<integration-id>` with the ID from the previous step. Make note of your tenant's ID; you will use it every time you run the integration locally.

Now that you can reach your tenant from the command line, the next step is to fill out those starter files Pandium put in your remote repository with logic for your integration.


---

# 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.pandium.com/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1/install-the-pandium-cli.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.