Sandbox vs testnet vs live

Mintea has three environments. They are not the same thing.

Environment	How you access it	Chain	Credits	Onchain?
Simulated / sandbox	Authorization: Bearer mts_...	313370	0	No — Postgres simulator
Testnet / Fuji	Cookie or mtk_ live key	43113	Cheaper	Yes — real Avalanche Fuji
Live / Avalanche	Cookie or mtk_ live key	43114	Full price, Pro	Yes — Avalanche C-Chain

Fuji is a real testnet (real RPC, factory, and transactions). It is useful for trying the product onchain. It is not the integrator sandbox.

Sandbox keys (mts_)

Same HTTP contract, same host (https://api.mintea.tech). No second deploy.

1. Sign in to the Operator Console.
2. Settings → API keys → Create sandbox key. Copy the mts_... secret once.
3. Call the API as usual:

curl -H "Authorization: Bearer mts_..." https://api.mintea.tech/v1/chains
# → only the simulated chain (environment: "simulated")

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

Sandbox collections persist so list/get/mint/manage keep working after restart. Responses use the same JSON as live (address, txHash, tokenId) with synthetic values. There is no Snowtrace explorer.

Sandbox keys cannot use Fuji or Avalanche (400). Live keys and cookie sessions cannot use chain 313370. Console create-collection stays on Fuji/mainnet and still spends credits.

Caps apply (20 simulated collections and 1000 tokens per user).

Fuji testnet (43113)

Real contracts. Available on all plans, including Basic. Credits are discounted (create 5, mint 1, batch ceil(n / 6)). This is still metered — it is not free.

Avalanche mainnet (43114)

Real contracts, full credit prices (create 15, mint 1, batch ceil(n / 2)). Requires Pro / Pro+.

See Credits for the schedule and API Keys for create/list/revoke.