5.2 Hub

The Synaptika Hub is the unified interface through which all participants -- node operators, pool curators, VPI holders, and developers -- interact with the protocol. It serves as both a marketplace for VPI trading and a control plane for managing protocol primitives.

The Hub is designed to lower the barrier to entry for every participant type: node operators register and monitor their infrastructure, curators create and manage pools, and consumers browse, mint, trade, and manage VPIs — all through a single application.

Access to Protocol Primitives

The Hub provides direct access to the protocol’s core operations:

• Node Management: Register nodes, publish capability manifests, monitor health and performance metrics, manage pool commitments, and track earnings.
• Pool Operations: Create pools (for curators), browse available pools, view pool composition and performance, and manage admission criteria.
• VPI Lifecycle: Mint new VPIs against pools, configure inference endpoints, monitor usage and billing, transfer or release VPIs.
• Staking and Governance: Stake Synaptika Tokens, participate in governance votes, and manage delegation.

VPI Marketplace

The centerpiece of the Hub is the VPI Marketplace — a secondary market where VPIs can be listed, traded, and leased. The marketplace creates liquidity for inference capacity, enabling price discovery and efficient allocation of AI compute.

Key marketplace features:

• Model and Pool Discovery: Browse available models across the network, filter by tier, region, latency, and price. Compare pools side-by-side on performance metrics.
• VPI Trading: List VPIs for sale at a fixed price or through auction mechanisms. Buyers can acquire VPIs with immediate capacity activation — no setup required.
• VPI Leasing: Lease idle VPI capacity to other users for a defined duration. Leasing creates yield for VPI holders while providing flexible, commitment-free access for consumers.
• Usage Analytics: Track inference consumption, cost per request, latency distributions, and capacity utilization across all owned VPIs.

The marketplace evolves with the network. In the initial phase, Synaptika operates the marketplace as a curated environment. As the protocol matures and secondary market volume grows, marketplace governance transitions to the community.

Hub FAQ

<details> <summary>Is the Hub the only way to interact with Synaptika?</summary>

No. The Hub is the primary user interface, but all protocol operations are also accessible via API and SDK. Developers building on Synaptika can integrate directly with the protocol without using the Hub’s UI. The Hub serves as the reference client and the default experience for non-technical participants.

</details> <details> <summary>How is VPI pricing determined on the marketplace?</summary>

Primary market pricing (minting) is set at the pool level by the curator. Secondary market pricing is determined by supply and demand — VPI holders set their own listing prices, and buyers decide whether to transact. Over time, marketplace dynamics will establish pricing conventions based on model quality, pool reputation, and capacity scarcity.

</details> <details> <summary>Can I use the Hub without crypto/tokens?</summary>

The Hub is exploring fiat on-ramp integrations for the initial launch to reduce friction for enterprise and developer users. The goal is to make VPI acquisition as simple as a SaaS subscription, with the token mechanics abstracted behind a familiar purchasing experience.

</details>

Hub: Dissenting Opinions

"A VPI marketplace will suffer from low liquidity in the early network."

This is likely true in the first phase. The mitigation strategy is to launch with the primary market (minting against Synaptika-managed pools) as the dominant mechanism, and introduce secondary trading gradually as VPI supply and demand reach sufficient scale. Liquidity bootstrapping programs and market-making incentives are under consideration.

"Enterprise users won’t interact with a token-based marketplace."

Enterprise adoption requires abstracting the token layer behind familiar interfaces — invoicing, SLAs, and account management. The Hub’s enterprise tier is designed to provide this abstraction, where tokens are used under the hood but the user experience mirrors a traditional infrastructure procurement workflow.