Your API keys (optional)
Keys are kept only in this browser (localStorage on your device). When you load NFTs, export a ZIP, or pin, they are sent over HTTPS to this site's API routes so the server can call Alchemy and web3.storage on your behalf. They are not stored in a CIDKeeper database. The hosted app relies on small free-tier quotas when you do not add keys, so using your own keys keeps the tool fast for you and fair for everyone. Anyone who can modify or observe this deployment could in theory intercept them, so use provider keys you can rotate and restrict (IP allowlists, usage caps) in the Alchemy and web3.storage dashboards.
Work in progress: Pinning via web3.storage is still being built and tested. Prefer ZIP export and CID analysis for production-style backups until pinning is stable.
How to get your Alchemy API key
CIDKeeper needs an Alchemy key to list NFTs and build ZIP exports. Create a dedicated app in your Alchemy account so you can rotate or cap usage independently. Steps below follow the dashboard in order.
Open Alchemy, go to My Apps, and click Create new app.

Name your app (for example CIDKeeper), add a short description, set the use case to NFTs, then continue.

Choose chains: select Ethereum and the networks you need (for example Ethereum Mainnet).

Activate services: keep the recommended NFT-related APIs selected, then click Create app.

On your app’s setup page, copy the API key and paste it into Alchemy API key above, then save to this browser.

Built-in Foundation factory contracts
- 0x3B612a5B49e025a6e4bA4eE4FB1EF46D13588059
- 0x612E2DadDc89d91409e40f946f9f7CfE422e777E
Additional factory addresses
Add other collection-factory contracts that emit the same indexed event layout. Stored only in this browser (localStorage), up to 24 addresses. Used when the option above is enabled.
No extra factories saved yet.