Build with MintFlow
Prepare a complete token launch from another site or agent. Then open an editable preview so the user can review the details and explicitly approve the selected launch path.
Safe by design
Public agent tools never connect a wallet, sign, spend, mint, list, buy, or broadcast.
The handoff
From conversation to explicit approval
- 01
Describe
Your site or agent gathers the collection, supply, tiers, and traits.
- 02
Prepare
MintFlow validates the data and returns a prefilled wizard URL.
- 03
Review
The user opens the URL and can edit every field before continuing.
- 04
Approve
The user explicitly approves the action required by the launch path shown in review.
Quick start
Prepare an editable launch
Send collection details to the public prepare endpoint. Open the returned launchUrl for the user. Nothing is minted until they continue in the wizard.
curl https://mintflow.me/api/v1/mint/prepare \ -H "Content-Type: application/json" \ -d '{ "collectionName": "Prism Pass", "description": "A limited membership collection.", "totalQuantity": 100, "hostingOption": "self", "tiers": [ { "id": "member", "name": "Member", "percentage": 100, "features": ["Member access", "Partner rewards"] } ] }'What agents can do
MintFlow offers the same safe preparation workflow through HTTP and browser-native WebMCP.
- Discover the API through /api/v1, /openapi.json, and /llms.txt.
- Prefill collection metadata, artwork URL, supply, royalties, tiers, traits, and canary settings.
- Open an editable preview for the user instead of asking them to re-enter details.
- Request a launch path without signing, charging, broadcasting, or committing; unavailable hosted preferences normalize to the wallet path.
- Read indexed collection members and verified OrdLock listings.
Browser WebMCP tools
These tools register through document.modelContext in supported secure browsers. They are same-origin by default. Cross-origin access requires an explicit trusted HTTPS origin allowlist.
The wallet stays in the user's hands
Wallet discovery happens in the visible MintFlow wizard. Yours Wallet and BSV Desktop can work when they expose the required BRC-100 capabilities. For Mint to your wallet, the user chooses the wallet and approves every identity, signing, funding, minting, and broadcast request.
Agents can prepare either launch path without committing it. Mint to your wallet has a $0 MintFlow fee, plus Bitcoin network costs. When the hosted path is offered in review, MintFlow-hosted sales has a $10 setup fee with hosted on-chain setup costs included; after Sigma sign-in and explicit Stripe payment, MintFlow provisions the collection, inventory, storefront, and delivery. An unavailable hosted preference is normalized to Mint to your wallet before any action.
Advanced
More integration options
Most integrations only need the prepare endpoint above. Open these sections when you need a lower-level handoff or partner setup.
Build the URL directly
Encode a versioned JSON payload as base64url and place it in theinit query parameter. Prefer the prepare endpoint when possible because it validates the payload first.
const payload = { version: 1, collectionName: "Prism Pass", description: "A limited membership collection.",};
const init = Buffer.from(JSON.stringify(payload), "utf8") .toString("base64url");
const launchUrl = "https://mintflow.me/mint?init=" + init;Read collection sale data
Use GET /api/v1/collections/{collectionId} to read indexed collection members and verified active OrdLock listings. This endpoint is read-only.
Return to a calling site
Approved partners can attach a server-issued, signed handoff to the launch URL. MintFlow validates it before offering a return to the calling site. Raw callback URLs in query parameters or init data are ignored.
Admin access and partner cosigning
Admin routes require a Sigma access token whose role claim includes admin. Approved partners can use the server-side cosign route with an admin bearer token.
POST /api/cosign
{ "partnerId": "partner_123", "rawTx": "<hex>", "targetVout": 0}
// Requires an admin bearer token with role=admin.Machine-readable reference
Start with the capability index. Agents can then follow the OpenAPI contract or the concise instructions in llms.txt.