The public mint page
The drop's public mint page, as HTML. **This route needs no bearer token** — it is the link a creator pastes into a post, a bio, or a DM, and a page that asked a collector to log in before showing them a price would not be a page anyone could share. It renders the drop's name, its image, its supply and what is left, its price, and its mint state, coloured with the brand kit the drop renders with, so an edition looks like the creator's brand rather than like putty. A drop that is still a `draft`, a drop belonging to another creator, and a drop id that does not exist all answer with the same 404, so this route cannot be used to find out that a private drop exists. The page is static HTML with no script: a mint is a server-side reservation, and a page that reserved editions in the browser would be the double-mint bug again.
The drop's public mint page, as HTML. This route needs no bearer token — it is the link a creator pastes into a post, a bio, or a DM, and a page that asked a collector to log in before showing them a price would not be a page anyone could share. It renders the drop's name, its image, its supply and what is left, its price, and its mint state, coloured with the brand kit the drop renders with, so an edition looks like the creator's brand rather than like putty. A drop that is still a draft, a drop belonging to another creator, and a drop id that does not exist all answer with the same 404, so this route cannot be used to find out that a private drop exists. The page is static HTML with no script: a mint is a server-side reservation, and a page that reserved editions in the browser would be the double-mint bug again.
Path Parameters
The drop's id. The last segment of its public mint-page URL.
1 <= length <= 64Response Body
text/html
application/json
application/json
curl -X GET "https://example.com/creator/drops/string/page""string"What this deployment can take GET
The payment methods this API has a provider wired for, and for each one the stablecoins it can settle. A storefront renders one Pay button per entry, so a deployment that has wired cards and not stablecoins shows one button rather than a dead second one. `configured` is false for a method with no provider — a card-only deployment is a legitimate state, and a stablecoin checkout on it is refused with a 503 and a sentence rather than failing deeper.
The public drop as JSON GET
The same public view the mint page renders, as JSON, for a client that wants the drop's name, price, and remaining supply without parsing HTML. **No bearer token is required.** The shape is a strict subset of the creator's own view: no `creatorAddress` is withheld here, no brand-kit id, no status. The `supply` block is recomputed on every read, so a collector polling this never sees a stale remaining count. A draft, a foreign drop, and a missing id are the same 404.