Bot API
One call before each buy returns what landed in the last window, so your bot can set its priority fee and Jito tip from real numbers. Needs a key with an active plan.
Request
GET /api/v1/fees?size=small&window=60
Authorization: Bearer <your key>
| Parameter | Values | Meaning |
|---|---|---|
size | all, none, small, mid, large | Launch size by the creator's first buy. Default all. |
window | 10, 30, 60, 180 | Minutes back from now. Default 60. |
Response
JSON with one entry per block window under blocks: first, second and first_ten.
| Field | Type | Meaning |
|---|---|---|
from, to | unix seconds | The window measured. |
launches | integer | Launches read in the window. |
buys | integer | Landed buys counted. |
fee | p50, p75, p90 | Priority fee in lamports. |
tip | p50, p75, p90 | Jito tip in lamports. |
total | p50, p75, p90 | Fee plus tip in lamports. |
cu_price | p50, p75, p90 | Compute unit price in micro-lamports. |
tipped | 0 to 1 | Share of buys that paid a Jito tip. |
Percentile fields are null when no buys landed in the window.
History
GET /api/v1/history?size=all&group=first&days=30
Authorization: Bearer <your key>
Finished UTC hours with the same percentiles, flattened: fee_p50, tip_p75, total_p90, cu_p50 and so on. group is first, second or first_ten; days goes up to 30.
Limits and errors
Up to 20 calls per second per key. 401 means a missing or unknown key, 402 a key without an active plan, 429 too many calls.