Lookup table

curl -s https://stonkpile.xyz/api/lookup | jq '.lookup | length'

let table = null;

async function search(q) {
  table ??= (await (await fetch("https://stonkpile.xyz/api/lookup")).json()).lookup;
  const needle = q.toLowerCase();
  return table.filter(
    (r) =>
      r.symbol?.toLowerCase().includes(needle) ||
      r.name?.toLowerCase().includes(needle) ||
      r.mint === q,
  );
}

curl -s https://stonkpile.xyz/api/lookup | jq '.lookup | length'

let table = null;

async function search(q) {
  table ??= (await (await fetch("https://stonkpile.xyz/api/lookup")).json()).lookup;
  const needle = q.toLowerCase();
  return table.filter(
    (r) =>
      r.symbol?.toLowerCase().includes(needle) ||
      r.name?.toLowerCase().includes(needle) ||
      r.mint === q,
  );
}

GET https://stonkpile.xyz/api/lookup

The search table on its own: every ticker, every company name and every mint in the index, with nothing else attached. Use it to build your own search box without pulling the full index on every keystroke.

Why it is its own endpoint

It used to be serialised into the homepage, which was fine while it held 1,600 tickers and no addresses. Adding mints and every quoted coin roughly doubled the page, and most visitors never type anything. So it moved here: the client fetches it the first time the input is touched and the browser caches it for the life of the snapshot. The same reasoning applies to anything you build. Fetch it once, search locally.

Response

string

ISO timestamp of the snapshot this table came from.

object[]

One entry per searchable thing: the symbol, the name, the mint and what kind of entry it is, so a hit on a quoted coin is not presented as a stock.

curl -s https://stonkpile.xyz/api/lookup | jq '.lookup | length'

let table = null;

async function search(q) {
  table ??= (await (await fetch("https://stonkpile.xyz/api/lookup")).json()).lookup;
  const needle = q.toLowerCase();
  return table.filter(
    (r) =>
      r.symbol?.toLowerCase().includes(needle) ||
      r.name?.toLowerCase().includes(needle) ||
      r.mint === q,
  );
}

A user pasting a contract address wants a decision, not a list. When the query looks like a mint, send it to /api/verify/{mint} instead and show the verdict.

Caching

Five minutes at the edge, with a longer stale-while-revalidate window so a search right after the snapshot turns over is answered instantly. Access-Control-Allow-Origin: *.

Getting started

Concepts

API reference

Agents

Why it is its own endpoint

Response

Caching

​Why it is its own endpoint

​Response

​Caching

Why it is its own endpoint

Response

Caching