(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.
What is Moralis?
Moralis is an enterprise-grade Web3 data infrastructure platform providing:
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.
Recommended Timeouts
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.
Reference Documentation
For detailed information:
references/FAQ.md
- Common questions and answers
references/ProductComparison.md
- Detailed feature comparison
references/UseCaseGuide.md
- Implementation patterns by use case
Support Resources
Docs:
https://docs.moralis.com
Discord:
Community support
Forum:
https://forum.moralis.io
Stack Overflow:
Tag
moralis
Next Steps
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.