paid

Get outcome labels for up to 40 pump.fun mints, one payment

Use when you grade a list of your own rug or graduation calls or backtest a signal on pump.fun memecoins; for one mint the $0.001 single lookup costs less. One payment returns the outcome labels of one to 40 caller-selected pump.fun mints in the order asked with the fields and the fixed public rule of the single lookup GET /v1/outcome/{mint} and is charged once whatever the answers. Each item: rugged by the public rule and when, rugged within 300 s of launch, true graduation and migration time, the creator's first sell, peak and last curve SOL, the mayhem flag, whether each label is settled (resolved) and the rule version. A mint we never saw answers known:false; a list with no known mint, more than 40, a malformed or a repeated mint is refused unpaid. No probabilities and no opinions.

get/v1/outcome/batch

Request

  • Base URL: https://api.loopholetape.com
  • URL: https://api.loopholetape.com/v1/outcome/batch
  • Auth: none required

Query parameters

mintsstring nullable

One to 40 distinct mint addresses, comma-separated (MCP accepts an array).

One to 40 distinct mint addresses, comma-separated (MCP accepts an array). A pasted link works too: pump.fun/coin/<mint>, gmgn.ai/sol/token/<mint>, solscan.io/token/<mint>, birdeye.so/token/<mint>, a Jupiter swap link or solana:<mint>; a DexScreener, Axiom or Photon link only when its id is a mint we know (a pair address is refused 400 pair_address_not_mint). The link is resolved before the 402, which names the resolved mint; an unreadable link is refused 400 url_not_recognised, unpaid.

Response

Paid response (header PAYMENT-RESPONSE carries the settlement)

okboolean required
schema_version'2.0' required
generated_atstring date-time required
tnumber required

unix seconds at generation

coverage'full' | 'thin' required

the mint is inside our live window (created while our captur / thin = the mint is not in the live window (older than ~2 h of silen

dataobject required

Example response

{
  "data": {
    "...": "route specific"
  }
}

Changes

No recorded changes to this operation across all 2 revisions of this API.