Getting started
Base URL https://www.evermor.trade/api/v1. Reads are plain GETs, writes are POSTs with a JSON body, and every answer is JSON. Prices and amounts are in whole units (a token has 18 decimals, a pair has its own); trades also carry the raw integers. Times are unix seconds.
const r = await fetch("https://www.evermor.trade/api/v1/tokens?sort=newest&limit=20");
const { tokens } = await r.json();
for (const t of tokens) console.log(t.symbol, t.marketCapUsd, t.rules.map((x) => x.name));GET https://www.evermor.trade/api/v1 lists the endpoints and the contract addresses.
Tokens
GET/tokens
| Parameter | Meaning |
|---|---|
| sort | marketCap (default) or newest |
| rule | only tokens with this rule, by id: kntq-burn, holder-rewards, auto-burn, flow-rules-v2… |
| limit | 1 to 500, default all |
Each token looks like this:
{
"address": "0x…",
"name": "Example",
"symbol": "EXMPL",
"chainId": 99901,
"creator": "0x…",
"pair": { "address": "0x0000000000000000000000000000000000000000", "symbol": "HYPE", "decimals": 18 },
"poolId": "0x…",
"hook": "0x…",
"launchedAt": 1794100000,
"priceUsd": 0.0000412,
"pricePair": 0.00000061,
"marketCapUsd": 38450.2,
"supply": 933500553,
"burnedPct": 6.65,
"fees": { "protocolPct": 1, "creatorPct": 1, "lpPct": 1 },
"rules": [{ "id": "kntq-burn", "name": "KNTQ burn", "category": "rewards", "summary": "…" }],
"rulesFinal": false,
"pendingAmendment": null,
"wheel": null,
"metadataURI": "ipfs://…",
"url": "https://www.evermor.trade/token/0x…"
}pair is the asset the token trades against now (the zero address is native HYPE). On a token with a pair wheel it changes at each spin, and so does poolId. burnedPct is the share of the 1,000,000,000 supply that is gone for good.
One token
GET/tokens/{address}
settings, and a custom hook's full drawing under customHook. 404 if the address is not an Evermor token.Trades
GET/tokens/{address}/trades
| Parameter | Meaning |
|---|---|
| since | unix seconds: only trades after it, for polling |
| limit | 1 to 1000, default 200 |
{
"id": "0xabc…-12",
"txHash": "0xabc…",
"block": 1234567,
"timestamp": 1794200000,
"token": "0x…",
"trader": "0x…",
"side": "buy",
"amountPair": 2.5,
"amountToken": 4012345.1,
"pricePair": 0.000000623,
"raw": { "amountPair": "2500000000000000000", "amountToken": "4012345100000000000000000", "sqrtPriceX96": "…" }
}Amounts are gross, before the hook's cuts. trader is the buyer or seller the Evermor router named, otherwise the transaction's signer.complete is false for a moment when the index is behind the chain.
Holders
GET/tokens/{address}/holders
progress below 1 means the index is still reading the token's history.KNTQ furnace
GET/furnace
Stats
GET/stats
Write: how it works
The write endpoints never sign or send anything, and never hold a key. They check a request with the same code as the site's forms, then answer the transaction(s) your own wallet signs and sends: { description, chainId, to, data, value }, in order. Whatever the API checks, the contracts check again, so a tampered transaction just reverts.
Send the wallet that will sign as creator or trader: the API then runs the transaction against mainnet first and returns simulation, with the reason in plain words when the contracts would refuse it.
// viem: sign and send what the API returned, in order, from the creator's wallet
for (const t of reply.transactions) {
const hash = await wallet.sendTransaction({ to: t.to, data: t.data, value: BigInt(t.value) });
await client.waitForTransactionReceipt({ hash });
}Rules catalog
GET/rules
Check a custom hook
POST/hooks/check
{
"customHook": {
"taxes": [{ "side": "buy", "from": 0, "to": 0, "pct": 3, "burn": 50, "creator": 50, "recipient": 0, "lp": 0 }],
"guards": [{ "side": "buy", "kind": "maxUsd", "from": 0, "to": 30, "amount": 500 }]
},
"creatorFee": 1
}Times are minutes from launch (to: 0 means forever). Tax destinations (burn, creator, recipient, lp) are percentages that add up to 100. Guards are pause, holds, maxUsd or minUsd, and end within 2 hours. Build one visually in the hook builder to see the full shape.
Launch a token
POST/launch
| Parameter | Meaning |
|---|---|
| name, symbol | 1 to 32 characters; 1 to 12 letters or digits |
| description, website, x, telegram | optional; links are https:// URLs |
| image | logoSvg | metadataURI | an ipfs:// or https:// image, a plain SVG logo, or your own metadata URI (then nothing is pinned) |
| pair | a pair symbol from /rules (default HYPE), or wheel: { pairs: [...], every } for a pair wheel |
| preset | rules | a ready-made set by id, or rules: [{ id, values }]; values you leave out take their defaults |
| customHook | a custom hook, as in /hooks/check, added next to the rules |
| creatorFee, lpFee | in %: 0 to 10 |
| firstBuy | an amount of the pair bought in the launch transaction (in an ERC-20 pair, the answer starts with an approval) |
| finalRules | true makes the rules final at launch |
| creator | the wallet that will sign: the launch is simulated as it |
| dryRun | true checks and simulates without pinning anything |
{
"creator": "0xYourWallet",
"name": "Slow Burn",
"symbol": "SLOW",
"description": "Every buy burns a little.",
"image": "ipfs://Qm…",
"website": "https://…",
"pair": "HYPE",
"rules": [
{ "id": "anti-snipe-pool" },
{ "id": "kntq-burn", "values": { "buy": 1, "sell": 1 } }
],
"creatorFee": 1,
"firstBuy": "0.5",
"dryRun": true
}{
"valid": true,
"summary": { "pair": "HYPE", "cutsAtMost": { "buyPct": 3, "sellPct": 2 }, "rules": [ … ], "launchFee": "15000000000000000" },
"transactions": [
{ "description": "Launch Slow Burn ($SLOW)", "chainId": 99901, "to": "0x1B87…", "data": "0xbaef…", "value": "515000000000000000" }
],
"simulation": { "ok": true, "token": "0x…" }
}A request with problems answers valid: false and every problem in plain words. Launches are limited to 20 an hour per IP.
Trade
POST/trade
| Parameter | Meaning |
|---|---|
| token | the token's address |
| side | buy or sell |
| amount | the pair for a buy, the token for a sell, in whole units |
| slippagePct | 0 to 50, default 3 |
| trader | the wallet that will sign: rules that look at who trades are checked against it |
| referrer | a wallet that earns the referral share on tokens with the Referral rule |
Change a token's rules
POST/tokens/{address}/amend
action: "propose" with remove: [ids] and add: [{ id, values }], or cancel, or finalize (no change ever again). A proposal applies after 24 hours of public notice; apply lets anyone apply a due one (the keeper does).The contract's terms apply: rules that hold funds are never removed; rules that tax or refuse sells, or raise the pool fee, are never added; and what added rules take must fit in what removed rules take today.
Hook market
POST/market/message
{ author, draft: { name, description, tags, royalty, spec } }: the exact text the author signs (personal_sign) to publish a custom hook, its ts, and the draft to send back.POST/market/publish
{ draft, author, ts, signature } within 5 minutes: publishes the hook on the Hook market, as the site does. Every token launched with it pays the author the royalty.Limits and terms
Answers are cached at the edge for 3 to 60 seconds, so polling faster than that returns the same data. Past the cache, each IP gets 120 requests a minute; above it the API answers 429 with a Retry-After header.
The API is free and best effort, with no uptime promise. Fields may be added to v1, never renamed or removed. For anything that moves money, read the chain: every contract is verified on the Elysium explorer.
Building something with it? Tell us on X at @TradeEvermor.