WHAT THIS IS
PROJECT$KIMCHI APPsoftware to earn like kimchi terminal
ENTRY/landingpublic landing; KIMCHI/ mark returns here
DESK/?view=marketfive views, no login, same origin
RULESTATUS ≠ INSTRUCTIONstatuses are research labels, never a buy or sell
USAGE — DESK
COMMAND BARANALYZE <MINT | $TICKER>base58 mint, or a ticker resolved off the hot list
MARKETREAD + CLICKrows open [02] ANALYSIS in the same shell; cmd/ctrl-click opens /token/<mint>
WATCHLISTTOGGLE PER TOKENlocal to this browser
REFRESH30Smarket boards re-read while the tab is visible
VIEWS
[01] MARKETKOL LEADERBOARD · HOT · TRENDING · CALL OUTclick a KOL row for the inline detail
[02] ANALYSISTOKEN HERO · KIMCHI SCORE · SIGNAL · PRICE ACTIONthen metrics, holder distribution, whale holders, social, narrative dna
[03] LAUNCHVENUE → METADATA → REVIEW → BUILD → SIGNsigning happens in your wallet; the server never holds a key
[04] AGENTSCREATE → CONFIGURE → PERMISSIONS → KEY → API → RUNagent factory + keyed external run api
[05] DOCSTHIS PAGE
METHODOLOGY
VERSION1.0.0
SCALEfive dimensions, 0-100, weighted, deterministic
STATUS LABELSWATCH · HIGH RISK · INSUFFICIENT DATA · MEETS MONITORING THRESHOLD
NEVERBUY or SELLstatuses are research labels, not instructions
WEIGHTS
CONTRACT SAFETY0.28
LIQUIDITY / PAIR0.20
HOLDER STRUCTURE0.20
PRICE ACTION0.12
SOCIAL0.10
NARRATIVE0.10
HONEST STATES
MISSING CRITICAL FIELDINSUFFICIENT DATAoverall withholds its number instead of guessing
PROVIDER DOWNREAL REASONthe failure reason is carried, never replaced by a value
NO SOURCEUNKNOWNa value with no source and no timestamp is not published
PUBLIC API
READ (SAME ORIGIN)NO KEYthis desk reads its own routes from its own pages
READ (EXTERNAL)BEARER KEY REQUIREDAuthorization: Bearer — keys are operator-issued, hashed at rest
TOKEN REPORTGET /api/token?mint=<base58>
CHARTGET /api/chart?mint=<base58>&timeframe=1M|5M|1H|4H|1D
TRENDINGGET /api/market/trending?hot=50&trending=50&interval=1h
CALL OUTGET /api/market/callout?cap=20
SOL SPOTGET /api/sol
TOOLSGET /api/tools/<tool>the registry behind agents
AGENT API
ENDPOINTPOST /api/agents/{agent_id}/runAuthorization: Bearer gpt_*** — the agent's own key
REQUEST{"input": "Analyze this Solana token", "ca": "<MINT>"}
GATESKEY → AGENT STATUS → PERMISSION → RATEa valid key never skips a gate
RESPONSEMACHINE-READABLE JSONsettled result, or 202 + poll url when still running
ERRORSSTRUCTURED CODESMISSING_KEY · INVALID_KEY · REVOKED_KEY · AGENT_DISABLED · PERMISSION_DENIED · OVER_QUOTA
MANAGEMENTGET/POST/PATCH/DELETE /api/agents · /api/agents/{id}/keysoperator scope agents.admin, or the desk console
LAUNCH FLOW
1CONNECT PHANTOMserver holds no key; sign/send is yours
2UPLOAD METADATAlogo + name + ticker; self-hosted or ipfs
3RUN RULE REVIEWblockers stop the build; warnings carry through
4BUILD → SIGN → SENDbonding-curve create transaction, signed by you