allium-labs
- 10 skills
- 0 followers
- 11 hours ago last updated
- ▌ Alchemy API · allium-labs bundleWire Alchemy into application code (server, backend, dApp, script) using a standard API key. Preferred app-integration path for normal server/backend usage. Covers EVM JSON-RPC, WebSocket subscriptions, Simulation, Webhooks/Notify, Solana RPC, Solana DAS, Solana Yellowstone gRPC, Sui gRPC, Wallets/Account Kit, Account Abstraction, and operational topics. Requires `$ALCHEMY_API_KEY`. For app code without an API key (autonomous agent paying per-request, or explicit x402/MPP), use `alchemy-agentic-gateway` instead.
- ▌ Allium Data · allium-labs bundleQuery blockchain data using the allium CLI. Two products: Explorer (SQL analytics on Allium's data warehouse — any table, any timeframe, 150+ chains) and Realtime (3-5s freshness lookups for prices, balances, transactions, PnL, positions across 80+ chains). Supports API key, x402 micropayments, and Tempo MPP.
- ▌ Dex Analysis · allium-labsMethodology playbook for analyzing DEX/AMM trade, liquidity, and pricing data on Allium — Uniswap, PancakeSwap, PumpSwap/Pump.fun, Orca, Pendle, aggregators (0x, 1inch), and perp DEXs like Hyperliquid. Use whenever a question touches swap volume, trade counts, liquidity positions, impermanent loss, aggregator fee/routing analysis, or DEX-derived token prices — even if the user just names a protocol or asks why a number "looks off" compared to a known reference. Covers the per-hop double-counting, protocol-vs-project grouping, and fee-leg reconstruction pitfalls that come up repeatedly before you write the SQL.
- ▌ Rwa Analysis · allium-labsMethodology playbook for analyzing tokenized real-world assets (RWA) on Allium — tokenized treasuries, money market funds, tokenized equities/pre-IPO stocks, commodities, and private credit. Use whenever a question touches RWA supply, AUM, market cap, holders, mint/burn activity, or classification — even if the user just says "tokenized treasuries," "BUIDL," "tokenized stocks," "money market fund AUM growth," or names a specific RWA product/issuer. Covers the aggregation mistakes, classification pitfalls, and data-quality exclusions that come up repeatedly in real RWA questions before you write the SQL.
- ▌ Data Matching · allium-labsMatch an analytical question to the right Allium table, metric, dashboard, or realtime endpoint. Required when selecting a new data source for a query or analysis: define the intended meaning, compare schema candidates, test coverage, and record the fit and caveats before treating a source as correct. Run this before `allium-investigation` or any other analysis.
- ▌ Bridge Analysis · allium-labsMethodology playbook for analyzing cross-chain bridge and messaging-protocol data on Allium — CCTP, LayerZero, Wormhole, Across, canonical/application bridges, and general lock-and-mint flows. Use whenever a question touches bridge transfer volume, net flows between chains, tracing a specific cross-chain transaction, or attributing bridge activity to a protocol/integrator — even if the user just names a bridge or asks to "trace this transfer across chains." Covers the direction/double-counting mechanics and non-EVM tracing gap that come up repeatedly before you write the SQL. Distinct from a formal third-party coverage benchmark (see bridge-protocol-coverage-assessment for that) — this is the lighter-weight reference for getting an individual bridge query right.
- ▌ Lending Analysis · allium-labsMethodology playbook for analyzing DeFi lending protocol data on Allium — Aave, Morpho, Fluid, Euler, Maple, Compound-style forks, and per-chain lending markets. Use whenever a question touches deposits, borrows, liquidations, collateral swaps, utilization, TVL, or leverage on a lending protocol — even if the user just names a protocol/asset or asks to compare two lending metrics tables. Covers the table-per-event-type join gotchas, column-naming inconsistencies, and liquidation-fill double-counting that come up repeatedly before you write the SQL.
- ▌ Stablecoin Analysis · allium-labsMethodology playbook for analyzing stablecoin volume, supply, holders, and geographic usage on Allium — USDC, USDT, DAI, USDS, RLUSD, USDG, JPYC, and other fiat/crypto/ algorithmic-backed stablecoins. Use whenever a question touches stablecoin transfer volume, circulating supply, wallet/holder counts, geo splits, or cross-chain deployments — even if the user just names a specific stablecoin, asks for "adoption" or "usage" numbers, or asks to compare volume to a chart/number they already have. Covers the raw-vs-adjusted volume distinction, chain-specific double-counting mechanics, and address/case-sensitivity gotchas that come up repeatedly before you write the SQL.
- ▌ Allium Investigation · allium-labsInvestigate an onchain entity, protocol, market, or wallet question with Allium. Use when the task needs a defensible analytical answer rather than a one-off lookup: check Terminal for existing coverage, select the right source, build the method from a small test to production, validate the result, make calibrated claims, and save reproducible Explorer queries (with an optional dashboard hand-off prompt for Allium Assistant). Chains after `data-matching` (source selection) rather than repeating it.
- ▌ Alchemy Agentic Gateway · allium-labs bundleWire Alchemy into application code without an API key, using the x402 or MPP gateway with wallet-based auth (SIWE/SIWS) and per-request payments (USDC via x402, or USDC/credit-card via MPP). Specialized app-integration path. Use when the user is building application code AND no API key is available, or they're an autonomous agent that needs to pay for itself, or they explicitly want x402/MPP. For normal app code with an Alchemy API key, use `alchemy-api`.