Oi Cap Exceeded

Type URI: https://docs.rip.bet/errors/oi-cap-exceeded

What it means

The order would push projected open interest on the asset past the configured per-asset OI cap. HIP-3 requires per-asset notional caps of at least max($1,000,000, 0.5 × current OI), and RIPBET enforces them at the API boundary before the order is relayed to Hyperliquid. The HTTP status is 403 Forbidden.

The response carries extension fields you can show to the user or log: asset, current_oi_usd, projected_oi_usd, and oi_cap_usd.

When you might see this

• POST /v1/orders (and the prediction-package endpoint POST /v1/predict) for an opening order on NYCTMP1 or NYCTMP2 when the resulting notional would exceed the asset's cap.
• Closing or reducing positions does not produce this error; only orders that increase open interest are checked.

How to resolve

• Reduce the order size so that projected_oi_usd stays at or below oi_cap_usd, then retry.
• Wait for other participants to close positions and refresh GET /v1/markets to see the updated oi and cap before retrying.
• If the cap itself is too low for legitimate flow, ask an operator to raise it via ripbet-ops set-oi-cap. Caps are only raised in HIP-3-compliant increments and require a deployer action.
• Surface current_oi_usd, projected_oi_usd, and oi_cap_usd in the client UI so traders understand why the order was rejected.