Practical overview
When it fits
Use it when you need an off-chain index and read API for Nuvex account data, or a documented adapter approach for aggregating public price observations. Configure an RPC URL, at least one supported program ID, and a storage destination for the indexer; apply the SQL migrations before connecting the API to PostgreSQL.
Who it is for
- Developers building off-chain read services for Nuvex data.
- Operators configuring an account-indexing pipeline with PostgreSQL or JSON snapshot storage.
- Teams integrating filtered public price observations into a service.
Documented uses
- Decode known Nuvex program account layouts into a PostgreSQL store or JSON snapshot.
- Serve indexed requests, node data, and network counts through an HTTP read API.
- Aggregate fresh public price observations while discarding stale, unsigned, or untimestamped sources.
- Package local infrastructure using the repository's Compose and monitoring configuration.
Requirements & limits
The repository is public and identifies an Apache-2.0 license.
- The indexer requires an RPC URL, at least one program ID, and either DATABASE_URL or NUVEX_READ_MODEL_PATH.
- PostgreSQL API use requires applying the repository's Prisma migration SQL first.
- The price endpoint reports a median of fresh public observations, not an on-chain result; it omits the median when too few sources remain.
- The API documents health and price routes; jobs and models return 501.
- The repository's AI directory contains no model, and its --health option only checks the process.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Configure the indexer inputs
Prepare the required configuration for the documented account-indexing process.
Before you start
- A Solana RPC URL, set as NUVEX_RPC_URL or NUVEX_SOLANA_RPC_URL.
- At least one program ID: NUVEX_ORACLE_CORE_PROGRAM_ID, NUVEX_ORACLE_REGISTRY_PROGRAM_ID, or NUVEX_VERIFICATION_PROGRAM_ID.
- Either DATABASE_URL or NUVEX_READ_MODEL_PATH for storage.
Steps
Set one of the documented RPC URL variables.
Set at least one supported program ID.
Configure either a database URL or a JSON snapshot path.
Expected outcome
The indexer has the required documented inputs to start its account-layout indexing process.
Guide limitations
- The repository states that the process exits with status 2 when these requirements are missing.
- A configured RPC, program ID, and storage destination must be valid for successful operation.
- The --health option checks only the process.
Prepare PostgreSQL for the API
Apply the repository's documented schema migrations before connecting the API to PostgreSQL.
Before you start
- PostgreSQL storage configured through DATABASE_URL.
- The SQL files in indexer/prisma/migrations/.
Steps
Apply the SQL in indexer/prisma/migrations/ to the PostgreSQL database.
Point the API at the PostgreSQL database using its configured connection.
Expected outcome
The database schema is prepared before the API connects to PostgreSQL.
Guide limitations
- The repository says migrations must be applied first.
- The documented make check does not start a database.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 8 October 2026
- Original website title
- NuvexNetwork/nuvex-services · Official homepage title · retained in its source language

