An NFT data API in two published versions — a stable V1.1 on Ethereum only, and a newer V2.2 "Multi Chain API" covering eight mainnets — plus GoPricing, a per-token appraisal that returns an estimated price for a specific tokenId decomposed into a collection floor base, an intercept and machine-learned per-trait premiums, and returns the trait weights and intercept themselves so the buyer can re-derive the number. GoPricing is documented only under V1.1 and is Ethereum-only. Wash-trade filtering is default-on in the web product for an enumerated table of metrics but default-OFF in the V1.1 API (exclude_wash_trading defaults to false) and has no exclude parameter at all on the V2.2 transaction-history endpoint, which instead tags each last sale with an is_wash_trade boolean. No accuracy figure, model version or as-of query is published anywhere. Strongest on what the vendor removes before it prints the number (6/10): MORE DISCLOSURE THAN THE POOL NOTE ALLOWS, BUT THE RULE IS NOT RE-DERIVABLE AND THE API DEFAULT IS OFF. A dedicated page exists at https://docs.nftgo.io/docs/wash-trade-filter-1. Under 'Wash Trade Auto Filter' it states verbatim: "To allow for a better and more seamless user experience where users get to see the… Weakest on whether the number is revised after you have used it (5/10): ONE OF THE FOUR ARTEFACTS SHIPS; THE OTHER THREE DO NOT. (1) COMPUTED-AT TIMESTAMP — PRESENT, AND MANDATORY. The PricingItem schema published at https://docs.nftgo.io/reference/get_pricing_pricing_v1_pricing_get reads "PricingItem":{"title":"PricingItem","required":["contract_address","token_id","processed_at"] and… Published price: No price is published on any page I could load.
NFT Analytics
NFT Analytics evaluated across what the vendor removes before it prints the number, what the printed number actually counts, a mark for the token you hold, with a published error, and whether the number is revised after you have used it.
Ranked on 4 published criteria weighted 30/26/24/20, which set goal alignment — 30 of the 86 points. The rest: regional access 20, evidence depth 18, ease of use 10, institutional trust 8. Profile match is shown in breakdowns but carries no weight.
What matters most before choosing in this category
Weighted on what the vendor removes before it prints the number, what the printed number actually counts, a mark for the token you hold, with a published error, and whether the number is revised after you have used it, in that order. THE FILTER EVERY VENDOR ADVERTISES IS SWITCHED OFF EXACTLY WHERE THE NUMBER LEAVES THE BUILDING. Of the six vendors ranked here, exactly one removes inorganic trades from the printed figure by default (CryptoSlam's aria-label tooltip, served on https://www.cryptoslam.io/, /nfts, /collections and /blockchains: "Wash sales are NOT included in Sales (USD) aggregation."). NFTGo's filter is default-ON in the web product for an enumerated 55-entry metric table (https://docs.nftgo.io/docs/wash-trade-filter-1: "the wash trade filter has been automatically turned on for the following key metrics") and default-OFF in the API a buyer actually integrates — the published OpenAPI parameter block reads {"name":"exclude_wash_trading","schema":{"type":"boolean","default":false}}, and the vendor's own tutorial "How to filter out wash trades?" ships its copy-paste sample as "const excludeWashTrading= false;".
Weighted on what the vendor removes before it prints the number, what the printed number actually counts, a mark for the token you hold, with a published error, and whether the number is revised after you have used it, in that order. THE FILTER EVERY VENDOR ADVERTISES IS SWITCHED OFF EXACTLY WHERE THE NUMBER LEAVES THE BUILDING. Of the six vendors ranked here, exactly one removes inorganic trades from the printed figure by default (CryptoSlam's aria-label tooltip, served on https://www.cryptoslam.io/, /nfts, /collections and /blockchains: "Wash sales are NOT included in Sales (USD) aggregation."). NFTGo's filter is default-ON in the web product for an enumerated 55-entry metric table (https://docs.nftgo.io/docs/wash-trade-filter-1: "the wash trade filter has been automatically turned on for the following key metrics") and default-OFF in the API a buyer actually integrates — the published OpenAPI parameter block reads {"name":"exclude_wash_trading","schema":{"type":"boolean","default":false}}, and the vendor's own tutorial "How to filter out wash trades?" ships its copy-paste sample as "const excludeWashTrading= false;".
Expert review and scoring weights
How this category is reviewed
Reviewed on what the vendor strips out before it prints the figure, what that figure actually counts, whether it prices the specific token you hold and admits its error, and whether it restates history after you have used it. Weights are the engine’s: 30 / 26 / 24 / 20.