Add-ons
Bundles
A bundle grants several add-ons for one price. A plan holds at most one bundle.
IPFS and WebSocket packages are never part of a bundle. A bundle’s add-ons are enforced exactly like the same add-ons bought separately: the 402 gate, per-key add-on grants and MCP access all see them as active. At checkout, separately selected add-ons that make up a whole bundle are billed as that bundle. On an existing subscription a bundle is always your explicit choice: adding one ends the separate add-ons it covers and charges only the difference.
WebSocket packages
Live streaming is offered separately from add-ons. See WebSocket Streaming.Enabling add-ons
Add-ons, bundles and WebSocket packages are managed from your account. Additions apply immediately and are charged pro-rata for the rest of the billing period; removals take effect at the end of the period.Enterprise includes everything. The Enterprise plan bundles all add-ons and WebSocket Unlimited, with no separate setup.
How access is enforced
When you call an endpoint that belongs to an add-on you haven’t activated, Nexus returns HTTP 402 Payment Required:addon field tells you which add-on to enable. WebSocket access is enforced at connection time instead (see WebSocket Streaming).