Get fee estimates

GET /network/fees

What priority fees are

Every Solana transaction pays a tiny base fee (5,000 lamports per signature — about half a cent). Under load, transactions can also attach a priority fee to get scheduled ahead of others. Priced in micro-lamports per compute unit, it's easily the most confusing number in Solana — this endpoint (and the "priorityFee": "auto" option on send) exists so you never compute it by hand.

Example

curl https://api.sarg.am/v1/solana/network/fees \
  -H "Authorization: Bearer $MAINLY_API_KEY"

{
  "baseFee": { "lamportsPerSignature": 5000 },
  "priority": {
    "unit": "microLamportsPerComputeUnit",
    "recommended": 10082,
    "levels": {
      "low": 2,
      "medium": 10082,
      "high": 100000,
      "veryHigh": 1000000
    }
  },
  "updatedAt": "2026-08-04T09:41:12Z"
}

Response fields

Field	Type	Description
`priority.recommended`	number	What we'd attach right now for reliable inclusion without overpaying. Refreshed continuously from recent blocks.
`priority.levels`	object	The current market at four percentiles, if you want to choose your own trade-off.

Scoping the estimate to your transaction

Fee markets are per-account: writing to a hot account (a popular pool, a mint in demand) costs more priority than the global average suggests. For a transaction-specific estimate, POST your draft:

curl -X POST https://api.sarg.am/v1/solana/network/fees/estimate \
  -H "Authorization: Bearer $MAINLY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "transaction": "AeF3...base64...==" }'

The response has the same priority shape, computed from the accounts your transaction actually touches.

If you use "priorityFee": "auto" on send, this happens automatically and you never need this endpoint.

Under the hood

Replaces provider-specific priority fee APIs and getRecentPrioritizationFees, plus the percentile math over recent blocks.