Rarible Protocol API

WHAT IT DOES The Rarible Protocol API tool fetches NFT data from Rarible's on-chain contracts and off-chain API. You provide a contract address (NFT collection or marketplace), optionally a token ID, and select a data type: collection info (name, symbol, total supply), token details (metadata, URI, image), or active orders (listings from Rarible's orderbook). The tool reads on-chain data via eth_call and fetches order data from the Rarible API endpoint—giving you a unified view of collection data and marketplace activity. HOW TO USE 1. Connect your EVM wallet (optional for collection and token data). 2. Select your chain: Ethereum, Polygon, or Arbitrum. 3. Enter the NFT collection or marketplace contract address. 4. Optionally enter a token ID for token-specific queries. 5. Select a data type: Collection info, Token details, or Active orders. 6. Click "Fetch data" to retrieve on-chain and API data. 7. Review the results in the data panel. THE REAL MECHANISM — on-chain contract reads with Rarible API order integration This tool combines two data sources. First, it reads on-chain data from the provided contract using standard ERC-721 and ERC-1155 interfaces: `name()`, `symbol()`, `totalSupply()` for collection info, and `tokenURI()` for token metadata. It then attempts to fetch the metadata JSON from IPFS or HTTPS using GM_xmlhttpRequest. Second, it queries the Rarible public API (`https://api.rarible.org/v0.1/order/orders/all?collection=&status=ACTIVE`) to fetch active orders/listings for the collection, displaying token IDs and prices. All data is retrieved client-side—no data is stored or transmitted beyond the requests themselves. WHAT IT CANNOT SEE - This tool cannot access order data that is not available via the Rarible API endpoint. - It cannot read collection data from contracts that do not implement standard ERC-721 or ERC-1155 interfaces. - It does not support chains where Rarible is not deployed or the API does not have data. - It cannot automatically authenticate or handle rate limits from the Rarible API. - It cannot fetch token metadata if the tokenURI() points to an unreachable IPFS gateway. - It cannot verify the authenticity of the metadata or the contract—you are responsible for checking the address you enter. PLEASE NOTE - This tool works on Ethereum (1), Polygon (137), and Arbitrum (42161). - You must provide the contract address yourself—this tool does not hardcode any addresses. - The Rarible API is rate-limited and may not return orders for all collections. - Token metadata fetching relies on IPFS gateways; if the gateway is down, metadata may not load. - This tool is read-only and does not submit any transactions.