Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Learn about Moralis and Web3 development. Invoked without a question, gives a friendly platform walkthrough — what's available, what data you can fetch, and...
Learn about Moralis and Web3 development. Invoked without a question, gives a friendly platform walkthrough — what's available, what data you can fetch, and...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
If the user invokes /learn-moralis with no question (or just says "learn moralis"), respond with a friendly platform overview. Walk them through: What Moralis is (enterprise Web3 data platform) The two skills available and when to use each: @moralis-data-api (136 endpoints) — query wallet balances, tokens, NFTs, DeFi positions, prices, transactions, analytics. Use for "what is the current/historical state?" @moralis-streams-api (20 endpoints, EVM only) — real-time EVM event monitoring via webhooks. Use for "notify me when something happens" Supported chains: 40+ EVM chains for both skills, Solana for Data API only How to get started: set MORALIS_API_KEY in .env, then use the skill that fits their need Keep it conversational and concise — think "onboarding tour", not "dump the docs". End by asking what they'd like to build so you can point them to the right skill. If the user invokes /learn-moralis with a specific question, answer that question directly using the knowledge below, then route them to the appropriate technical skill.
Moralis is an enterprise-grade Web3 data infrastructure platform providing: Data APIs - Query wallet balances, tokens, NFTs, DeFi positions, prices, transactions Streams - Real-time EVM event monitoring via webhooks (EVM chains only, no Solana) Datashare - Export historical data to Snowflake, BigQuery, S3 Data Indexer - Custom enterprise indexing pipelines RPC Nodes - Direct blockchain node access Key Stats: Powers 100M+ end users, 2B+ monthly API requests, 50+ supported chains.
After answering a general question, route users to the appropriate skill: User NeedRoute ToQuery wallet data (balances, tokens, NFTs, history)@moralis-data-apiGet token prices, metadata, analytics@moralis-data-apiQuery NFT metadata, traits, floor prices@moralis-data-apiGet DeFi positions, protocol data@moralis-data-apiQuery blocks, transactions@moralis-data-apiReal-time wallet monitoring (EVM)@moralis-streams-apiReal-time contract events (EVM)@moralis-streams-apiWebhooks for EVM on-chain events@moralis-streams-apiTrack EVM transfers as they happen@moralis-streams-api Rule of thumb: Data API = "What is the current/historical state?" Streams = "Notify me when something happens"
QuestionAnswerSkillGet wallet token balances?Yes, with USD prices@moralis-data-apiGet wallet NFTs?Yes, with metadata@moralis-data-apiGet wallet transaction history?Yes, decoded@moralis-data-apiGet token prices?Yes, real-time + OHLCV@moralis-data-apiGet NFT floor prices?Yes (ETH, Base, Sei)@moralis-data-apiGet DeFi positions?Yes (major chains)@moralis-data-apiMonitor wallets in real-time?Yes (EVM only)@moralis-streams-apiTrack contract events live?Yes (EVM only)@moralis-streams-apiGet historical events?Use Data API queries@moralis-data-apiENS/Unstoppable domain lookup?Yes@moralis-data-apiToken security scores?Yes@moralis-data-apiDetect snipers/bots?Yes@moralis-data-apiGet trending tokens?Yes@moralis-data-apiGet top tokens by market cap?Yes@moralis-data-apiSearch tokens by name/symbol?Yes@moralis-data-api
Execute transactions (read-only APIs) Provide private node access (use RPC Nodes product separately) Index custom smart contracts (use Data Indexer product) Store user data (you handle storage) Provide testnet price data (only mainnet prices)
ChainChain IDNotesEthereum0x1All APIs including floor pricesBase0x2105All APIs including floor pricesPolygon0x89Missing only floor pricesBSC0x38No profitability, no floor pricesArbitrum0xa4b1No profitability, no floor pricesOptimism0xaNo profitability, no floor pricesAvalanche0xa86aNo profitability, no floor pricesSei0x531Nearly full (no profitability), includes floor pricesMonad0x8fNew chain, good support
Linea, Fantom, Cronos, Gnosis, Chiliz, Moonbeam, Moonriver, Flow, Ronin, Lisk, Pulse
Mainnet and Devnet supported via @moralis-data-api only. Streams does not support Solana. Use __solana suffix endpoints.
Blast, zkSync, Mantle, opBNB, Polygon zkEVM, Zetachain
PlanMonthly CUsThroughputPriceFree40K/day1,000 CU/s$0Starter2M1,000 CU/s$49/moPro100M2,000 CU/s$199/moBusiness500M5,000 CU/s$490/moEnterpriseCustomCustomContact Compute Units (CUs): Each API call costs CUs based on complexity. Simple queries ~1-5 CUs, complex queries ~10-50 CUs. Overages: Starter $11.25/M, Pro $5/M, Business $4/M Free tier includes: All APIs (Wallet, Token, NFT, Price, DeFi, Blockchain, Streams)
Sign up: https://admin.moralis.com/register Get API key: Dashboard → API Keys Set up .env: Add MORALIS_API_KEY=your_key to your .env file (the skill will help you create it) Use skill: Ask what you want to build — the skill will check for your key and guide you
Need: Display user's tokens, NFTs, balances, and transaction history. Solution: @moralis-data-api endpoints: getWalletTokenBalancesPrice - Token balances with prices getWalletNFTs - NFT holdings getWalletHistory - Decoded transaction history getWalletNetWorth - Total portfolio value
Need: Export transaction history with cost basis. Solution: @moralis-data-api endpoints: getWalletHistory - All transactions decoded getWalletProfitability - Realized gains/losses
Need: Display NFT metadata, traits, prices, and ownership. Solution: @moralis-data-api endpoints: getNFTMetadata - Full metadata + traits getNFTFloorPriceByContract - Floor price getNFTOwners - Current holders getNFTTrades - Sale history
Need: Show user's DeFi positions across protocols. Solution: @moralis-data-api endpoints: getDefiPositionsSummary - All positions getDefiPositionsByProtocol - Protocol-specific data
Need: React to on-chain events in real-time. Solution: @moralis-streams-api: Create stream with topic0 for target events Receive webhook when event occurs Process and act on data
Need: Token prices, holders, trading volume, security scores. Solution: @moralis-data-api endpoints: getTokenPrice - Current price getTokenAnalytics - Volume, liquidity getTokenHolders - Holder distribution getTokenScore - Security analysis
ScenarioUseDisplay current wallet balanceData APIAlert when balance changesStreamsShow transaction historyData APILog every new transactionStreamsGet NFT metadataData APINotify on NFT transferStreamsQuery token priceData APITrack DEX swaps liveStreams
Most Data API endpoints respond quickly. However, response times can vary based on: Query complexity: Simple lookups (balance, price) are fastest. Decoded endpoints (wallet history, DeFi positions) do more processing. Wallet size: Wallets with large transaction histories take longer. Use pagination with smaller limits for whale/power-user wallets. Chain: Response times vary across chains. Some chains are inherently slower than others.
For production applications, set client-side timeouts to 30s to handle edge cases. Most requests return much faster, but large wallets or slower chains can occasionally take longer. For detailed optimization guidance, see @moralis-data-api → references/PerformanceAndLatency.md.
For detailed information: references/FAQ.md - Common questions and answers references/ProductComparison.md - Detailed feature comparison references/UseCaseGuide.md - Implementation patterns by use case
Docs: https://docs.moralis.com Discord: Community support Forum: https://forum.moralis.io Stack Overflow: Tag moralis
After answering a question, always suggest the next action: If user needs to query data: "Use @moralis-data-api — make sure your MORALIS_API_KEY is set in your .env file, then I can help you fetch the data." If user needs real-time events: "Use @moralis-streams-api — make sure your MORALIS_API_KEY is set in your .env file and have your webhook URL ready, then I can help set up the stream." If user is exploring: Suggest specific endpoints based on their use case.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.