> For the complete documentation index, see [llms.txt](https://docs.re.al/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.re.al/services/indexers/goldsky.md).

# Goldsky

## Install + log in

1. Create an account at [app.goldsky.com](https://app.goldsky.com).
2. Create an API key on the Settings page.
3. Install the Goldsky CLI:

   ```sh
   curl https://goldsky.com | sh
   ```
4. Log in with the API key created earlier:

   ```sh
   goldsky login
   ```

## Build and deploy

Deploy your subgraph in one of four ways:

### Build and deploy from source

```sh
cd <your-subgraph-directory>
graph build # Build your subgraph as normal.
goldsky subgraph deploy my-subgraph/1.0.0
```

## Build & Deploy from ABI and address

```sh
goldsky subgraph deploy your-subgraph-name/your-version --from-abi <path-to-config-file>
```

## Query Endpoint

Access data by querying the endpoints. Use the following command to list all your subgraphs, and open the “GraphQL API” links that get printed in your browser to query your data in the GraphQL playground.

```sh
goldsky subgraph list
```


---

# 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.re.al/services/indexers/goldsky.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.