Practical overview
When it fits
Use it when a .NET application needs to call Jupiter’s Solana API and the application will handle wallet signing and transaction submission where required.
Who it is for
- C# and .NET developers integrating Jupiter API features into an application.
- Teams building Solana token-data, swap, portfolio or order-management workflows.
Documented uses
- Fetch token prices, 24-hour changes and liquidity.
- Search tokens and retrieve metadata, tags and token lists.
- Request swap quotes and obtain unsigned transactions or raw instructions for caller-side signing.
- Retrieve Jupiter product positions and staked JUP.
- Create, update, cancel and inspect limit orders and DCA orders through Trigger V2.
Requirements & limits
The library is MIT-licensed. Setup requires the .NET 8 SDK. The README says a Jupiter API key is free; Tokens V2 and Portfolio require one. Keyless calls are limited to 0.5 requests per second, compared with 1 request per second with a key. Trigger V2 also uses a challenge-response JWT valid for 24 hours, with no refresh endpoint described.
- The library is an HTTP client and does not include a Solana SDK; transaction signing remains the caller’s responsibility.
- A Solana wallet secret key is needed only to sign real swaps or orders.
- Portfolio V1 is labeled beta, and the repository describes its public API as pre-release.
- Trigger V2 adds challenge-response authentication on top of the Jupiter API key.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build the .NET library and request token prices
Compile the library and make the documented C# price lookup.
Before you start
- .NET 8 SDK
- The Solgrid.Jupiter repository
Steps
Clone the repository.
Change to the src directory and run
dotnet build -c Release.Create a
JupiterSwapClientand callGetPricesAsyncwith a mint address, as shown in the README.
Expected outcome
A built library and a C# example that requests token prices through Jupiter.
Guide limitations
- The README describes the API as pre-release and subject to change before 1.0.0.
- Tokens V2 requires a Jupiter API key; the README's price example marks the key optional.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- solgrid-development/Solgrid.Jupiter · Official homepage title · retained in its source language

