Start here when the problem is simple: you have one or more wallet addresses, and you need a file someone can inspect before tax software or professional review.
This workflow is not about final tax classification. It is about preserving the raw export, normalizing a readable CSV, and checking enough transaction hashes to know where the gaps are.
Use this when
- You have public wallet addresses, not exchange credentials.
- The immediate output should be a CSV or evidence pack.
- You need questions for an accountant, not a finished tax report.
What the workflow should produce
- Raw API response kept as an archive.
- Normalized CSV with transaction hashes and chain notes.
- A small sample of hashes checked against explorers.
- A short list of missing fields, uncertain labels, and questions.
Minimum setup
- Create a Moralis API key and keep it outside the prompt history.
- Check the current Moralis Data API supported-chain page before choosing the chain parameter.
- Ask Codex to write a small script that stores raw JSON first, then transforms a copy into CSV.
Skill to package next
crypto-tax-wallet-export: input wallet addresses and chain names, call the provider API, write raw/, exports/, and review/checklist.md.
Moralis docs expose an llms.txt index, which makes this a good candidate for an AI-assisted “read the docs first” prompt before writing code. Treat endpoint names and feature coverage as source-checked inputs, not assumptions.
Check before trusting it
Verify current Moralis endpoints, chain coverage, pricing, and limits before using this with a client file. Do not ask readers to paste private keys, seed phrases, exchange credentials, or sensitive client data into an AI tool.
