NFT count thresholds
Use minCount with POST /api/wallet/verify-ownership to require a positive integer count of matching BSV NFTs.
{ "collection": "your-exact-collection-id", "minCount": 3 }The response's owns indicates whether the observed match count reaches the threshold. Your application should validate that its configured threshold is a positive safe integer before making a request. Do not rely on implicit coercion of strings or fractional values.
What is counted
The implementation inspects BSV ordinal origin/collection metadata across connected wallet addresses for the primary profile. It does not sum ERC-20 balances, satoshis, market value, or staking positions. A wallet connector for another chain does not add that chain's NFT verification to this endpoint.
Multiple tiers
Define tiers in your own application using explicit collection/origin selectors and count requirements. Check each criterion through a trusted path and apply a documented rule such as “all required collections” or “any qualifying collection.” There is no generic batch-threshold API or signed entitlement token produced by this route.
Keep authorization checks server-side. A client can change a displayed tier or forge a submitted count. Recheck at an interval appropriate to the operation, and do not grant new access when indexer evidence is incomplete or unavailable.