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

# Build with agents

> Use Goldsky Feeds from AI agents and coding assistants: install the Feeds skill, connect the docs MCP server, get a Feeds key from the Goldsky API, and generate tools from the OpenAPI spec.

Feeds suits AI agents. One HTTP request answers a question like "what does this wallet hold?" across all 8 [supported chains](/feeds#supported-chains). Responses are normalized JSON with USD values already attached, so an agent doesn't need to decode logs or look up prices.

This page covers four ways to build with Feeds from an agent:

| Goal | Use |
| - | - |
| Have a coding assistant write Feeds code for you | [The Feeds skill](#install-the-feeds-skill) |
| Let an agent look up the Feeds docs while it works | [The docs MCP server](#connect-the-docs-mcp-server) |
| Let an agent provision its own Feeds key | [The Goldsky API](#get-a-feeds-key-from-the-goldsky-api) |
| Give an agent Balances and Transfers as callable tools | [The OpenAPI spec](#generate-tools-from-the-openapi-spec) |

## Install the Feeds skill

The [Goldsky Agent](/ai-skills) skill pack includes a `feeds` skill for Claude Code, Cursor, Windsurf, Codex, and other AI coding assistants. It teaches the assistant how to authenticate, call the Balances and Transfers endpoints, and avoid common mistakes, such as using the Goldsky API token instead of the Feeds key.

```bash theme={"dark"}
npx skills add goldsky-io/goldsky-agent
```

After you install it, describe what you want in plain language. For example:

* "Show me what 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 holds on Base."
* "Build a portfolio endpoint that returns a wallet's total value and one row per token."
* "Write a job that checks for inbound USDC transfers to our deposit address every minute."

See [Agent Skills](/ai-skills) for other install methods and for agents that don't load skills automatically.

## Connect the docs MCP server

The Goldsky docs MCP server lets any MCP client search the Goldsky docs, including the Feeds API reference, while it answers. Point your client at:

```text theme={"dark"}
https://docs.goldsky.com/mcp
```

For clients that use the `mcpServers` schema, such as Cursor and Claude Code:

```json theme={"dark"}
{
  "mcpServers": {
    "goldsky": { "url": "https://docs.goldsky.com/mcp" }
  }
}
```

See [Goldsky MCP server](/mcp-server) for setup in other clients.

## Get a Feeds key from the Goldsky API

An agent can get your project's Feeds key from the [Goldsky API](/api-reference/overview) without opening the dashboard. For the dashboard option, see [Get an API key](/feeds/api/overview#get-an-api-key). Authenticate with a Goldsky API token from the [API Keys page](https://app.goldsky.com/dashboard/settings/api-keys) of the dashboard. The token needs the Editor role.

```bash theme={"dark"}
curl -X POST "https://api.goldsky.com/api/v1/feeds/api-key" \
  -H "Authorization: Bearer $GOLDSKY_API_KEY"
```

The call is idempotent. If the project has no Feeds key yet, it creates one and returns it once, as `data.api_key`. If a key already exists, `data.api_key` is `null`. Grab the existing key from the Feeds section of the dashboard, or rotate it with `POST /api/v1/feeds/key/rotate`. Rotating revokes the old key immediately and returns the new one once.

```json theme={"dark"}
{
  "data": {
    "name": "feeds",
    "api_key": "your-feeds-api-key"
  }
}
```

Store the key in `GOLDSKY_FEEDS_API_KEY` and send it in the `X-API-Key` header, which keeps it out of URLs and request logs:

```bash theme={"dark"}
curl "https://edge.goldsky.com/data/feeds/wallets/balances?address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045" \
  -H "X-API-Key: $GOLDSKY_FEEDS_API_KEY"
```

<Warning>
  The Goldsky API token and the Feeds key are different credentials. The token authenticates requests to `api.goldsky.com`. The Feeds key authenticates requests to `edge.goldsky.com/data`. Don't give an agent that only reads feed data access to the Goldsky API token.
</Warning>

The same API also lists every feed with `GET /api/v1/feeds`, and returns a feed's recent requests and usage under `/api/v1/feeds/{theme}/{dataset}/logs` and `/usage`. See the [Feeds catalog in the API reference](https://api.goldsky.com/api/v1/docs/#all/tag/feed-catalog) for every endpoint.

## Generate tools from the OpenAPI spec

Many agent frameworks can turn an OpenAPI spec into callable tools. Point them at the Feeds spec:

```text theme={"dark"}
https://edge.goldsky.com/data/openapi.json
```

The spec describes every parameter and response field of the [Balances](/feeds/api/balances) and [Transfers](/feeds/api/transfers) endpoints. It also includes other endpoints served with the same key, such as Polymarket and block data, so expose only the tools your agent needs. To also let the agent manage the Feeds key and read usage, add the Goldsky API spec at `https://api.goldsky.com/api/v1/docs/openapi.json`.

## Tips for agents

* **Filter by chain when you can.** Requests default to every supported chain. Pass `chains`, such as `chains=base`, when the user names a chain.
* **Follow pagination.** Both endpoints return pages. See [pagination](/feeds/api/overview#pagination) in the API overview.

Can't find what you're looking for? Reach out to us at [support@goldsky.com](mailto:support@goldsky.com) for help.


## Related topics

- [Agent Skills](/ai-skills.md)
- [Feeds](/feeds.md)
- [Introduction to Goldsky](/introduction.md)
- [ctx.hypercore: trade and deploy on Hyperliquid HyperCore](/compose/context/hypercore.md)
- [Goldsky MCP Server](/mcp-server.md)