Skip to main content
Numbers come back as plain JSON numbers, not strings. Floating-point values are truncated, not rounded, at the API edge. The displayed value never overstates the real one.

​
Precision

​
Truncated, not rounded

97.9488... becomes 97.94, not 97.95. -12.345 becomes -12.34. Always toward zero. Need stricter precision for accounting? Compute from the source data. The edge value is display-safe, not accounting-grade.

​
Integer fields

These are exact integers. No decimals, no truncation:
  • markets_traded
  • rank
  • whale_trade_count

​
Nulls and unavailable

Many fields are nullable (e.g. strategy_type, best_category). Treat them as nullable even when an endpoint usually populates them. Newer builder endpoints also return trust metadata: explicit unavailable or partial markers when a provider-owned value can’t be returned at request time. Don’t convert these into 0, [], or {}. Read the metadata field and treat the value as missing.