Goldsky Feeds

Feeds answers one question about one wallet over HTTP: what it holds, or what it sent and received, across the supported chains in a single request. Goldsky indexes, normalizes, and prices the rows. The caller does not run a pipeline.

The same host and the same key also serve Polymarket and block-header feeds. Those are listed under "Other feeds on this key", and they do not follow the conventions below.

The installed CLI has no feeds command. Do not look for goldsky feeds, and do not mint the key with goldsky edge create. The endpoint name feeds is reserved on the Edge create path, so that command is rejected. The CLI login token is a different credential and does not authenticate these requests.

When this is the wrong tool

• The rows need to land in the user's own database or webhook. That is a Turbo pipeline (/turbo-builder, /datasets). Feeds does not stream into a sink; streaming is not offered yet (https://docs.goldsky.com/feeds/streaming).
• The question is a Turbo dataset name or chain prefix. That is /datasets. Those prefixes differ: Feeds says polygon and arbitrum_one, Turbo says matic and arbitrum.
• The question is JSON-RPC. That is /edge, or /boost when they want to keep their current provider.

Key

A project has one Feeds key, and every feed answers it. Creating that key is the setup. Do it with the API. Do not send the user to the dashboard, and do not run goldsky edge create.

The call authenticates with the project token from goldsky login, which is stored at ~/.goldsky/auth_token. Do not read that file into the chat, do not pass --token, and do not ask the user to paste a token. If goldsky project list says they are not logged in, use /auth-setup first. The caller has to be an Editor on the project.