NFT Trencher Docs
Board
Docs
How to read the board, connect a wallet, get reminded and stay safe. Times, counts and prices in examples change constantly and are only examples. Documentation v1.7 · Last verified 2026-09-17.
API
Who gets a key
The API is a benefit for holders of the Cassette. Sign in with the wallet that holds it, open your profile and press MAKE KEY in the API ACCESS tile under ALERTS & LINKS. The key appears once, right under the tile, with COPY — copy it then; later the profile shows only its beginning. NEW KEY replaces it and the old one stops at once, REVOKE kills it; both ask for a second tap.
One key per profile, personal and non-transferable. If the Cassette leaves your signed wallets, the key goes dark on its own within ten minutes; buy or move a Cassette back and make a new one.
What the API gives
The board as data: the same mints the board shows for Robinhood Chain, Ethereum, Ink, HyperEVM and Arc, a week ahead, selected by the board's own rules. For every mint — the name and links (X, site, OpenSea, mint page), every stage with its kind, label, start and end, price, currency and per-wallet limit, the active and the next stage, the status (upcoming, live, sold out, ended), the minted count and the supply, the board's tier and its flags (a free mint that turned paid, a contract that locks transfers), and when the mint's data last changed.
- The whole slice, with filters by chain, status and tier — several values at once.
- One mint by its id, contract or OpenSea slug.
- Changes since a moment — the mints whose data changed and the ones that left the board, for bots that poll.
- Your key — a check of the header, with usage and limits.
Not in the API: images, Solana, per-wallet mint statistics, anything about other people. The whitelist page of the site and its verdicts stay on the site.
Whitelist checks
The same check the board runs, from your own tools: your wallet signs OpenSea's sign-in message, OpenSea answers about that wallet, and its limits are yours, not ours. The signature becomes a pass that lives with you for three days; we keep neither the pass nor the answers. One signature per wallet — OpenSea answers only about the wallet that signed.
A scan covers the collections on the board with a gated stage ahead, or the ones you name, and returns where the wallet is on a list with the stage it is listed for. The public stage is never reported — everyone is let in there. Collections OpenSea did not answer for are listed separately: silence is not a refusal.
Limits and freshness
| What | Limit |
|---|---|
| Requests | 120 a minute, bursts of up to 30 in a second |
| Whitelist scans | 20 an hour, whatever the number of collections in a scan |
| Sign-ins | 60 an hour |
| Over a limit | 429 with the seconds to wait |
| Freshness | the board rebuilds about every 40 seconds; polling faster than once a minute buys nothing |
| Methods and errors | GET only; every error is JSON with a reason and a hint — a wrong filter or date answers 400, another method 405 |
The limits are per key, not per address. The values above may change; the reference states the current ones.
Reference and fair use
Endpoints, fields, examples and error codes: API reference. The key goes in the X-API-Key header; the base address is https://neverfuckingtrade.com/api/v1.
Keep the key and the OpenSea pass like passwords; sign OpenSea's message only in our flow, on the site or from your own code. Sharing a key or reselling the data ends access. The data is the board's own selection, provided as is; mint decisions remain yours. Full terms: API terms.