Fregs API • Public • 100% on-chain artwork

Fregs API

The Fregs API is a thin public layer over the live collection. Use it to fetch minted Fregs, owner data and trait metadata from a clean HTTP surface, while live token state stays on-chain and SVG assets are served directly from the API bundle. The examples below are static snapshots that mirror the response shapes and use `api.fregs.io` in the curl commands.
Fregs start at token ID 0. If a token used to exist but was burned, the API returns 410 Gone.

Base URL https://api.fregs.io

Primary prefix /fregs

Response formats application/json, image/svg+xml

Static examples are trimmed for readability, especially SVG payloads.

Collection

Core Endpoints

Use these for collection-wide lookups, token detail pages and ownership checks. Token-specific examples below are generated from the first minted Freg found on the active deployment.

Traits

Trait Endpoints

Trait listings and trait SVG payloads come from the bundled project manifests and local SVG assets. Large SVG strings are trimmed in the docs view only, so the structure stays real without filling the page with data URIs.

Items

Item Endpoints

Item listings and ownership summaries are served from the FregsItems contract. Item detail routes return static item metadata as JSON by default, with a separate SVG endpoint for the raw item artwork.