pnl.memedocs

Changelog

What changed for a caller, newest first.

Every change

Nothing here breaks an earlier call unless it says so.

  1. Live traders, as data
    • get_live_traders: the traders shown outside pnl.meme who are trading this minute, each with the lines a live tile draws.
    • get_live_trader: one of them, live: the session, money in play, what they hold, their newest moves, each coin's cap series, their board row and their best plays.
    • get_trade_replay: one of their plays as data to redraw: the token's cap from entry to exit, every buy and sell, what went in and what it made.
    • Three kit tools on MCP and REST, on a data key on plan builder or above.
    Tools
  2. Why it crossed $500K and $1M
    • GET /v1/reasons/{chain}/{address} now carries milestones: the top reasons a token had the first time its market cap crossed $500K and $1M, kept as they were then, to pin on a chart. Empty until a token crosses one.
    Reasons API
  3. Why a token moves
    • GET /v1/reasons/{chain}/{address}: the crowd's top reasons a token moves, each in a real post's words, who says them and the mood of the rest, on a data key on plan builder or above. Its OpenAPI document is GET /v1/reasons/openapi.
    • The same answer as a kit tool, get_reasons, on MCP and REST.
    Reasons API
  4. The trader kit
    • POST /v1/mcp now lists the trader kit: tools named for the question they answer, from get_trader and get_token to get_changes_since. ?catalog=full still lists the whole capability menu to a key.
    • No key needed to start: the public tier answers the free reads to any client.
    • Every tool is a REST call too, GET /v1/tools/{tool}, and one OpenAPI 3.1 document describes them all at GET /v1/tools/openapi.
    • A watchlist per key, manage_watchlist, and a changes cursor over it, get_changes_since.
    • Three prompts on the server: vet, profile and morning_brief.
    • New keys start pnl_. A key you already hold keeps working on every door.
    Connect your agentTools
  5. pump.fun accounts in depth
    • GET /v1/pump/users/{id} with its trades and positions, and GET /v1/pump/stream for wallet activity as it arrives.
    pump.fun Data API
  6. Whose wallet is this
    • GET /v1/wallets/{address}: what we hold on one wallet, in one request. Its OpenAPI document is GET /v1/wallets/openapi.
  7. Two platform Data APIs
    • Beside FOMO's, on the same key and the same allowance:
    • GMGN Data API: GMGN wallets with the name and X GMGN gives them, and the PnL it published, on the same key.
    • pump.fun Data API: pump.fun accounts: the wallet, its username, the X it declares and its calls, on the same key.
  8. Free keys
    • A free data key, minted in the Builder API window after one human check. No login, no card.
    Plans & keys
  9. The plan ladder
    • Builder, pro, network and fleet, each paid once in USDC for 30 days; free is the floor a lapsed plan returns to.
    • FOMO parity doors: users, resolve, pnl, me, and pump.fun users and callouts.
    Plans & keys
  10. The FOMO Data API
    • A typed reference with its OpenAPI 3.1 document, and GET /v1/fomo/stream, resumable by seq.
    FOMO Data API
  11. Buy a key
    • One USDC payment from your own wallet. The key is minted on the spot and shown once.
  12. The data key
    • A read-only class of key, with three doors: POST /v1/skills/run, POST /v1/mcp and GET /v1/stream.
NORMALsigned outpolling? keys