Venue model
Provider-specific schemas remain in server adapters, while components consume one venue-neutral model with source and freshness metadata.
Venue model
Provider-specific schemas remain in server adapters, while components consume one venue-neutral model with source and freshness metadata.
Each adapter validates its upstream payload and returns normalized prices, funding, liquidity proxies, timestamps, and availability. React components do not consume provider-specific schemas.
Operational controls
Identity is chain ID plus contract plus economic underlying. Multipliers are applied before basis and quantity comparisons. Disconnected streams reconnect with bounded backoff.
Limits and risk
Public APIs can be delayed, incomplete, rate-limited, or unavailable. A visible price does not guarantee executable depth.
Missing, stale, or contract-dependent values remain unavailable. Hinge does not insert demo values to complete a calculation.