Platform & API

Platform architecture

Quick answer

The backend is a Node.js/Express service on PostgreSQL that caches on-chain data, indexes metadata and issues allowlist signatures. It never custodies assets. Elevate does not currently offer a supported public developer API.

This page exists so that “how does it work” has an answer. Endpoints are internal and may change without notice; if a supported public API is published it will be documented separately.

Who this is for

Developers curious how the platform works. This is architecture documentation, not a public API reference.

Projects service

Lists collections with live on-chain data, serves single-collection detail and streams updates. Minted counts and participants are read from the contracts and cached briefly.

Collections service

Serves a collection's static data from the chain, recently minted tokens, and the tokens owned by a given wallet.

Minting service

Checks allowlist status, issues signatures for eligible wallets and records mint history per wallet. Transactions themselves are signed and sent by your wallet.

Indexing

Collections are indexed by tracking transfers and fetching token metadata. Indexing starts automatically the first time a collection is viewed, or can be triggered manually. Rarity is computed from the indexed metadata after reveal.

What the backend never holds

User private keys.
User funds or tokens.
Anything that could move assets without the user's wallet signing.

Public API status

Not a public API

The endpoints the site uses are reachable but unsupported and undocumented for third parties. Do not build on them. If Elevate publishes a supported developer API, it will appear under /docs/api with versioning and a changelog.

Written and maintained by the Elevate team. Last updated 12 September 2026. Corrections: reach the team on the official Discord.

Ready to mint? View verified Bittensor NFT collections.