SCRY / PRIORITY FEES API

Check Solana priority fees before you send

Prepare a Solana priority-fee request for the network, Jupiter, Raydium or your own account keys.

Payment
USDC on Solana or Base
Response
Fee levels + timestamps
Cache
20 seconds

01 / REQUEST

Which context does your workflow need?

This selector only prepares a URL and a command. This page makes no API request, connects no wallet and initiates no payment.

Which context does your workflow need?

Jupiter and Raydium use fixed program addresses. They do not automatically represent the exact writable accounts in your transaction.

1–150 slots; default: 50. This is the slot window considered, not an age in seconds.

Global context · 50 slots · ready to copy

Your request URL

https://scry.solanahub.de/x402/network/priority-fees-live?preset=global&lookback_slots=50

1. Inspect the payment offer

curl -q --silent --show-error --include --max-time 10 --max-redirs 0 --proto '=https' --request GET 'https://scry.solanahub.de/x402/network/priority-fees-live?preset=global&lookback_slots=50'

This ordinary curl request has no payment header. Expect HTTP 402 with the offer, not the paid fee response. This page does not execute the command.

2. Request it with your x402 client

Use the same URL in an already configured x402-capable client. Inspect the offer and select one supported network: Solana or Base, both in USDC.

Maximum API payment budget

5000 atomic USDC

5000 atomic USDC units = 0.005 USDC for one request. Stop if the price, network, recipient or resource differs from the offer you reviewed. No automatic retry or second payment.

Your x402 client handles payment within your budget and then receives the actual JSON response. The curl command above is not a payment client.

Client workflow and API contract

02 / USE THE RESPONSE

From the response to your own fee budget

The response contains levels from min to unsafeMax and a recommended value from the source. The unit is micro-lamports per compute unit (CU). You need the CU limit actually requested by your transaction to turn this into a priority fee.

Evaluate an existing response locally

The free standalone Node helper checks a chosen fee level, budget, scope and response age for legacy and v0 transactions. It uses exact integer arithmetic and does not buy, sign or submit anything.

Check timestamps before each use

Responses may be cached for up to 20 seconds. Check source_updated_at and coverage.last_refreshed_at against your own age limit; a new response-generation timestamp does not make old source data fresh.

What the result tells you

Fee context
A network- or account-scoped fee snapshot with coverage. It does not simulate your final transaction or guarantee inclusion.
Two separate costs
0.005 USDC pays for the Scry API request. The priority fee is calculated separately in SOL. Base fees, rent, tips and transaction value are not included.
Examples stay examples
The free JSON example is frozen and only shows the response structure. Its numbers are not a current fee quote; the budget helper rejects these examples.