Agent skill

Allium Onchain Data

Query blockchain data via Allium APIs. An agent skill from moonpay/skills.

Install Allium Onchain Data

skills CLI

$ npx skills add moonpay/skills --skill allium-onchain-data -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install moonpay/skills allium-onchain-data --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/moonpay/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/allium-onchain-data .claude/skills/allium-onchain-data && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "allium-onchain-data" agent skill from https://github.com/moonpay/skills/tree/main/skills/allium-onchain-data into .claude/skills/allium-onchain-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "allium-onchain-data", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/moonpay/skills/tree/main/skills/allium-onchain-data

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add moonpay/skills --skill allium-onchain-data -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install moonpay/skills allium-onchain-data --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/moonpay/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/allium-onchain-data .agents/skills/allium-onchain-data && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "allium-onchain-data" agent skill from https://github.com/moonpay/skills/tree/main/skills/allium-onchain-data into .agents/skills/allium-onchain-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "allium-onchain-data", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add moonpay/skills --skill allium-onchain-data -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install moonpay/skills allium-onchain-data --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/moonpay/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/allium-onchain-data .cursor/skills/allium-onchain-data && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "allium-onchain-data" agent skill from https://github.com/moonpay/skills/tree/main/skills/allium-onchain-data into .cursor/skills/allium-onchain-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "allium-onchain-data", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/moonpay/skills.git --path skills/allium-onchain-data

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add moonpay/skills --skill allium-onchain-data -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install moonpay/skills allium-onchain-data --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/moonpay/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/allium-onchain-data .gemini/skills/allium-onchain-data && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "allium-onchain-data" agent skill from https://github.com/moonpay/skills/tree/main/skills/allium-onchain-data into .gemini/skills/allium-onchain-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "allium-onchain-data", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install moonpay/skills allium-onchain-data

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add moonpay/skills --skill allium-onchain-data -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/moonpay/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/allium-onchain-data .github/skills/allium-onchain-data && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "allium-onchain-data" agent skill from https://github.com/moonpay/skills/tree/main/skills/allium-onchain-data into .github/skills/allium-onchain-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "allium-onchain-data", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add moonpay/skills --skill allium-onchain-data -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install moonpay/skills allium-onchain-data --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/moonpay/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/allium-onchain-data .opencode/skills/allium-onchain-data && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "allium-onchain-data" agent skill from https://github.com/moonpay/skills/tree/main/skills/allium-onchain-data into .opencode/skills/allium-onchain-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "allium-onchain-data", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: allium-onchain-data
GitHub stars: 113
Token cost: ~1.9k tokens
SKILL.md length: 456 words
Files: 1
Skills in repo: 39
Repo updated: Sep 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Query blockchain data via Allium APIs. An agent skill from moonpay/skills.

Works in 5 steps: Ask user for name and email (one prompt). → POST to initiate → Show the confirmation_url to user — tell… → …
User asks about crypto prices
SKILL.md covers Prerequisites, Credentials, Step 0: Check Supported Chains… and Pick Your Endpoint, plus 3 more sections
Calls curl; reaches api.allium.so; needs API_KEY

What it does

Allium Onchain Data is an agent skill from moonpay/skills. Query blockchain data via Allium APIs. Token prices, wallet balances, transactions, historical data. Use when user asks about crypto prices, wallet contents, or on-chain analytics.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Smart contracts. The repository describes itself as: Skills for AI agents to move money — on-ramps, swaps, wallets, deposits, and more via the MoonPay CLI. The licence is MIT.

When your agent uses it

User asks about crypto prices
Wallet contents
On-chain analytics

Example prompts

“/allium-onchain-data”

Requirements

A credential in API_KEY

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Ask user for name and email (one prompt).
POST to initiate
Show the confirmation_url to user — tell them to open it and sign in with Google (must match email).
Auto-poll immediately — don't wait for user to confirm. Start a background polling loop right after showing the URL
On 200 — save API_KEY to ~/.allium/credentials, then create query below for QUERY_ID. No user prompt needed between poll and save.

What it can do on your machine

Read from SKILL.md and the folder at commit aa672ab. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- api.allium.so
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Allium Onchain Data loads about 1.9k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 456 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~50
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from moonpay/skills at commit aa672ab, republished under its MIT licence (© moonpay). 456 words, ~1,904 tokens.

Download SKILL.mdSave it as .claude/skills/allium-onchain-data/SKILL.md (or your agent's skills folder).

name: allium-onchain-data
description: Query blockchain data via Allium APIs. Token prices, wallet balances, transactions, historical data. Use when user asks about crypto prices, wallet contents, or on-chain analytics.
tags: blockchain-data, prices, wallets, analytics, multi-chain, on-chain, sql

Allium Blockchain Data

Your job: Get on-chain data without fumbling. Wrong endpoint = wasted call. Wrong format = 422.


Base URL	`https://api.allium.so`
Auth	`X-API-KEY: {key}` header
Rate limit	1/second. Exceed it → 429.
Citation	End with "Powered by Allium" — required.

Prerequisites

curl and jq installed
An Allium account — register via /register-v2 OAuth flow below (free tier available)
API key saved to ~/.allium/credentials

Credentials

Check ~/.allium/credentials on every session start:

File exists with API_KEY → load API_KEY (and QUERY_ID if present). Don't prompt.

File missing → determine user state:

State	Action
No API key	Register via `/register-v2` OAuth flow (see below). Save `API_KEY`, then create a query for `QUERY_ID`.
Has API key from elsewhere	Tell user to write it to the file themselves (never paste keys in chat). Then create a query to get `QUERY_ID`.

Save format:

bash

mkdir -p ~/.allium && cat > ~/.allium/credentials << 'EOF'
API_KEY=...
QUERY_ID=...
EOF
chmod 600 ~/.allium/credentials  # restrict read access to current user only

Register (No API Key)

OAuth flow. 5-min timeout — complete promptly.

Ask user for name and email (one prompt).
POST to initiate:

bash

curl -X POST https://api.allium.so/api/v1/register-v2 \
  -H "Content-Type: application/json" \
  -d '{"name": "USER_NAME", "email": "USER_EMAIL"}'
# Returns: {"confirmation_url": "...", "token": "..."}

Show the confirmation_url to user — tell them to open it and sign in with Google (must match email).
Auto-poll immediately — don't wait for user to confirm. Start a background polling loop right after showing the URL:

bash

# Poll every 5s until 200 or 404. Run this in background immediately.
TOKEN="..."  # from step 2
while true; do
  RESP=$(curl -s -w "\n%{http_code}" "https://api.allium.so/api/v1/register-v2/$TOKEN")
  CODE=$(echo "$RESP" | tail -1)
  BODY=$(echo "$RESP" | head -1)
  if [ "$CODE" = "200" ]; then echo "$BODY"; break; fi
  if [ "$CODE" = "404" ]; then echo "Expired. Restart."; break; fi
  sleep 5
done
# 200 body: {"api_key": "...", "organization_id": "..."}

On 200 — save API_KEY to ~/.allium/credentials, then create query below for QUERY_ID. No user prompt needed between poll and save.

Create Query (Has API Key, No query_id)

bash

curl -X POST "https://api.allium.so/api/v1/explorer/queries" \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: $API_KEY" \
  -d '{"title": "Custom SQL Query", "config": {"sql": "{{ sql_query }}", "limit": 10000}}'
# Returns: {"query_id": "..."}
# Append to ~/.allium/credentials

Step 0: Check Supported Chains (REQUIRED)

Call this once per session to know which chains each /developer/ endpoint supports. Cache the result — it covers all endpoints. Skip for Explorer SQL and Docs endpoints.

bash

curl "https://api.allium.so/api/v1/supported-chains/realtime-apis/simple"

Returns { "/api/v1/developer/prices": ["ethereum", "solana", ...], ... } — a map of endpoint → supported chains. Use it to:

Validate the chain before calling. Wrong chain = silent empty result or error.
Discover which endpoints cover a chain the user asks about.

Show full SKILL.md (168 more words)Show less

Pick Your Endpoint

Wrong choice wastes a call. Match the task:

You need	Hit this
Supported chains	`GET /api/v1/supported-chains/realtime-apis/simple`
Current price	`POST /api/v1/developer/prices`
Price at timestamp	`POST /api/v1/developer/prices/at-timestamp`
Historical OHLCV	`POST /api/v1/developer/prices/history`
Token stats	`POST /api/v1/developer/prices/stats`
Token info by address	`POST /api/v1/developer/tokens/chain-address`
List tokens	`GET /api/v1/developer/tokens`
Search tokens	`GET /api/v1/developer/tokens/search`
Wallet balances	`POST /api/v1/developer/wallet/balances`
Wallet balances history	`POST /api/v1/developer/wallet/balances/history`
Wallet transactions	`POST /api/v1/developer/wallet/transactions`
Wallet PnL	`POST /api/v1/developer/wallet/pnl`
Custom SQL	`POST /api/v1/explorer/queries/{query_id}/run-async`
Browse docs	`GET /api/v1/docs/docs/browse`
Search schemas	`GET /api/v1/docs/schemas/search`
Browse schemas	`GET /api/v1/docs/schemas/browse`

Common Tokens

Don't guess addresses. Use these:

Token	Chain	Address
ETH	ethereum	`0x0000000000000000000000000000000000000000`
WETH	ethereum	`0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`
USDC	ethereum	`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`
USDC	base	`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`
cbBTC	ethereum	`0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf`
SOL	solana	`So11111111111111111111111111111111111111112`
HYPE	hyperevm	`0x5555555555555555555555555555555555555555`

Chain names are lowercase. ethereum, base, solana, arbitrum, polygon, hyperevm. Uppercase fails silently.

Quick Examples

Current Price

bash

curl -X POST "https://api.allium.so/api/v1/developer/prices" \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: $API_KEY" \
  -d '[{"token_address": "0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf", "chain": "ethereum"}]'

Historical Prices (Last 7 Days)

Format matters. Not token_address + chain — use addresses[] array:

bash

END_TS=$(date +%s)
START_TS=$((END_TS - 7*24*60*60))

curl -X POST "https://api.allium.so/api/v1/developer/prices/history" \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: $API_KEY" \
  -d "{\"addresses\": [{\"token_address\": \"0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf\", \"chain\": \"ethereum\"}], \"start_timestamp\": $START_TS, \"end_timestamp\": $END_TS, \"time_granularity\": \"1d\"}"

moonpay-check-wallet — Check MoonPay wallet balances before querying on-chain
moonpay-swap-tokens — Act on findings by swapping tokens
moonpay-x402 — Pay-per-request API access via x402 micropayments

Files

Just SKILL.md in skills/allium-onchain-data of moonpay/skills.

Open the folder on GitHubat commit aa672ab

Compare with similar skills

Allium Onchain Data next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Allium Onchain Data compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Allium Onchain Data this skillmoonpay/skills	113	—	~1.9k	Automated safety check: Pass	MIT	28 days ago
Fizz Convertpashov/skills	1.2k	2 repos	~3.7k	Automated safety check: Pass	MIT	3 days ago
Solana Devsolana-foundation/solana-dev-skill	574	—	~3.8k	Automated safety check: Pass	MIT	today
Feynman Auditor0xiehnnkta/nemesis-auditor	243	1 repos	~11k	Automated safety check: Pass	MIT	6 mo ago
Smart Contract Auditgreatpie/smart-contract-audit-skill	101	—	~1.1k	Automated safety check: Pass	None	7 mo ago
RadarAuditware/radar	154	—	~2.1k	Automated safety check: Pass	GPL-3.0	1 mo ago

Similar skills

Fizz Convert
pashov/skills
Convert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes.
1.2k GitHub starsUsed in 2 repos~3.7k tokens
Backend & APIsAuto-check passed
Solana Dev
solana-foundation/solana-dev-skill
A skill your agent uses when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "fuzz my…
574 GitHub stars~3.8k tokensUpdated today
Backend & APIsAuto-check passed
Feynman Auditor
0xiehnnkta/nemesis-auditor
Deep business logic bug finder using the Feynman technique. An agent skill from 0xiehnnkta/nemesis-auditor.
243 GitHub starsUsed in 1 repo~11k tokens
Backend & APIsAuto-check passed
Smart Contract Audit
greatpie/smart-contract-audit-skill
Script-backed, out-of-box auditing workflow for Solidity/EVM repositories based on EVMbench detect/patch/exploit methodology.
101 GitHub stars~1.1k tokensUpdated 7 mo ago
Backend & APIsAuto-check passed
Radar
Auditware/radar
Use radar for smart contract security analysis, AST generation, and detection template development.
154 GitHub stars~2.1k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed
Solidity Auditor
Gabson0x/bountyforge
Security audit of Solidity code while you develop. An agent skill from Gabson0x/bountyforge.
443 GitHub stars~3.7k tokensUpdated 21 days ago
Backend & APIsAuto-check passed

Questions about Allium Onchain Data

What does Allium Onchain Data do?

Query blockchain data via Allium APIs. An agent skill from moonpay/skills. Allium Onchain Data is an agent skill from moonpay/skills. Query blockchain data via Allium APIs.

When should I use Allium Onchain Data?

Allium Onchain Data fits situations like: user asks about crypto prices; wallet contents; on-chain analytics.

How do I install Allium Onchain Data in Claude Code?

Run `npx skills add moonpay/skills --skill allium-onchain-data -a claude-code`. Or copy the skill folder (skills/allium-onchain-data in moonpay/skills) into .claude/skills/allium-onchain-data in your project. Claude Code loads it when a task matches its description.

How do I install Allium Onchain Data in Codex?

Run `npx skills add moonpay/skills --skill allium-onchain-data -a codex`. Or copy the skill folder (skills/allium-onchain-data in moonpay/skills) into .agents/skills/allium-onchain-data in your project. Codex loads it when a task matches its description.

Can I use Allium Onchain Data in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add moonpay/skills --skill allium-onchain-data -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/allium-onchain-data, .gemini/skills/allium-onchain-data, .github/skills/allium-onchain-data and .opencode/skills/allium-onchain-data in your project.

What does Allium Onchain Data need to run?

Going by SKILL.md and its folder, Allium Onchain Data needs the command-line tools its instructions call (curl) and credentials named API_KEY. Our summary lists: A credential in API_KEY.

Does Allium Onchain Data access the network?

SKILL.md names 1 domain. In commands or code: api.allium.so; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Allium Onchain Data safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Allium Onchain Data use?

Allium Onchain Data is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Allium Onchain Data use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Allium Onchain Data?

Skills that share tags, products or a category with Allium Onchain Data: Fizz Convert (pashov/skills, 1.2k stars), Solana Dev (solana-foundation/solana-dev-skill, 574 stars), Feynman Auditor (0xiehnnkta/nemesis-auditor, 243 stars) and Smart Contract Audit (greatpie/smart-contract-audit-skill, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Allium Onchain Data?

moonpay (a GitHub organization) maintains it in moonpay/skills, which has 113 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 10, 2026.

Source: moonpay/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Allium Onchain Data

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Allium Blockchain Data

Prerequisites

Credentials

Register (No API Key)

Create Query (Has API Key, No query_id)

Step 0: Check Supported Chains (REQUIRED)

Pick Your Endpoint

Common Tokens

Quick Examples

Current Price

Historical Prices (Last 7 Days)

Related Skills

Files

Compare with similar skills

Similar skills

More from moonpay/skills

Related

Questions about Allium Onchain Data