Read everything, no key needed.
Every record on NORKI is public, so the API that serves the site is public too. Plain HTTP and JSON. Read only: writes need a creator's wallet signature and go through the site.
REST endpoints
Base: /api. CORS is open for reads.
/coins?sort=new|linked|progress&limit=24
Launch plans, newest first, with live curve facts for linked coins.
/coins/:planId
One plan with its creator profile, notes, other plans by the same wallet and live coin facts.
/creators/:wallet
A wallet's public profile (if any) and every plan it published.
/check?mint=:mint
Creator wallet, holdings and authorities for any pump.fun mint, plus its NORKI plan if one exists.
/notes
The newest creator notes across all coins.
/fees
The fee sheet and whether it is proposed or decided.
/stats
Plans published, coins linked, plans today, and where records are stored.
/chain
SOL price, slot, TPS and (after launch) the $NORKI mint facts.
Example
Who made a pump.fun coin, and does that wallet have a plan here?
curl "http://localhost:5190/api/check?mint=<MINT>"
{
"facts": { "mint": "...", "kind": "pump", "creator": "...",
"creatorShare": 0.018, "complete": false, "progress": 0.12,
"mintAuthority": null, "freezeAuthority": null },
"plan": { "id": "...", "ticker": "...", "pledge": { "keep": 60, "burn": 30, "community": 10, "devBuySol": 0.5 } },
"profile": { "handle": "...", "verified": false },
"otherPlans": []
}How writes are signed
Writes go to POST /api/records with an action (profile, plan, link or note), the payload, a nonce from GET /api/nonce?address= and an ed25519 signature by the wallet over the message the site shows. The server rebuilds the message, checks the signature and spends the nonce. A bot can do the same with its own wallet; the record is then public under that wallet like any other.
Limits
- Reads: about 120 requests a minute per network; the creator check about 30.
- Writes: 20 a minute per network, then per wallet per day: 3 plans, 5 links, 20 notes, 10 profile saves.
- Request bodies over 6 KB are refused.