Skip to main content
Access: Mint account The Mint API lets an application generate, manage, and deliver the same account-owned assets available through Mint and Mint MCP. API generations do not create chats; they save assets directly to the account library. Use the production base URL https://api.mint.gg/v1 and the OpenAPI contract as the source of truth for request and response schemas.

​
Services

3D Models

Generate, review, optimize, retopologize, convert, and retrieve 3D Models.

Asset Packs

Generate and manage coordinated collections of 3D assets.

Worlds

Generate, review, revise, and retrieve explorable Worlds.

Materials

Generate Materials and coordinated Material Packs.

Images

Generate, edit, retrieve, and upload reference images.

Audio

Generate and retrieve sound effects and general Audio.

Animation

Animate eligible 3D Models and Asset Pack characters.

Assets

List account assets and retrieve their files and manifests.

​
Authentication

Sign in to Mint Platform with the Google or email account you use on Mint. Open API keys, create a live key, and send it as a Bearer token: Mint-approved installed integrations can instead use OAuth Authorization Code with S256 PKCE. Those integrations receive a pre-registered public client ID and exact callback URLs from Mint, request resource=https://api.mint.gg, and use mint:assets:read and/or mint:assets:generate. OAuth access maps directly to the signed-in account’s default developer project; the integration does not create or store a hidden API key. API keys remain the standard choice for your own server-side integration.

Authentication, rate limits, and retries

Protect Bearer credentials, stay within account limits, and retry safely.

Credits and usage

Check available Credits, pending reservations, and account API usage.

AI agent skill

Give Codex, Claude Code, Cursor, or another coding agent the complete workflow.

​
Core workflow

  1. Authenticate with MINT_API_KEY.
  2. When you need an advisory Credit requirement, call POST /v1/pricing:estimate immediately before starting work.
  3. Start work with the service-specific endpoint. Preview-based generation defaults to auto.
  4. Poll the returned operation with bounded backoff.
  5. Read the asset identified by operation.resource and retrieve its available files.
Use Mint Platform to revoke keys, inspect API operations, review usage, and manage the subscription and Usage Credits shared by Mint web, MCP, and the API.

​
Asset organization

API generations are saved directly to the account library. They do not create Mint chats or chat history. API-created assets are not assigned to personal Mint Projects. If your product has users, teams, collections, or workspaces, keep that organization in your application database and associate it with the Mint operation and asset IDs returned by the API. Set generationMode to review only when the integration needs to inspect, approve, or revise a Preview before final generation. The pricing estimator is read-only and uses normal authenticated account rate limits. It does not accept Idempotency-Key, create an operation, reserve Credits, or guarantee the later charge. See Credits and usage. Start with the Quickstart, or install the Mint API skill when a coding agent will implement the integration.

​
Preview-based generation

Worlds, 3D Models, and Asset Packs first create a Preview: a fast visual proposal, not the final 3D asset.
  • auto is the default and recommended generationMode. Mint continues from Preview to the final asset without another API call.
  • review pauses at preview_ready. The integration must approve the Preview or revise it with concrete feedback.
  • Revising creates an updated Preview. Approving begins final generation.
generationMode controls workflow behavior, not quality. Each 3D Model, Asset Pack, and World guide documents its exact approve and revise fields.

​
Presets

Choose a public generationPreset; Mint selects and manages the underlying provider model. Provider model IDs are not part of the public contract. Build against generationPreset and the returned Mint resource IDs.

​
Operations and statuses

An operation tracks asynchronous work. Save its id and poll the URL in the Location header rather than assuming the initial response means the asset is finished. When auto generation reaches a Preview but needs more Credits for the final asset, the same operation moves to billing_required instead of failing or becoming stranded. Its Preview remains available. After resolving billing, call POST /v1/operations/{operationId}:resume when the operation already contains a Preview or other intermediate resource. If billing blocked the request before Mint created a resource, repeat the original request with the same Idempotency-Key; Mint reopens that operation instead of creating a duplicate. Operation responses can include a credits object:
  • estimated: current best estimate for the requested stages.
  • reserved: Credits still held for unfinished work.
  • finalized: Credits settled for completed provider work.
  • availableAfterReservation: the account balance after the latest reservation or settlement update.