canonical: https://jentic.com/apis/crossmint.com/crossmint

# Crossmint API

Jentic publishes the only available OpenAPI specification for Crossmint API, keeping it validated and agent-ready. Crossmint is a multi-chain platform for wallets, NFT and SFT minting, collection management, and crypto-and-card checkout. The API spans 81 endpoints covering smart wallet creation and funding, NFT and SFT mint with optional template flows, transaction and signature approvals, payment-enabled orders, verifiable credentials, IP asset registration, and user identity. It supports server-side integrations via an X-API-KEY header issued from the Crossmint console.

## For AI agents

Create wallets, mint NFTs/SFTs, run on-chain transactions, and process crypto-or-card orders on Crossmint across multiple blockchains.

## Scope

Does not handle on-chain consensus, custom smart contract deployment, or DEX trading - use for Crossmint-managed wallets, mints, and orders only.

## Capabilities

- Create and fund smart wallets across supported chains via /2025-06-09/wallets endpoints
- Mint NFTs and SFTs into a collection, with optional template-based mint flows
- Run on-chain transactions and signatures with explicit approval workflows
- Process payment-enabled orders that accept both crypto and card via the orders endpoints
- Manage collection metadata, edit individual NFTs, and burn obsolete tokens
- Delegate signing authority to additional wallet signers and rotate them

## Use cases

### Card-to-NFT Checkout

Sell NFTs to mainstream users who pay with a credit card by creating an order via POST /2022-06-09/orders, processing payment via POST /2022-06-09/orders/{orderId}/payment, and minting on completion. Crossmint handles the fiat-to-crypto bridge and the wallet-on-the-fly creation, so the buyer doesn't need a wallet of their own. Integration is typically a single page plus a backend payment confirm.

Example prompt: Create a Crossmint order for an NFT priced at $30 USD, process the card payment, and confirm the mint succeeded

### Smart Wallet Creation and Funding

Provision a non-custodial smart wallet for each user with POST /2025-06-09/wallets and fund it via POST /2025-06-09/wallets/{walletLocator}/balances. Apps use this to onboard users without requiring them to install MetaMask, then attach delegated signers so app-side automation can co-sign transactions. The wallet locator abstracts away the underlying chain and address format.

Example prompt: Create a Crossmint smart wallet for user.email@example.com on Polygon and fund it with 5 USDC

### NFT Drop Pipeline

Run a structured NFT drop by creating a collection with POST /2022-06-09/collections, defining mint templates, and minting per-recipient via POST /2022-06-09/collections/{collectionId}/nfts. Teams use idempotent PUT mint endpoints to retry safely when network issues happen, and PATCH/DELETE to fix metadata mistakes or burn errors. The /actions/{actionId} status endpoint lets the pipeline poll for on-chain confirmation.

Example prompt: Create a collection on Polygon, define a template, and mint 100 NFTs to a list of recipient wallets, polling /actions/{actionId} until each succeeds

### AI Agent On-Chain Action Approval

An AI agent operating on a user's behalf creates and approves transactions on a Crossmint smart wallet through Jentic. The agent searches for the crossmint_create_transaction operation, executes against the user's vaulted X-API-KEY, then calls the approvals endpoint when policy permits. Jentic isolates the API key so the agent only ever sees a scoped capability, not the raw secret.

Example prompt: Use the Jentic SDK to create a Crossmint transaction sending 10 USDC and submit the approval, returning the resulting transaction ID

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /2025-06-09/wallets | Create a smart wallet |
| POST | /2025-06-09/wallets/{walletLocator}/transactions | Create a wallet transaction |
| POST | /2022-06-09/collections | Create a collection |
| POST | /2022-06-09/collections/{collectionId}/nfts | Mint an NFT into a collection |
| POST | /2022-06-09/orders | Create an order |
| POST | /2022-06-09/orders/{orderId}/payment | Process payment for an order |
| GET | /2022-06-09/actions/{actionId} | Get action status |
| GET | /2025-06-09/wallets/{walletLocator}/balances | Get wallet balance |

## Key resources

- **Wallets** — Create wallets, get balances, fund wallets, run transactions and signatures, and manage delegated signers via /2025-06-09/wallets endpoints
- **Collections and NFTs** — Create and update collections, mint and burn NFTs and SFTs, and manage templates via /2022-06-09/collections endpoints
- **Orders and Payments** — Create orders, process payments, and edit orders via /2022-06-09/orders endpoints
- **Actions** — Poll asynchronous mint and transaction status via /2022-06-09/actions/{actionId}

## Why Jentic

- **Setup:** Wiring Crossmint by hand means setting its X-API-KEY header auth, picking the production or staging host, and juggling two dated path prefixes (2022-06-09 and 2025-06-09) across wallets, collections, and orders. Through Jentic you install once, import Crossmint from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Crossmint puts the wallet locator, collection id, and order id in the URL path (/2025-06-09/wallets/{walletLocator}/..., /2022-06-09/collections/{collectionId}/nfts), so a rule can pin your agent to one wallet or collection. You choose the operations it may call, so a wallet transaction submission or order payment is not included unless you add it.
- **Credential handling:** Your Crossmint X-API-KEY is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'mint an NFT' or 'create a smart wallet', and Jentic returns the matching Crossmint operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Crossref API** — Crossref handles DOI metadata for scholarly works while Crossmint handles wallet and NFT operations
- **Cronitor API** — Cronitor monitors scheduled jobs that may run minting or settlement workflows on Crossmint
- **Cron-job.org API** — cron-job.org schedules recurring HTTP calls into Crossmint for batch mints or status polls

## FAQ

### Why is there no official OpenAPI spec for Crossmint API?

Crossmint does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Crossmint API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Crossmint API use?

The Crossmint API uses an API key supplied in the X-API-KEY header, generated from the Crossmint console with a server-side scope. Through Jentic the key is held encrypted in the vault and injected into the X-API-KEY header at request time so it never enters the agent's context.

### Can I mint an NFT and accept a card payment in the same flow?

Yes. Create the order with POST /2022-06-09/orders (with the NFT product configuration), call POST /2022-06-09/orders/{orderId}/payment to charge the card, and Crossmint mints the NFT to the buyer's wallet on payment success. Poll GET /2022-06-09/actions/{actionId} for confirmation.

### How do I create a smart wallet through Jentic?

Search Jentic for 'create a Crossmint wallet', load the schema for POST /2025-06-09/wallets, and execute with the user identifier and chain. Jentic handles the X-API-KEY injection.

### How many endpoints does the Crossmint API expose?

The Crossmint API exposes 81 endpoints covering wallets, transactions, signatures, collections, NFT and SFT minting, templates, orders, payments, verifiable credentials, IP assets, and user management.

### Can I retry a mint safely if my network drops?

Yes. Crossmint exposes idempotent PUT mint endpoints such as PUT /2022-06-09/collections/{collectionId}/nfts/{id}, so the same mint ID will not produce duplicate on-chain mints if you retry.

### Can I limit what my agent is allowed to do with the Crossmint API?

Yes. Because you run Jentic One yourself, your own rules decide which Crossmint operations the agent may call and which stored X-API-KEY it uses, so a wallet transaction submission via POST /2025-06-09/wallets/{walletLocator}/transactions or an order payment via POST /2022-06-09/orders/{orderId}/payment is off limits unless you add it. Since Crossmint carries the wallet locator, collection id, and order id in the URL path, you can pin the agent to a single wallet or collection and let it only mint into that collection or poll GET /2022-06-09/actions/{actionId} for status. The API key stays with your own instance and is injected at request time, so the agent never sees the raw secret.