AssetFable integrations
A portfolio spanning wallets, NFTs, exchanges, and graded cards cannot come from one data source. Blockchains provide public ownership and transaction records, RPC and indexing services make them usable, marketplaces add NFT context, price services provide references, and exchanges expose private account data through authorized APIs.
AssetFable connects those layers while keeping the source visible. The documented landscape includes EVM networks, Solana and Bitcoin flows, read-only exchange connections, and market, explorer, NFT, and IPFS services. Actual availability depends on product status, region, platform, and provider coverage.
Each source has a limited job; no single provider is treated as the sole truth for an entire portfolio.
EVM ecosystems such as Ethereum, Base, Polygon, Optimism, and Arbitrum, together with documented Solana and Bitcoin flows, support public wallet, token, NFT, and transaction context. Other chains can depend on enabled coverage.
Depending on the feature, services such as Alchemy, Helius, Zerion, CoinGecko, DexScreener, Moralis, PublicNode, Pyth, Chainlink, or explorer-compatible APIs may enrich records. Their scope and update times differ.
OpenSea, Magic Eden, PancakeSwap NFT, IPFS gateways, Pinata, and other enabled sources may provide collection, listing, image, and metadata context. The contract and network remain authoritative for on-chain ownership.
The documented exchange scope mentions Bitpanda, Binance, Coinbase, and OKX with read-only access. Graded cards may use eBay references and other market records without turning them into binding appraisals.
The flow depends on whether information is public or requires an account connection you authorize.
A public wallet address follows a different data path from a private exchange account or a physical card. AssetFable maps network, provider, and asset type separately rather than forcing every record through one interface.
Public blockchain records do not need a private key. Exchange APIs are intended for read-only credentials. Wallets, marketplaces, and buy or swap providers present their own approvals and terms when you leave AssetFable.
Review sync time, network, and provider when a value looks unexpected. Refresh after temporary errors and compare with an explorer or original provider when ownership, balance, or transaction status is important.
Providers can change APIs, pricing, supported regions, rate limits, and terms. AssetFable cannot guarantee an external system.
Public blockchain requests and private account connections have different privacy implications. Use minimum read-only exchange permissions and revoke credentials directly with a provider when they are no longer needed.
Wallets, NFTs, prices, exchanges, and graded cards require different kinds of information. Specialized sources provide broader context, while making provider, timestamp, and origin information more important.
No. Features can vary by region, platform, plan, network status, provider coverage, or product phase. This page describes the documented integration framework; the current app state is the operational source.
No. AssetFable does not ask for seed phrases, private keys, or recovery data. Public wallet requests use public addresses, and any transaction approval happens in your own wallet.
Compare data type, permission, and provider limits first, or open the app to see the current integration status.
