Appearance
Credits
Onchain operations deduct credits after a successful onchain confirmation. Image uploads debit 1 credit before contacting Pinata and refund upload failures. Insufficient balance returns 402 with code insufficient_credits.
Plans (v1)
| Plan | Monthly credits | Notes |
|---|---|---|
| Basic | 100 | Default |
| Pro | 500 | Upgrade currently rejected (403) |
| Pro+ | 2000 | Upgrade currently rejected (403) |
Check your balance:
bash
curl -b cookies.txt https://api.mintea.tech/v1/billing/credits
# or
curl -H "Authorization: Bearer mtk_..." https://api.mintea.tech/v1/billing/creditsPOST /v1/billing/upgrade always returns 403 in v1.
Action costs
Costs depend on the chain. Sandbox collection actions cost 0. Real IPFS image uploads cost 1 credit even with sandbox keys. Fuji is cheaper than Avalanche; Fuji is not free.
| Action | Simulated (mts_) | Fuji 43113 | Avalanche 43114 |
|---|---|---|---|
| Create collection | 0 | 5 | 15 |
Mint (safeMint) | 0 | 1 | 1 |
Mint with metadata (safeMintWithMetadata) | 0 | 1 | 1 |
Batch mint (safeMintBatch / with metadata) | 0 | ceil(n / 6) (min 1) | ceil(n / 2) (min 1) |
| Freeze / lock / pause / metadata / registry | 0 | 0 | 0 |
Batch mint is cheaper than n individual mints because one onchain transaction amortizes operator overhead. Fuji uses a steeper discount. Including metadata in a batch does not change the batch cost (standalone setMetadata is free).
Batch size is capped at 50 recipients per request.
See Sandbox vs testnet vs live for when to use mts_ keys vs Fuji.
Insufficient credits
When a paid action cannot be funded:
- HTTP status:
402 - Error code:
insufficient_credits - Body shape: see Errors
Credits are not deducted if the onchain transaction fails.
Image uploads
Each successful IPFS image upload costs 1 credit, including repeat uploads and uploads during minting or metadata editing. Choosing an existing gallery image, editing gallery names, and editing tags are free. The dashboard shows the total batch cost before upload and requires enough credits to start it. The API debits credits atomically before contacting Pinata and refunds upload failures. Invalid images are rejected before billing. If Pinata succeeds but the gallery catalog write fails, the upload stays charged and its URI is returned.