Mintea

Appearance

Getting Started ​

This guide walks through registering, authenticating, creating a collection, and minting a token with the Mintea API.

Base URL ​

https://api.mintea.tech

All versioned routes are under /v1. Examples below use this origin.

Health check (no auth):

bash
curl https://api.mintea.tech/health
# → { "ok": true }

1. Register (invite required) ​

Registration consumes an invite code. Contact your operator if you do not have one.

bash
curl -c cookies.txt -X POST https://api.mintea.tech/v1/auth/register \
  -H 'content-type: application/json' \
  -d '{
    "email": "you@example.com",
    "password": "password123",
    "inviteCode": "welcome-2026"
  }'

A successful register sets the mintea_session cookie (saved into cookies.txt via -c).

2. Log in ​

If you already have an account:

bash
curl -c cookies.txt -X POST https://api.mintea.tech/v1/auth/login \
  -H 'content-type: application/json' \
  -d '{"email":"you@example.com","password":"password123"}'

Confirm the session:

bash
curl -b cookies.txt https://api.mintea.tech/v1/auth/me

See Authentication for cookie vs API key details.

3. Create an API key (optional) ​

For scripts and CI, create a key while authenticated with the cookie:

bash
curl -b cookies.txt -X POST https://api.mintea.tech/v1/api-keys \
  -H 'content-type: application/json' \
  -d '{"name":"ci"}'

The response includes the raw key once (prefix mtk_ for live, mts_ for sandbox). Store it securely — only a hash is kept server-side.

Create a sandbox key with "environment":"sandbox" — see Sandbox vs testnet vs live. Fuji is a real testnet and still spends (cheaper) credits.

Use it on protected routes:

bash
curl -H "Authorization: Bearer mtk_..." https://api.mintea.tech/v1/collections
curl -H "Authorization: Bearer mts_..." https://api.mintea.tech/v1/collections

4. Check credits ​

bash
curl -b cookies.txt https://api.mintea.tech/v1/billing/credits

New accounts start on the Basic plan (100 monthly credits). See Credits for costs.

5. Create a collection ​

Creating a collection deploys an NFT via the Mintea factory (5 credits on Fuji, 15 on Avalanche). Sandbox keys (mts_) cost 0 and do not deploy onchain. You only supply name and symbol — no baseURI; the token descriptor is wired onchain at construction.

bash
curl -b cookies.txt -X POST https://api.mintea.tech/v1/collections \
  -H 'content-type: application/json' \
  -d '{"name":"Demo","symbol":"DEMO"}'

Note the returned collection address for the next steps.

6. Mint a token ​

Minting costs 1 credit on Fuji and Avalanche (0 with a sandbox key). Supply a recipient address; end users do not need a wallet connected to the API.

bash
curl -b cookies.txt -X POST https://api.mintea.tech/v1/collections/0xCollection/mint \
  -H 'content-type: application/json' \
  -d '{"to":"0xRecipient"}'

Replace 0xCollection with your collection address and 0xRecipient with the wallet that should receive the NFT.

Next steps ​

  • Set onchain metadata keys/values (ERC-8048) — see Collections
  • Batch mint or mint-with-metadata for cheaper / combined flows — see Credits
  • Understand error shapes — see Errors