asolytics-apilisted

# Asolytics Public API ## Overview Use this skill to work against the Asolytics Public API safely and efficiently. Prefer the bundled references over re-discovering the API from scratch, and refresh the spec before relying on exact request or response shapes if the docs may have changed. ## Workflow 1. Read [references/api-overview.md](references/api-overview.md) first for auth, base URL, and endpoint families. 2. Read [references/endpoints.md](references/endpoints.md) when you need endpoint-level parameters or request body fields. 3. Read [references/openapi.json](references/openapi.json) only when exact schema details or edge cases matter. 4. Prefer small, cheap requests first because the API is alpha and some endpoints consume tokens. 5. Use `GET /public-api/v1/balance` when token awareness matters before running a wide query. ## Auth Send the personal public API token in the `X-PUBLIC-API-TOKEN` header. Prefer an environment variable such as `ASOLYTICS_PUBLIC_API_TOKEN` instead of pasting secrets into files or commits. If the token is missing, ask the user for it. If they don't have one yet, walk them through getting it: 1. Create a free Asolytics account (or log in): https://app.asolytics.pro/login 2. Open the profile page and copy the public API token: https://app.asolytics.pro/profile 3. Export it locally so it isn't pasted into chats or commits: `export ASOLYTICS_PUBLIC_API_TOKEN="<token>"` Do this before running any write or paid requests. ```bash curl -sS