Quickstart

In this quickstart you read a fund token’s metadata, find a fund’s address, and get the fund token’s latest price and its history. Every call is a read: it changes nothing, and it needs no account or API key. You need: a terminal with curl. The last step also shows a call in JavaScript (Node.js 18 or later).

The funds you can read today are the funds of Starke’s public beta, on Solana mainnet. They are offered only within the public beta program, for protocol testing and feedback, and are not an investment product.

1. Read a fund token’s metadata

Each fund has its own token, and each token has a symbol. Ask for the metadata of rkBlueChip, the token of the rkShares Blue Chip Beta fund:

curl "https://api.starke.finance/v1/vaults/metadata/rkBlueChip"

The API answers with the token’s name, symbol, description and image URL:

{
  "name": "…",
  "symbol": "rkBlueChip",
  "description": "…",
  "image": "https://…"
}

Wallets and explorers read this same URL to show the token: it is the metadata URL written on-chain in each fund token.

2. Find a fund’s address

The other fund reads take the fund’s address, its account on Solana. To find it, open the fund from the Starke app’s fund list: the fund page’s URL ends with it.

https://app.starke.finance/funds/<fund address>

Copy that last part. The examples below write it as <fund address>.

3. Get the fund token’s latest price

curl "https://api.starke.finance/v1/vaults/vtoken-prices?ids=<fund address>"

The answer is keyed by fund address. It looks like this (the values are an example):

{
  "<fund address>": {
    "name": "rkShares Blue Chip Beta",
    "symbol": "rkBlueChip",
    "mint_id": "<fund token address>",
    "uri": "https://api.starke.finance/v1/vaults/metadata/rkBlueChip",
    "aum_usd": 28105.125,
    "supply": 25000,
    "price_usd": 1.124205
  }
}

aum_usd: the fund’s value, in US dollars.
supply: the number of fund tokens in circulation.
price_usd: the price of one fund token, in US dollars.
mint_id: the fund token’s address on Solana.

To read several funds at once, pass up to 50 addresses, separated by commas.

4. Get the price history

Add a time window and the spacing of the points:

curl "https://api.starke.finance/v1/vaults/vtoken-prices/history?ids=<fund address>&start_time=2026-11-01T00:00:00Z&end_time=2026-11-08T00:00:00Z&granularity=1day"

Times are ISO 8601 in UTC, ending in Z. granularity is 15mins, 1hour or 1day. The answer lists each fund’s price points, oldest first. The same call in JavaScript:

const params = new URLSearchParams({
  ids: "<fund address>",
  start_time: "2026-11-01T00:00:00Z",
  end_time: "2026-11-08T00:00:00Z",
  granularity: "1day",
});

const response = await fetch(
  `https://api.starke.finance/v1/vaults/vtoken-prices/history?${params}`,
);

if (!response.ok) {
  // Only a validation error (400) has a JSON body; the others are plain text.
  throw new Error(`${response.status}: ${await response.text()}`);
}

const history = await response.json();
console.log(history["<fund address>"]);

When a call fails

Check the HTTP status first. A 400 for a missing or invalid query parameter has a JSON body that names each parameter; every other error has a short plain-text body. Errors lists them all.

Architecture: where these numbers come from.
Transaction model: how a deposit or a redemption reaches the chain, and how to tell when the API shows it.
API reference: every read the API offers.

Overview

Guides

API reference

Endpoints

Explanation

1. Read a fund token’s metadata

2. Find a fund’s address

3. Get the fund token’s latest price

4. Get the price history

When a call fails

Next

​1. Read a fund token’s metadata

​2. Find a fund’s address

​3. Get the fund token’s latest price

​4. Get the price history

​When a call fails

​Next

1. Read a fund token’s metadata

2. Find a fund’s address

3. Get the fund token’s latest price

4. Get the price history

When a call fails

Next