Reference
Public API
Read-only JSON endpoints for coins, gauges, receipts, the $GAUGE burn and the keeper's health.
All read endpoints are public, need no key and return JSON. Amounts are strings of lamports (1 SOL = 1,000,000,000) or token base units, to keep them exact. Times are ISO 8601 in UTC.
#GET /api/coins
Every listed coin with its gauge summary.
{
"coins": [{
"mint": "…pump",
"state": "listed",
"name": "Example",
"symbol": "EXM",
"image": "https://…",
"listedAt": "2026-10-19T03:00:00.000Z",
"vaultLamports": "800740744",
"daysFunded": 36,
"feeCoverageBps": 5938,
"inflow7dLamports": "900740744",
"locked": true,
"sunsetActive": false,
"vaultMode": "locked",
"pendingChanges": 0
}]
}
state is listed or flagged (checks failing). feeCoverageBps is in basis points: 10000 means fees cover the budget exactly.
#GET /api/coins/:mint
One coin in full.
| Field | Contents |
|---|---|
gauge.runway |
Daily cost, days funded, 7-day inflow, fee coverage |
gauge.lines[] |
Each line's label, payee, amount, period, autopay, proof URL, spending limit address, remaining this period, paid so far |
gauge.receipts[] |
Latest vault movements: signature, time, lamports (negative = out), direction, line, payee, memo |
gauge.sunset |
Idle period, idle since, due time, active, sunset wallet, spending limit |
split |
Shareholders with roles, vault and burn basis points, locked |
multisig |
Mode (locked or editable), members with permission masks, threshold, time lock, transaction count |
pendingChanges[] |
Proposed, unexecuted changes on an editable vault |
checks[] |
Each on-chain check: id, ok, required, text |
totals |
Payouts, spends, sunsets, buybacks and burns since listing |
budget |
The budget as published |
Returns 404 for a coin that is not listed.
#GET /api/platform
The $GAUGE burn:
burnWallet,burnWalletLamports;receivedFromCoinsLamports,routedToVaultsLamports,paidToBudgetLinesLamports;buybackLamports,boughtTokens,burnedTokens;log[](recent buys and burns);keeperFresh(the keeper reported within three cycles),keeperAlerts(how many alerts it raised, such as a low balance),keeperOk(both: fresh and no alerts),lastCycleAt.
#GET /api/config
Platform addresses and limits: the keeper and burn wallets, the $GAUGE mint, the platform share in basis points, the maximum number of budget lines, and the time-lock bounds.
#GET /api/health
200 while the keeper has reported within three cycles, 503 otherwise:
{ "ok": true, "keeperFresh": true, "lastCycleAt": "2026-10-19T03:43:46.315Z", "alerts": 0 }
Point an uptime monitor at it.
#Setup endpoints
POST /api/check, /api/vault, /api/attach, /api/split, /api/send, /api/pay and /api/register drive the setup wizard and the pay form. They build transactions for a creator's wallet to sign and relay only setup and budget-payment transactions. They are rate limited per client and are not a stable interface; use the website for them.
#Fair use
Data refreshes every keeper cycle (about ten minutes), so polling more than once a minute gains nothing.