NFT discovery feed and one-click mint UI that aggregates live drops across EVM chains via a hosted minting protocol.
- 01live mint discovery
- 02embedded one-click mint
- 03minter leaderboards
- 04trending drops feed
- 05FOMO-driven mint surfaces
| Variable | Scope | Description |
|---|---|---|
| MINT_FUN_API_KEY | Server | API key for mint.fun's discovery / leaderboard endpoints (request via team contact). |
Use Mint.fun as a discovery surface and as a hosted mint UI. For the simplest integration, deep-link users to `https://mint.fun/<chain>/<contractAddress>` which renders the canonical mint button across supported drops. To embed trending drops, fetch the feed JSON from `https://mint.fun/api/feed?chain=base` and render contract address + image + mint price client-side. For programmatic mints in your own UI, decode the contract from the feed and call its `mint(address,uint256)` directly via wagmi `useWriteContract` rather than going through mint.fun.
- ⚑Mint.fun does not enforce royalties — it just routes mint calls; royalty behavior depends entirely on the underlying drop contract, so vetting the source contract is on you.
- ⚑Chain coverage shifts with platform priorities — historical drops on chains they later dropped (e.g. Base Goerli, niche L2s) become un-mintable through their UI even if the on-chain contract still works.
- ⚑Their feed API is rate-limited and unauthenticated calls cache aggressively (~60s) — don't build real-time mint sniping off the public endpoint, use direct RPC + contract events.
- ⚑Many featured drops use custom mint configs (signature-gated, allowlist via Merkle, dynamic pricing); the embed handles these but a raw `mint()` call from your own UI may revert with `InvalidProof` if you skip the signature step.
- ⚑Mint.fun's IPFS metadata is mirrored, not pinned — for collectibles you intend to keep, re-pin the original `tokenURI` to your own IPFS provider.